AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve system event data related to assets. Specifically, the "Get Retrieve System Events View" operation fetches system events filtered and paginated according to user-supplied parameters. This is useful for monitoring asset-related activities, auditing changes, or integrating system event logs into workflows for alerting or reporting.

Practical examples include:

  • Fetching recent system events for a specific user to audit their actions.
  • Retrieving a limited number of system events ordered by timestamp for dashboard display.
  • Applying query conditions to filter events by type or status.

Properties

Name Meaning
X USER ID The User ID header value identifying the user making the request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Query condition/filter string.
- 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 system events from the API. Each item in the output corresponds to a system event record matching the query parameters. The structure typically includes event details such as timestamps, event types, user information, and other metadata relevant to asset system events.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard ConnectSecure API.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for OpenAPI integration.

Troubleshooting

  • Missing or invalid X USER ID: The node requires the "X USER ID" header; ensure this is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is valid and has necessary permissions.
  • Query parameter issues: Invalid or malformed query conditions may cause API errors; validate query syntax.
  • Pagination problems: Using skip and limit incorrectly might result in empty or incomplete data sets.
  • Network or connectivity errors: Ensure the base URL is reachable and network settings allow outbound requests.

Links and References

Discussion