AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Asset" resource to retrieve asset service information. Specifically, it performs a "Get Retrieve Asset Services" operation, which fetches details about asset services based on user-supplied criteria. This is useful in scenarios where you need to query asset-related data filtered or sorted according to specific conditions, such as retrieving all services linked to a particular user or filtering services by certain attributes.

Practical examples include:

  • Fetching all asset services associated with a given user ID.
  • Retrieving a limited number of asset services with pagination support.
  • Ordering asset services by a specified field for reporting or display purposes.

Properties

Name Meaning
X USER ID The User ID header value used to identify the user making the request (required).
Additional Query Parameters Optional parameters to refine the query:
- Condition: A query condition/filter string.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field name(s) to order the results by.

Output

The node outputs JSON data representing the retrieved asset services matching the query parameters. The structure typically includes an array of asset service objects, each containing relevant fields describing the service details. There is no indication that binary data is returned by this node.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard ConnectSecure API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled within the node for request building.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authorization or request errors. Ensure the correct user ID is provided.
  • Invalid query parameters: Providing malformed or unsupported query conditions may result in API errors or empty responses. Validate query syntax and parameter types.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful requests. Verify API endpoint accessibility and credential correctness.
  • Rate limiting or permission errors: If the API enforces rate limits or permissions, exceeding limits or lacking access rights will cause errors. Check API usage policies and credentials.

Links and References

Discussion