Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Ad Audit" resource to retrieve statistics about user-locked data. Specifically, it performs a query operation named "Retrieve User Locked Stats," which fetches records related to locked user information based on various filtering and pagination parameters.

Typical use cases include:

  • Auditing or monitoring locked user data in an advertising system.
  • Extracting filtered subsets of locked user stats for reporting or further processing.
  • Paginating through large datasets of locked user records with sorting options.

For example, you might use this node to get all locked stats for a specific user ID, filter by certain conditions (e.g., date ranges or status), skip a number of records for paging, limit the number of results returned, and order the results by a specified field.

Properties

Name Meaning
X USER ID The unique identifier of the user whose locked stats are being retrieved.
Condition A query string to filter the results based on specific criteria (e.g., status, date).
Skip Number of records to skip, useful for pagination.
Limit Maximum number of records to return.
Order By Field name(s) to sort the results by (e.g., date, status).

Output

The node outputs JSON data containing the retrieved user locked stats matching the query parameters. The structure typically includes an array of records with fields relevant to the locked stats, such as user identifiers, lock details, timestamps, and any other metadata provided by the API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure API service to fetch the ad audit data.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authentication or data retrieval errors.
  • Invalid query condition syntax: If the condition string is malformed or uses unsupported filters, the API may return errors or empty results.
  • Pagination issues: Setting skip or limit incorrectly (e.g., negative numbers) could lead to unexpected results or errors.
  • API authentication failures: Ensure that the API key credential is correctly configured and has sufficient permissions.
  • Network or connectivity problems: Failures to reach the external API endpoint will result in errors; verify network access and endpoint availability.

Links and References

Discussion