Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Asset Data" resource of the Connect Secure API to retrieve asset interface information. It allows users to query asset data with flexible filtering, pagination, and sorting options. This is useful in scenarios where you need to fetch specific asset details from a large dataset, such as retrieving asset interfaces based on certain conditions or ordering them by particular fields.

Practical examples include:

  • Fetching all asset interfaces that meet a specific condition (e.g., assets of a certain type or status).
  • Paginating through asset records by skipping a number of entries and limiting the result count.
  • Ordering the retrieved asset interfaces by a specified field for easier analysis or display.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification purposes in the API call.
Condition Query condition string to filter the asset interfaces returned by the API.
Skip Number of records to skip, used 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 representing the retrieved asset interfaces matching the query parameters. The structure corresponds to the API response for asset interfaces, typically an array of objects each describing an asset interface's 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 properly configured.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X USER ID header; ensure it is provided and correct.
  • Invalid query condition syntax: If the Condition parameter is malformed, the API may return errors or no data.
  • Pagination issues: Setting Skip or Limit incorrectly might result in empty responses or unexpected data slices.
  • Ordering errors: Using invalid field names in Order By can cause the API to reject the request or ignore the ordering.
  • API connectivity problems: Network issues or incorrect credentials will prevent successful data retrieval.

To resolve these, verify input values, check API documentation for valid query formats, and confirm network and credential configurations.

Links and References

  • Connect Secure API Documentation (refer to official docs for detailed query syntax and asset interface schema)
  • n8n Documentation on HTTP Request nodes and custom node development (for understanding routing and property usage)

Discussion