AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Asset Data" resource to retrieve information about a specific asset using an unquoted service endpoint. It is designed to fetch detailed data for a given asset identified by its unique ID. This operation is useful in scenarios where you need to programmatically access asset details, such as integrating asset management systems, automating reporting, or synchronizing asset data across platforms.

For example, you might use this node to:

  • Retrieve asset details before performing updates or audits.
  • Fetch asset information to display in dashboards or reports.
  • Integrate asset data retrieval into workflows that trigger based on asset status or attributes.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes.
Id Numeric identifier of the asset to retrieve.
  • X USER ID is passed as a header in the request and must be provided.
  • Id specifies which asset's data to retrieve.

Output

The node outputs JSON data representing the retrieved asset information. The exact structure depends on the API response but typically includes fields describing the asset's properties, status, and metadata.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication (referred generically as an API authentication token).
  • Depends on the base URL configured in the node credentials to connect to the AvantGuard ConnectSecure API.
  • Uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure the "X USER ID" property is set correctly; otherwise, the API may reject the request.
  • Invalid or missing asset Id: The "Id" property must be a valid number corresponding to an existing asset.
  • Authentication errors: Verify that the API authentication token is correctly configured in the node credentials.
  • Network or connectivity issues: Confirm the base URL is reachable and correct.
  • Unexpected API responses: Check if the API has changed or if additional permissions are required.

Links and References

Discussion