AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation retrieves tags from the AvantGuard ConnectSecure API. It is useful when you want to fetch a list of tags associated with your user account or system, potentially filtered or sorted according to specific criteria. Typical use cases include managing or displaying tags in dashboards, syncing tag data with other systems, or performing analytics on tagged items.

For example, you might use this node to:

  • Retrieve all tags for a particular user.
  • Fetch a limited number of tags sorted by creation date.
  • Skip a certain number of tags and retrieve the next batch for pagination purposes.

Properties

Name Meaning
X USER ID The User Id header value used to identify the user whose tags are being retrieved.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A query condition string to filter tags.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field name to order the results by.

Output

The output contains a JSON array of tag objects retrieved from the API. Each object represents a tag with its associated properties as returned by the backend service.

If the node supports binary data output (not indicated here), it would typically represent attachments or media related to tags, but this operation focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard ConnectSecure API.
  • The base URL for the API must be configured in the node credentials.
  • The node uses HTTP headers and query parameters to communicate with the API endpoint.

Troubleshooting

  • Missing or invalid User Id: If the X USER ID header is not provided or incorrect, the API may reject the request or return no data. Ensure the User Id is correct and supplied.
  • Invalid query parameters: Providing malformed or unsupported query conditions can cause errors or empty responses. Validate query syntax and parameter values.
  • API authentication errors: If the API key credential is missing or invalid, authentication will fail. Verify that the API key is correctly set up in n8n credentials.
  • Network issues: Connectivity problems or incorrect base URL configuration can prevent successful API calls. Check network access and credential settings.

Links and References

Discussion