Condition: contact has tag
How to use the Contact has tag condition to route the flow with the any, all and none operators.
Watch this step in the video · Contact has tag
What it is and when to use it
The Contact has tag condition (contact_has_tag) checks the contact's tags and routes the flow based on which ones they have. It's perfect for segmentation: for example, treating vip contacts differently, skipping steps for those already tagged customer, or filtering out anyone tagged do-not-contact. You'll find it in the Conditions section of the palette (tag icon).
Requirements
- Tags created in the workspace, or the exact name of a tag that gets created dynamically.
- A workflow where the contact is in context (most triggers provide it).
Steps
- In the Workflows editor, drag the Contact has tag node onto the canvas.
- In the inspector choose the Operator, which defines how the selected tags are evaluated:
- Has at least one (any): passes if the contact has one or more of the tags.
- Has all (all): passes only if they have all the tags.
- Has none (none): passes if they have none of the tags.
- Under Tags, select one or more tags from the workspace.
- If the tag is created dynamically (by another workflow), use the Or tag by name (legacy) field and type the exact name, for example
vip. If you fill both, the selected tags take precedence. - Connect the Yes/No outputs to the following nodes.
Verification
Test with one contact who has the tag and one who doesn't. Check the workflow's run history to see which output each took. A contact's tags are visible on their record under Contacts.
If it doesn't work
- Everyone exits through "No": confirm the contact actually has the tag on their record and that it's the same one you selected. If you use the legacy name, watch capitalization and accents: it must match exactly.
- A new tag isn't recognized: if the tag is created by an earlier node in the same flow, use the Or tag by name field with the exact name, since it may not be in the workspace list yet.
- The node isn't in the palette: make sure you're in the workflow editor and in the Conditions section.
Tips
- To exclude contacts (blocklist) use the none operator with the
do-not-contacttag. - Combine this condition with Add tag / Remove tag to build self-managing lifecycle flows.
Related articles
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.