AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Tags" resource to retrieve tag rules based on specified criteria. It is useful in scenarios where you need to fetch metadata or tagging rules associated with users or entities, such as filtering tags by conditions, paginating results, or ordering them. For example, a user might want to retrieve all tag rules that apply to a specific user ID, limit the number of returned rules for performance reasons, or sort them by creation date.

Properties

Name Meaning
X USER ID The User ID for which the tag rules are being retrieved. This is required and sent as a header named X-USER-ID.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A string to filter the tag rules.
- 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 node outputs JSON data containing the retrieved tag rules matching the query parameters. The structure typically includes an array of tag rule objects, each representing a rule with its properties as defined by the external API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication to the external service.
  • Needs the base URL of the API configured in the credentials.
  • The node uses HTTP headers and query parameters to communicate with the API endpoint.

Troubleshooting

  • Missing or invalid X USER ID header: The request will fail if the required user ID header is not provided or is incorrect. Ensure the "X USER ID" property is set correctly.
  • Invalid query parameters: Providing unsupported or malformed query parameters may cause errors or unexpected results. Validate the condition syntax and numeric values for skip and limit.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful requests. Verify API endpoint accessibility and credential correctness.
  • Empty results: If no tag rules match the query, the output will be empty. Adjust query parameters to broaden the search.

Links and References

  • Refer to the external API documentation for detailed information about tag rules, supported query parameters, and response formats.
  • n8n documentation on how to configure HTTP headers and query parameters in nodes.

Discussion