Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Asset Data" resource to retrieve asset metadata (Msdt). It is designed to query an external API endpoint that provides detailed information about assets based on specified conditions and pagination parameters. This node is useful in scenarios where users need to fetch filtered lists of asset data, such as inventory management, asset tracking, or reporting systems.

For example, a user might want to retrieve all assets belonging to a specific category or location, skip a certain number of records for pagination, limit the number of results returned, or order the results by a particular field.

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 data results based on specific criteria.
Skip Number of records to skip, used for pagination to offset the starting point of results.
Limit Maximum number of records to return in the response, controlling page size.
Order By Field name(s) to order the results by, allowing sorting of the returned asset data.

Output

The node outputs JSON data containing the retrieved asset metadata matching the query parameters. The structure typically includes an array of asset objects with their respective fields as provided by the external API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • Depends on the external Connect Secure API service to fetch asset metadata.
  • No additional environment variables or configurations are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: If the "X USER ID" header is not provided or incorrect, the API may reject the request. Ensure this property is set correctly.
  • Invalid query conditions: Malformed or unsupported query strings in the "Condition" property can cause errors or empty results. Validate the query syntax according to the API documentation.
  • Pagination issues: Setting "Skip" or "Limit" to inappropriate values (e.g., negative numbers) may lead to unexpected behavior or errors.
  • Ordering errors: Using invalid field names in "Order By" could result in API errors or unsorted data.
  • API connectivity: Network issues or invalid API credentials will prevent successful data retrieval. Verify credentials and network access.

Links and References

  • Refer to the Connect Secure API documentation for details on query syntax, supported fields, and authentication requirements.
  • n8n documentation on how to configure API credentials and use HTTP headers in nodes.

Discussion