Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve bio information related to an asset. Specifically, for the "Asset Data" resource and the "Retrieve Bio Info" operation, it fetches detailed biological or user-related data by using a user identifier and an asset ID. This is useful in scenarios where you need to programmatically access bio info linked to specific assets or users, such as in digital asset management, identity verification, or personalized content delivery systems.

Properties

Name Meaning
X USER ID The User Id header value sent with the request to identify the user making the query.
Id The numeric identifier of the asset whose bio information is being retrieved.
  • X USER ID is passed as a custom HTTP header.
  • Id is used as a path or query parameter to specify which asset's bio info to retrieve.

Output

The node outputs JSON data containing the bio information associated with the specified asset ID and user. The exact structure depends on the API response but typically includes fields representing biological or user metadata.

No binary data output is indicated in the source code or properties.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the external Connect Secure service endpoint described in the bundled OpenAPI specification.
  • The node uses the @devlikeapro/n8n-openapi-node package to build its operations from the OpenAPI spec.
  • Proper configuration of the API credentials within n8n is necessary for successful requests.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure that the "X USER ID" property is provided and correctly set; 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 configured properly in n8n.
  • Network or API errors: Check connectivity to the Connect Secure API endpoint and confirm the API service status.
  • Unexpected response format: If the API changes, the node might not parse the response correctly; updating the OpenAPI spec or node version may be required.

Links and References

Discussion