Check Tag - UNEXO icon

Check Tag - UNEXO

Node for Tag Checking

Overview

This node, named "Check Tag - UNEXO," is designed to check whether specific users have a particular tag assigned to them. It takes user data as input and verifies the presence of a given tag for each user by making an API request to an external service. This node is useful in scenarios where workflows need to branch or filter based on user tagging status, such as targeted marketing campaigns, user segmentation, or access control.

For example, you might use this node to:

  • Identify which users have been tagged as "premium" customers.
  • Filter out users who do not have a specific tag before sending notifications.
  • Trigger different workflow paths depending on tag presence.

Properties

Name Meaning
Users A string representing users to check. Leave blank to use users from the previous node.
Tag Name The name of the tag to check for among the specified users.

Output

The node outputs two separate streams:

  1. True output: Contains users who have the specified tag. Each item includes the original user data under the json property.
  2. False output: Contains users who do not have the specified tag, also with their original data under the json property.

The output JSON structure for each user includes at least the fields passed from the input, typically including user identifiers and any associated metadata.

No binary data is produced by this node.

Dependencies

  • Requires an environment variable CDP_URL that specifies the base URL of the external API endpoint.
  • Requires an environment variable UNEXO_API_KEY used as a Bearer token for authorization when calling the external API.
  • The node makes a POST HTTP request to the /api/tags/hasTagUsers endpoint of the configured service.

Troubleshooting

  • Missing or invalid environment variables: If CDP_URL or UNEXO_API_KEY are not set or incorrect, the HTTP request will fail. Ensure these are properly configured in your n8n environment.
  • Empty or malformed user data: If the input data does not contain expected user identifiers (anonymousIds), the node may send incomplete requests or fail. Verify that the input data structure matches expectations.
  • API errors: The external API might return errors due to network issues, invalid tokens, or server problems. Check the API response and logs for details.
  • Empty tag name: Providing an empty tag name will likely cause the API call to be ineffective or rejected. Always specify a valid tag name.

Links and References

  • No direct links available from the source code. For more information, consult the documentation of the external API service referenced by CDP_URL.

Discussion