Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve statistics about a specific asset. It is useful in scenarios where users need to fetch detailed information or metrics related to an asset identified by its unique ID. For example, it can be used in workflows that monitor asset performance, generate reports, or trigger actions based on asset status.

Properties

Name Meaning
X USER ID User Id required for the request, sent as a header named X-USER-ID. This identifies the user making the request.
Id The numeric identifier of the asset whose statistics are to be retrieved.

Output

The node outputs JSON data containing the statistics of the specified asset. The exact structure depends on the Connect Secure API response but typically includes various metrics and details about the asset's status or usage. There is no indication that binary data is returned.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node expects the user to provide a valid X USER ID header value.
  • The asset ID must be provided as a number.
  • The node depends on the external Connect Secure API service being available and accessible.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests without a valid user ID header. Ensure this property is set correctly.
  • Invalid asset ID: Providing an incorrect or non-existent asset ID will likely result in an error or empty response.
  • Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate.
  • Network issues: Connectivity problems with the Connect Secure API endpoint will cause request failures.
  • Check error messages returned by the API for more specific guidance.

Links and References

  • Refer to the official Connect Secure API documentation for details on the asset statistics endpoint and response format.
  • n8n documentation on how to configure API credentials and use HTTP headers in nodes.

Discussion