Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Tags, is designed to fetch a list of tags from the Connect Secure API. It allows users to query and retrieve tag data with flexible filtering, pagination, and sorting options. This operation is useful in scenarios where you need to manage or analyze tags associated with resources in Connect Secure, such as categorizing items, filtering content by tags, or integrating tag data into workflows.

Practical examples include:

  • Retrieving all tags that match a specific condition or filter.
  • Paginating through large sets of tags by skipping and limiting results.
  • Sorting tags based on certain fields to organize output.

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 which tags are retrieved (e.g., filter expressions).
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used to limit the size of the result set.
Order By Field name(s) to order the returned tags by, allowing sorted results.

Output

The node outputs JSON data representing the retrieved tags. The structure typically includes an array of tag objects matching the query parameters. Each tag object contains properties describing the tag's attributes as defined by the Connect Secure API.

If binary data were involved, it would be summarized here, but this operation deals solely with JSON tag data.

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 external dependencies beyond the API and n8n environment are needed.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X USER ID header; ensure it is provided and correct.
  • Invalid query conditions: If the Condition parameter is malformed or unsupported, the API may return errors or empty results.
  • Pagination issues: Setting Skip or Limit incorrectly might lead to unexpected subsets of data or no data.
  • API connectivity problems: Network issues or incorrect credentials will cause failures; verify API access and credentials.
  • Order By field errors: Using unsupported fields in Order By can cause errors or ignored sorting.

Links and References

Discussion