Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Asset Video Info, is designed to fetch video-related metadata or information about assets from a remote API. It is useful in scenarios where users need to query and retrieve detailed video asset data based on specific conditions, pagination controls, and sorting preferences. For example, a media management workflow could use this node to pull video asset details filtered by certain criteria (e.g., date range, tags) and then process or display that data downstream.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes in the API request headers.
Condition Query condition string to filter which asset video info records to retrieve.
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return.
Order By Field(s) to order the results by, controlling the sort order of returned records.

Output

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

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • The node depends on the external Connect Secure API service endpoint defined in its configuration.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is mandatory, omitting it or providing an incorrect value will likely cause authentication errors. Ensure the correct user ID is supplied.
  • Invalid query conditions: Malformed or unsupported query strings in the "Condition" property may result in empty responses or API errors. Validate the query syntax according to the API documentation.
  • Pagination issues: Setting "Skip" or "Limit" incorrectly (e.g., negative numbers) might cause unexpected results or errors.
  • Order By field errors: Using invalid or unsupported fields in "Order By" can lead to sorting failures or ignored parameters.
  • API connectivity problems: Network issues or incorrect API credentials will prevent successful data retrieval.

Links and References

  • Refer to the Connect Secure API documentation for detailed information on query conditions, supported fields, and response formats.
  • n8n documentation on HTTP Request node for understanding how routing and headers work in custom nodes.

Discussion