When it fires
The trigger fires immediately when:- A tag is added to a contact (manually, via API, or from another workflow)
- A tag is removed from a contact
Configuration
Tag event
Choose the event type:
You can create separate workflows for additions and removals, or use a single workflow with a Condition to branch.
Tag filter
Select which tags should trigger the workflow:Examples
Only fire on “hot-lead” tag:- Event: Tag Added
- Tag: Select “hot-lead” from dropdown
- Event: Tag Removed
- Tag: Leave empty (matches all)
- Event: Tag Added
- Tags: Select “interested”, “qualified”, “ready-to-buy”
Data available
Deduplication
Uses the contact ID + tag ID as the dedup key. Default window: 1 minute. If the same tag is toggled on and off quickly, only the first event triggers the workflow.Use case examples
Start outreach when tagged “hot lead”
A sales rep tags a contact → the agent calls them automatically.- Trigger: Contact tagged → Tag Added → “hot-lead”
- Action: Voice call — Sales agent
- Action: Condition — Check call outcome
- Outcome = no_answer: Send SMS — “Hi
{{firstName}}, I just tried to reach you. When’s a good time to chat?” - Outcome = voicemail: Wait 4 hours → Voice call retry
- Default: Update contact — Add “contacted” tag
- Outcome = no_answer: Send SMS — “Hi
Onboarding drip sequence
New customer tagged → send a series of emails over several days.- Trigger: Contact tagged → Tag Added → “new-customer”
- Action: Send email — Welcome email
- Action: Wait — 1 day
- Action: Send email — Getting started guide
- Action: Wait — 3 days
- Action: Voice call — Onboarding check-in agent
Notify team when tag removed
When a VIP tag is removed, alert the team.- Trigger: Contact tagged → Tag Removed → “vip”
- Action: Slack message — “
{{firstName}}{{lastName}}is no longer a VIP. Tag was removed.” - Action: Send webhook — Update CRM status
