AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve detailed views of assets. Specifically, the "Get Retrieve Asset View" operation fetches asset information based on user identification and optional query parameters. This is useful in scenarios where you need to programmatically access asset data for monitoring, reporting, or integration with other systems.

Practical examples include:

  • Fetching a list of assets owned or accessible by a specific user.
  • Applying filters or sorting to asset data to generate customized reports.
  • Paginating through large sets of asset records by skipping and limiting results.

Properties

Name Meaning
X USER ID The User Id header value used to identify the user making the request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition as a 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 asset view(s). The structure corresponds to the API response for asset details, which typically includes asset properties such as identifiers, metadata, status, and related information.

If binary data were involved, it would be summarized here; however, this node focuses on JSON asset data only.

Dependencies

  • Requires an API key credential for authenticating with 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 the bundled OpenAPI specification (openapi.json) for request building.

Troubleshooting

  • Missing or invalid X USER ID: The request will fail if the required user ID header is not provided or incorrect. Ensure the "X USER ID" property is set correctly.
  • API authentication errors: Verify that the API key credential is valid and has necessary permissions.
  • Query parameter issues: Invalid values for condition, skip, limit, or order_by may cause the API to reject the request. Double-check these parameters for correctness.
  • Network or connectivity problems: Confirm that the base URL is reachable from your n8n instance.

Common error messages usually relate to authentication failures, missing headers, or invalid query parameters. Reviewing the API documentation and ensuring correct input values typically resolves these issues.

Links and References

Discussion