AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Company" resource to retrieve audit data related to ADAudit. It is designed to fetch audit logs or records, which can be useful for monitoring user activities, compliance tracking, or security auditing within a company environment. Typical use cases include retrieving filtered audit logs based on conditions, paginating through large sets of audit data, and ordering results for reporting or analysis.

Properties

Name Meaning
X USER ID The User Id header value required for authentication or identification in 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 ADAudit records from the Company resource. Each item in the output corresponds to an audit record matching the query parameters. The structure typically includes fields relevant to audit logs such as timestamps, user actions, affected resources, and other metadata. There is no indication that binary data is returned by this node.

Dependencies

  • Requires an API key credential for authentication.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • Depends on the external AvantGuard ConnectSecure service endpoint to fetch audit data.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid User Id header; ensure it is provided and correct.
  • API connection errors: Verify that the API base URL and credentials are correctly set up.
  • Query parameter issues: Invalid or malformed query conditions may result in empty or error responses; check syntax and values.
  • Pagination problems: Using skip and limit incorrectly might cause unexpected results; ensure these values are logical.
  • Order By field errors: Ordering by non-existent fields may cause errors or ignored parameters.

Links and References

Discussion