AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Tags" resource of an API, specifically to retrieve a tag rule by its unique identifier. It is useful in scenarios where you need to fetch detailed information about a specific tag rule associated with a user, such as for auditing, display, or further processing within an automation workflow.

For example, if you manage tags for categorizing resources or users in your system, this node allows you to programmatically get the details of a particular tag rule by providing the user ID and the tag rule's ID.

Properties

Name Meaning
X USER ID The User Id header value used to identify the user context for the request.
Id The numeric identifier of the tag rule to retrieve.
  • X USER ID is passed as a custom HTTP header (X-USER-ID) in the request.
  • Id is used as a path or query parameter to specify which tag rule to fetch.

Output

The output will contain a JSON object representing the retrieved tag rule. This typically includes all the properties of the tag rule as returned by the API, such as its ID, name, conditions, actions, or other metadata defined by the service.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard ConnectSecure API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification file (openapi.json) bundled with the node for request building.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure that the "X USER ID" property is set correctly; otherwise, the API may reject the request or return unauthorized errors.
  • Invalid or non-existent Id: If the provided tag rule ID does not exist, the API will likely return a 404 error. Verify the ID before making the request.
  • Authentication errors: Confirm that the API key credential is valid and has the necessary permissions.
  • Network or connectivity issues: Check the base URL configuration and network access to the API endpoint.

Links and References

Discussion