Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve asset data based on user-defined query parameters. It is useful for scenarios where you need to fetch and process asset information from a secure system, such as inventory management, asset tracking, or reporting workflows. For example, you can use this node to pull a filtered list of assets owned by a specific user, limit the number of results returned, or order the assets by certain fields.

Properties

Name Meaning
X USER ID The User Id header value required for authentication or identification in the API call.
Condition A query condition string to filter which assets are retrieved (e.g., status='active').
Skip Number of records to skip in the result set, useful for pagination.
Limit Maximum number of asset records to return.
Order By Field(s) by which to order the returned assets (e.g., "name asc", "date desc").

Output

The node outputs JSON data representing the retrieved assets. Each item in the output corresponds to an asset record matching the query conditions. The structure depends on the API response but typically includes asset properties such as IDs, names, statuses, and other metadata. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure API service being accessible.
  • No additional environment variables or configurations are explicitly required beyond the API credential.

Troubleshooting

  • Common issues:
    • Missing or invalid User Id header (X USER ID) may cause authentication failures.
    • Incorrect query conditions might result in empty responses or errors.
    • Pagination parameters (skip and limit) must be non-negative integers; invalid values could cause request errors.
  • Error messages:
    • Authentication errors usually indicate missing or incorrect API credentials or headers.
    • Query parameter errors suggest malformed or unsupported filter expressions.
  • Resolutions:
    • Verify the User Id is correctly provided and authorized.
    • Check the syntax and validity of the condition string.
    • Ensure numeric inputs for skip and limit are valid numbers.

Links and References

Discussion