AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Asset Data" resource to retrieve information about a specific asset port. It is designed to fetch detailed data for an asset port identified by its unique ID. This functionality is useful in scenarios where users need to programmatically access asset port details, such as in network management, inventory tracking, or integration workflows that require asset port metadata.

For example, a user might use this node to automatically pull asset port configurations into a monitoring system or to synchronize asset port data between different platforms.

Properties

Name Meaning
X USER ID The user identifier required for authentication or authorization in the API request.
Id The unique numeric identifier of the asset port to retrieve.

Output

The node outputs JSON data representing the retrieved asset port's details. The structure of this JSON corresponds to the asset port's properties as defined by the external API schema. This typically includes fields such as port identifiers, status, configuration, and related metadata.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication (referred generically as an API authentication token).
  • Depends on an external REST API endpoint configured via the node's base URL credential.
  • Uses HTTP headers including a custom header for user identification (X-USER-ID).

Troubleshooting

  • Missing or invalid X USER ID header: Ensure the user ID is correctly provided; otherwise, the API may reject the request.
  • Invalid or missing asset port Id: The node requires a valid numeric ID; providing zero or negative values may cause errors.
  • API connectivity issues: Verify the base URL and credentials are correctly set up in n8n.
  • Unexpected API responses: Check if the asset port ID exists and the user has permission to access it.

Links and References

  • Refer to the external API documentation for "Asset Data" and asset port retrieval endpoints for detailed response schemas and error codes.
  • n8n documentation on setting up API credentials and HTTP request nodes for further customization.

Discussion