Trigger: Tag Removed

The Tag Removed trigger (tag.removed) fires a workflow when a tag is removed from a contact. It's the natural counterpart to "Tag Added": it lets you reverse automations or reactivate processes as soon as a contact stops belonging to a category.

When it fires

It fires as soon as the tag removal is saved on the contact, regardless of who removed it (agent, API, workflow).

Requirements

• A contact that previously had that tag assigned.

Trigger configuration

• Tag name: leave blank to fire on any removed tag, or set an exact one (e.g. "on hold") to scope the workflow.

Available variables

• $tag.id, $tag.name, $tag.removed_at
• Standard $contact.* variables

Example

A workflow triggered by tag.removed with Tag name = "on hold": when an agent removes that tag from a contact (because they're active again), the workflow re-enrolls them in the lead-nurturing sequence that had been paused.

Tips

• Use it alongside tag.added to build full enter/exit cycles for a segment (e.g. waitlist, active campaign, etc.).
• Unlike "Tag Added", this trigger doesn't offer a "once per contact" option — if you need that limit, add a condition node that checks whether it already ran before.

Troubleshooting

If the workflow doesn't fire when a tag is removed as part of a contact merge or another automation, confirm that the process which removed it actually emitted the event — some merges record the change differently than a manual removal.