Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve asset storage information. Specifically, for the "Asset Data" resource and the "Retrieve Asset Storage" operation, it fetches details about a particular asset storage entry identified by its ID. This is useful in scenarios where users need to programmatically access stored asset data within the Connect Secure system, such as integrating asset metadata retrieval into automated workflows or reporting systems.

Practical examples include:

  • Automatically fetching asset storage details when processing asset-related events.
  • Integrating asset storage data into dashboards or other applications.
  • Validating asset existence or properties before further processing.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Id Numeric identifier of the asset storage entry to retrieve.

Output

The node outputs JSON data representing the retrieved asset storage information corresponding to the provided asset ID. The exact structure depends on the Connect Secure API response but typically includes fields describing the asset's storage details.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and properly configured.
  • Uses the @devlikeapro/n8n-openapi-node package and OpenAPI specification (openapi.json) bundled with the node for request construction and parsing.

Troubleshooting

  • Missing or invalid X USER ID: Ensure the "X USER ID" property is set correctly; otherwise, the API may reject the request.
  • Invalid or missing asset ID: The "Id" property must be a valid number corresponding to an existing asset storage entry.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Network or API errors: Check connectivity to the Connect Secure API endpoint and confirm the service is operational.
  • Unexpected API responses: If the API schema changes, the node might fail to parse responses correctly; updating the OpenAPI spec or node version may be necessary.

Links and References

Discussion