Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Asset Storages, is designed to fetch asset storage data from the Connect Secure API. It allows users to query and retrieve a list of asset storages with flexible filtering, pagination, and sorting options. This is useful in scenarios where you need to programmatically access or analyze asset storage information, such as inventory management, auditing, or integration with other systems.

Practical examples include:

  • Retrieving all asset storages that meet certain conditions (e.g., location, status).
  • Paginating through large sets of asset storage records.
  • Sorting asset storages by specific fields for reporting purposes.

Properties

Name Meaning
X USER ID User Id required for authentication, passed as a header named X-USER-ID.
Condition Query condition string to filter asset storages based on specified criteria.
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used to limit the result set size.
Order By Field(s) to order the results by, allowing sorted output of asset storages.

Output

The node outputs JSON data representing the retrieved asset storages. Each item in the output corresponds to an asset storage record matching the query parameters. The structure typically includes fields describing the asset storage details as returned by the Connect Secure API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Authentication errors: Ensure the provided user ID header (X-USER-ID) and API credentials are correct and have sufficient permissions.
  • Empty results: Verify the condition query parameter syntax and values; incorrect filters may yield no data.
  • Pagination issues: When using skip and limit, ensure values are within valid ranges and consistent with the total available records.
  • Sorting errors: Confirm that the order_by field names match those supported by the API to avoid invalid query errors.

Links and References

Discussion