AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve bio information for a specific asset user. It is designed to fetch detailed biometric or personal data associated with an asset by specifying the user ID and the asset's unique identifier. This node is useful in scenarios where you need to programmatically access secure bio info records, such as in security systems, identity verification workflows, or asset management platforms.

For example, you might use this node to:

  • Retrieve biometric data of a user linked to a particular asset for authentication purposes.
  • Access detailed bio info to audit or verify user credentials in a secure environment.

Properties

Name Meaning
X USER ID The User ID header value used to identify the user making the request.
Id The unique numeric identifier of the asset whose bio info is being retrieved.

Output

The node outputs JSON data containing the bio information retrieved from the API for the specified asset and user. The exact structure depends on the API response but typically includes fields related to biometric data or personal details associated with the asset.

If the API supports binary data (e.g., images or biometric templates), the node would include this in the binary output field; however, based on the provided code snippet, only JSON output is indicated.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure to authenticate requests.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building properties and handling OpenAPI specifications.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure that the "X USER ID" property is set correctly; otherwise, the API may reject the request.
  • Invalid or missing asset Id: The "Id" must be a valid number corresponding to an existing asset; incorrect values will cause errors or empty responses.
  • Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Network or API endpoint issues: Confirm the base URL is correct and the API service is reachable.
  • Unexpected API response structure: If the output JSON does not match expectations, check for API changes or consult the API documentation.

Links and References

Discussion