Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Ad Audit" resource to retrieve user-enabled statistics. Specifically, it fetches data related to user activity or settings that have been enabled, allowing users to query and analyze audit information for a given user ID. This is useful in scenarios where you want to monitor or report on user-specific audit data, such as tracking feature usage, compliance checks, or system access logs.

For example, you might use this node to:

  • Retrieve audit stats for a specific user to verify which features they have enabled.
  • Query audit records with conditions to filter relevant data.
  • Paginate through large sets of audit data using skip and limit parameters.
  • Sort the results based on certain fields.

Properties

Name Meaning
X USER ID The unique identifier of the user whose enabled stats are being retrieved.
Condition A query condition string to filter the audit records returned by the API.
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return.
Order By Field(s) by which to order the returned records.

Output

The node outputs JSON data containing the retrieved user-enabled audit statistics. The structure typically includes an array of audit records matching the query parameters (condition, skip, limit, order_by). Each record represents a user-enabled stat entry with its associated details.

No binary data output is indicated by the source code or properties.

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 audit data.
  • Proper configuration of the API credentials within n8n is necessary for successful operation.

Troubleshooting

  • Missing or invalid User ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or data retrieval errors.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may result in empty responses or API errors.
  • Pagination issues: Setting Skip or Limit incorrectly (e.g., negative numbers) could lead to unexpected results or errors.
  • API authentication failures: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Order By field errors: Using invalid or unsupported fields in Order By may cause the API to reject the request.

Links and References

  • No direct links provided in the source code.
  • Refer to the Connect Secure API documentation for detailed information on query syntax, available fields, and authentication setup.

Discussion