Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Ad Audit" resource to retrieve user event statistics. It is designed to query an API endpoint that returns analytics or audit data related to user events, filtered and paginated according to specified parameters. This node is useful in scenarios where you want to analyze user behavior, track event occurrences, or generate reports based on user activity logs.

Practical examples include:

  • Fetching event stats for a specific user to monitor their engagement.
  • Applying conditions to filter events by type, date range, or other criteria.
  • Paginating through large datasets of event records using skip and limit.
  • Sorting results by specific fields to prioritize or organize the output.

Properties

Name Meaning
X USER ID The unique identifier of the user whose event stats are being retrieved.
Condition A query condition string to filter the event stats (e.g., filtering by event type).
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return.
Order By Field name(s) to order the results by (e.g., timestamp, event type).

Output

The node outputs JSON data containing the retrieved user event statistics. Each item in the output corresponds to an event record matching the query parameters. The structure typically includes details such as event identifiers, timestamps, event types, and any other relevant metadata returned by the API.

If the API supports binary data (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON event data.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the external Connect Secure API service to fetch the Ad Audit data.
  • No additional environment variables or configurations are explicitly required beyond the API authentication.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID is required, ensure it is provided and correctly formatted; otherwise, the API will reject the request.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may cause errors or empty results.
  • Pagination issues: Setting Skip or Limit incorrectly (e.g., negative numbers) might lead to unexpected results or errors.
  • API authentication failures: Verify that the API key credential is valid and has sufficient permissions.
  • Order By field errors: Using invalid or unsupported fields in Order By can result in API errors.

Links and References

Discussion