Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Connect Secure" API to retrieve information about a specific Asset by its ID. It is useful in scenarios where you need to fetch detailed data about an asset stored or managed within the Connect Secure system, such as for auditing, reporting, or integration purposes.

For example, you might use this node to:

  • Retrieve asset details before processing or updating them in another system.
  • Fetch asset metadata to display in a dashboard.
  • Integrate asset information into automated workflows that depend on asset status or attributes.

Properties

Name Meaning
X USER ID The user identifier required for authentication or authorization in the API request.
Id The numeric identifier of the Asset to retrieve from the Connect Secure system.

Output

The node outputs JSON data representing the retrieved Asset's details. This typically includes all relevant fields returned by the Connect Secure API for the specified asset ID. The exact structure depends on the API response but generally contains asset metadata and properties.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and the provided user ID and asset ID being valid.
  • The node uses the OpenAPI specification bundled internally to define operations and properties.

Troubleshooting

  • Invalid or missing X USER ID: Ensure the user ID header is correctly set; otherwise, the API may reject the request.
  • Asset ID not found: If the asset ID does not exist, the API will likely return an error or empty response.
  • Authentication errors: Verify that the API key credential is configured properly in n8n.
  • Network issues: Confirm connectivity to the Connect Secure API endpoint.
  • Check the node’s error messages for HTTP status codes and messages to diagnose issues.

Links and References

  • Connect Secure API documentation (refer to your internal or vendor-provided docs)
  • n8n documentation on using API credentials and HTTP request nodes

Discussion