Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve statistics about assets. Specifically, the "Retrieve Asset Stats" operation fetches asset-related data based on user-defined query parameters such as filtering conditions, pagination controls, and sorting preferences. This node is useful in scenarios where users need to analyze or report on asset metrics, filter assets by specific criteria, or integrate asset statistics into automated workflows.

Practical examples include:

  • Fetching asset stats for a particular user to monitor usage or performance.
  • Retrieving a limited set of asset records sorted by a specific field for reporting dashboards.
  • Applying complex query conditions to extract targeted asset information.

Properties

Name Meaning
X USER ID User Id header value to identify the user making the request.
Condition Query condition string to filter which asset stats are retrieved.
Skip Number of records to skip (for pagination).
Limit Maximum number of records to return.
Order By Field name(s) to order the results by.

Output

The node outputs JSON data containing the retrieved asset statistics matching the query parameters. The structure typically includes an array of asset stat objects, each representing individual asset metrics or details as returned by the Connect Secure API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the external Connect Secure service being accessible.
  • Uses the @devlikeapro/n8n-openapi-node package and OpenAPI specification bundled within the node for request construction.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this property is correctly set.
  • Invalid query conditions: Malformed or unsupported query strings may cause errors or empty results.
  • Pagination issues: Setting skip or limit incorrectly might result in unexpected subsets of data.
  • Authentication failures: Verify that the API key credential is configured properly and has necessary permissions.
  • Network or API errors: Check connectivity and API status if requests fail unexpectedly.

Links and References

Discussion