AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to retrieve asset data from an external service via an API. It allows users to fetch a list of assets with optional filtering, pagination, and sorting capabilities. This functionality is useful in scenarios where you need to integrate asset management data into your workflows, such as inventory tracking, reporting, or synchronization with other systems.

For example, you might use this node to:

  • Retrieve all assets belonging to a specific user.
  • Fetch a limited number of assets sorted by a particular field.
  • Apply custom query conditions to filter assets based on certain criteria.

Properties

Name Meaning
X USER ID The User ID for whom the assets are being retrieved. This is required and sent as a header.
Additional Query Parameters Optional parameters to refine the asset retrieval:
- Condition: A query condition string to filter results.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field name(s) to sort the results by.

Output

The node outputs JSON data representing the retrieved assets. Each item in the output corresponds to an asset object returned by the external API. The structure of each asset object depends on the API's response schema but typically includes asset details such as identifiers, attributes, and metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The base URL for the API must be configured in the node credentials.
  • The node sends requests with headers including Accept: application/json and Content-Type: application/json.
  • The X USER ID header must be provided to specify the user context for asset retrieval.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests without a valid user ID. Ensure this property is set correctly.
  • Incorrect query parameters: Invalid values for condition, skip, limit, or order_by may cause errors or unexpected results. Validate these inputs before execution.
  • Authentication errors: If the API key or base URL is misconfigured, the node will fail to connect. Verify credentials and endpoint settings.
  • Empty results: If no assets match the query conditions, the output will be empty. Adjust filters or check data availability.

Links and References

  • Refer to the external API documentation for detailed information on asset fields, query syntax, and supported operations.
  • n8n documentation on HTTP Request nodes and custom node development for further customization options.

Discussion