Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Asset View, is designed to fetch a filtered and paginated view of assets from an external service via its API. It allows users to specify query conditions, pagination controls (skip and limit), and sorting preferences to tailor the asset data retrieved. This is useful in scenarios where you need to programmatically access subsets of asset data for reporting, monitoring, or integration with other systems.

Practical examples:

  • Retrieving a list of assets that meet certain criteria (e.g., assets created after a specific date).
  • Paginating through large sets of asset records by skipping a number of entries and limiting the result size.
  • Sorting assets by a particular field such as creation date or asset name.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes in the API request header.
Condition Query condition string to filter the assets 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, controlling the sort order of the returned assets.

Output

The node outputs JSON data representing the asset view retrieved from the API. The structure typically includes an array of asset objects matching the query parameters. Each asset object contains fields describing the asset's properties as defined by the external service.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external Connect Secure API.
  • The node depends on the external Connect Secure API endpoint that supports querying asset views with filtering, pagination, and ordering.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID in the request header. Ensure this property is set correctly; otherwise, the API may reject the request.
  • Invalid query condition syntax: If the condition string is malformed or unsupported by the API, the request may fail or return no results.
  • Pagination issues: Setting skip or limit incorrectly (e.g., negative numbers) might cause errors or unexpected results.
  • API authentication errors: Verify that the API key credential is configured properly and has sufficient permissions.
  • Empty responses: Could indicate no assets match the query condition or incorrect filtering parameters.

Links and References

  • Refer to the official Connect Secure API documentation for details on the asset view endpoint, supported query parameters, and authentication requirements.
  • n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.

Discussion