Tag triggers (added / removed)
Fire automations when a tag is added to or removed from a contact.
Watch this step in the video · The palette: triggers and nodes
Tag triggers start an automation the moment a tag is added to or removed from a contact. Tags are your fast way to classify people (VIP, interested, past-due…), and these triggers turn that one click into automatic actions: route, send messages, move into a funnel or alert the team.
Available triggers
- Tag added — fires when a tag is assigned to a contact. Use Tag name to limit it to a specific tag; leave it empty to react to any.
- Tag removed — fires when a tag is taken off. Handy for reverting a state (for example, dropping someone from a sequence when they are no longer "interested").
Both expose variables like the tag ID, Name and When it was added, which you can insert into your actions.
Requirements
- A plan with Automations enabled.
- At least one tag created in the workspace.
Steps
- Open Automations and click New automation → Start from scratch.
- In the Trigger panel, open Choose how it starts and select Tag added (or Tag removed).
- In Settings, type the exact Tag name that should fire it. Leave it empty and any tag will do.
- Connect your Actions: send a template, assign to a team, log an activity or add/remove another tag.
- Insert the Tag name token from Available variables if you want to personalize the message.
- Save and click Activate.
Verify it
- Click Test and check Run history → View trace.
- Open a contact, actually add (or remove) the tag, and confirm the run shows as Completed.
If it doesn't work
- The Tag name must match the real tag exactly (case, accents and spaces count). When in doubt, leave it empty to test.
- Make sure the automation is Active.
- Remember Tag added and Tag removed are different triggers: use the right one for your case.
- Watch out for loops: if an action adds a tag that in turn fires this same flow, you can create a cycle. Use different tag names for the in and out steps.
- Seeing Paused by limit? You hit the plan's run cap.
Tips
- Use a "technical" tag (e.g.
welcome-sent) as a marker to avoid repeats. - Chain Tag added → action → another tag to build mini-funnels without touching the CRM.
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.