AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the Audit Log resource of an external service, specifically to retrieve audit log entries. It is useful for scenarios where you need to monitor or analyze user activities, system events, or changes recorded in audit logs. For example, security teams can use it to track access patterns or detect suspicious behavior by fetching filtered audit records.

Properties

Name Meaning
X USER ID The User ID header value required to authenticate or identify the user making the request.
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 node outputs JSON data representing the retrieved audit log entries. Each entry typically contains details about a specific audit event such as timestamps, user actions, affected resources, and other metadata depending on the external service's audit log schema.

If the node supports binary data output, it would represent attachments or files related to audit logs, but based on the provided code and properties, the output is purely JSON.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • Needs the base URL of the external service configured in credentials.
  • Depends on the external service's Audit Log API endpoint to fetch data.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid User ID header; ensure this is correctly set.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Query parameter issues: Incorrectly formatted conditions or unsupported query parameters may cause errors; validate query syntax.
  • Network or connectivity problems: Ensure the base URL is reachable from n8n and no firewall blocks exist.
  • Empty results: If no audit logs are returned, check if the query filters are too restrictive or if there are no matching records.

Links and References

  • Refer to the external service’s official Audit Log API documentation for detailed information on available fields, query parameters, and response structure.
  • n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.

Discussion