AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Ad Audit" resource to retrieve statistics about user lock status. Specifically, the "Get Retrieve User Locked Stats" operation fetches data related to how users are locked or restricted within an advertising audit context. This can be useful for monitoring user access issues, auditing security events, or analyzing user behavior in ad management systems.

Practical examples include:

  • Fetching a list of locked users to investigate potential security breaches.
  • Retrieving lock statistics filtered by certain conditions or sorted by specific fields.
  • Paginating through large datasets of user lock records for reporting purposes.

Properties

Name Meaning
X USER ID The unique identifier of the user for whom the locked stats are being retrieved.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition for the query.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The output JSON contains the retrieved user locked statistics data from the Ad Audit system. It typically includes details such as user lock counts, timestamps, reasons for locks, and other relevant metadata depending on the API response structure.

If the node supports binary data output, it would represent any associated files or attachments related to the user lock stats, but based on the provided code and properties, this node primarily outputs JSON data.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard ConnectSecure service.
  • Needs the base URL of the API endpoint configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building request properties and handling OpenAPI specifications.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID is required, ensure it is provided and correctly formatted; otherwise, the API call will fail.
  • Incorrect query parameters: Invalid values for condition, skip, limit, or order_by may cause errors or unexpected results.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network or connectivity issues: Ensure the base URL is reachable and the network allows outbound requests to the API.

Common error messages might include unauthorized access, bad request due to malformed query parameters, or not found if the user ID does not exist.

Links and References

Discussion