AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to retrieve records from the "Asset" resource using a "Get Retrieve Records" operation. It allows users to fetch asset data with optional filtering, pagination, and sorting capabilities. This node is beneficial in scenarios where you need to programmatically access asset information stored in an external system, such as inventory management, asset tracking, or reporting workflows.

Practical examples include:

  • Fetching a list of assets that meet specific conditions (e.g., assets located in a certain region).
  • Retrieving a limited number of asset records for display or further processing.
  • Sorting assets by a particular field like creation date or asset name.

Properties

Name Meaning
X USER ID User identifier required for authentication or scoping the request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A query condition string to filter records.
- 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 asset records. The structure typically includes an array of asset objects matching the query criteria. Each object contains fields relevant to the asset's details as provided by the external service.

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

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • Needs the base URL of the API endpoint configured in the credentials.
  • Depends on 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: The node requires a valid user ID header; ensure this is provided and correct.
  • Query parameter errors: Invalid values for condition, skip, limit, or order_by may cause API errors. Validate these inputs carefully.
  • Authentication failures: Check that the API key credential is correctly set up and has necessary permissions.
  • Empty results: If no records are returned, verify the query conditions and pagination parameters.
  • API connectivity issues: Ensure the base URL is reachable and the network connection is stable.

Links and References

  • OpenAPI Specification (bundled with the node)
  • Documentation for the external Asset API (not included here; refer to your API provider)

Discussion