AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve notification tickets related to assets. Specifically, the "Get Retrieve Notification Tickets View" operation fetches a filtered and optionally paginated list of notification tickets for a user. This is useful in scenarios where you want to monitor or audit asset-related notifications, track issues, or integrate ticket data into workflows for alerting or reporting.

Practical examples include:

  • Fetching recent notification tickets assigned to a specific user.
  • Filtering tickets based on conditions such as status or priority.
  • Paginating through large sets of tickets by skipping and limiting results.
  • Ordering tickets by date or other fields.

Properties

Name Meaning
X USER ID The User ID header value identifying the user whose notification tickets are being fetched. This is required.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition 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 notification tickets view. Each item in the output corresponds to a notification ticket with its associated details as returned by the API. The exact structure depends on the API response but typically includes ticket identifiers, statuses, timestamps, and related metadata.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure to authenticate requests.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • Uses the @avantguardllc/n8n-openapi-node package internally to build request properties from the OpenAPI specification.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is set up properly and has necessary permissions.
  • Query parameter issues: Invalid values for condition, skip, limit, or order_by may cause API errors; validate these inputs.
  • Network or connectivity problems: Ensure the base URL is reachable and no firewall or proxy blocks the connection.
  • Empty results: If no tickets are returned, check the filter conditions and user ID correctness.

Links and References

Discussion