Check Tag - Captain icon

Check Tag - Captain

Node for Tag Checking

Check Tag - Captain

AI-generated

Overview

This node checks if users have a specific tag by sending their user IDs and the tag name to an external API. It is useful in scenarios where you need to filter or route data based on user tags, such as marketing segmentation or access control. For example, it can be used to verify if users belong to a certain group before proceeding with further workflow steps.

Use Case Examples

  1. Check if users have a 'premium' tag to grant access to exclusive content.
  2. Filter users who have a 'newsletter' tag to send targeted emails.

Properties

Name Meaning
Tag Name The name of the tag to check for each user.
Users Optional list of users to check. If left blank, users are taken from the previous node's output.

Output

JSON

  • json - Each object contains user data and the tag check result. The output is split into two arrays: one for users who have the tag (true output) and one for users who do not (false output).

Dependencies

  • Requires an API key stored in the environment variable UNEXO_API_KEY for authorization.
  • Requires the environment variable CDP_URL to specify the base URL of the external API.

Troubleshooting

  • Common issues include network errors or invalid API keys causing request failures. The node retries the request up to 3 times with a 2-second delay between attempts.
  • If the API URL or key is not set correctly in environment variables, the request will fail.
  • Error messages related to HTTP request failures indicate connectivity or authorization problems. Verify environment variables and network access.

Discussion