Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Asset Ports, is designed to fetch port information related to assets from the Connect Secure API. It allows users to query asset ports with flexible filtering, pagination, and sorting options. This is useful in scenarios where you need detailed network or hardware port data associated with specific assets, such as in IT asset management, network inventory audits, or infrastructure monitoring.

Practical examples include:

  • Retrieving all ports for a given asset filtered by certain conditions.
  • Paginating through large sets of asset port data.
  • Sorting asset ports by specific fields like port name or status.

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 the asset ports returned (e.g., "status='active'").
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return.
Order By Field(s) to order the results by (e.g., "portName asc").

Output

The node outputs JSON data representing the retrieved asset ports. Each item in the output corresponds to an asset port record fetched from the API, containing details such as port identifiers, names, statuses, and other relevant metadata depending on the API response schema.

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 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 property is malformed, the API may reject the request. Validate the query syntax according to the API documentation.
  • Pagination issues: Setting Skip or Limit incorrectly might result in empty responses or missing data.
  • Order By errors: Using unsupported fields in Order By can cause API errors; verify allowed fields.
  • API connectivity problems: Network issues or incorrect credentials will prevent data retrieval.

Links and References

Discussion