Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Asset" resource of the Connect Secure API to retrieve records based on specified query parameters. It is useful for scenarios where you need to fetch filtered, paginated, and ordered lists of assets from the Connect Secure system. For example, you might use it to get all assets belonging to a particular user, or to retrieve a subset of assets matching certain conditions for reporting or further processing.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Condition Query condition string to filter which asset records to retrieve.
Skip Number of records to skip (offset) for pagination purposes.
Limit Maximum number of records to return.
Order By Field(s) by which to order the returned asset records.

Output

The node outputs JSON data containing the retrieved asset records matching the query parameters. The structure corresponds directly to the API response for asset retrieval, typically an array of asset objects with their properties. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and properly configured.
  • No additional environment variables or external services are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may result in API errors or empty results.
  • Pagination issues: Setting Skip or Limit incorrectly (e.g., negative numbers) could lead to unexpected results or errors.
  • Order By field errors: Specifying fields not supported by the API for ordering may cause failures.
  • To resolve these, verify the correctness of input values and ensure the API credentials have sufficient permissions.

Links and References

  • Connect Secure API documentation (refer to official docs for details on asset retrieval endpoints and query syntax).
  • n8n documentation on creating and using HTTP Request nodes and custom API integrations.

Discussion