Trigger Zaps When Contact Tags Are Added or Removed

A tag is the cleanest way for a flow to say “this specific thing just happened” to the rest of your stack. Two triggers listen for it — New Tagged Contact when one is added, Contact Tag Removed when one comes off — and between them they cover granting something and taking it away.

Tags come from your flows

Neither trigger fires on its own. Both are driven by the Add contact tag and Remove contact tag actions in a flow, so the flow is where you decide who qualifies. Add an Action node, then pick the action type.

Add contact tag and Remove contact tag are the two that drive these triggers

Add contact tag takes a list of tags rather than one. Type a tag and press Enter to add it; anything already on the contact is left alone.

One action can apply several tags — each one fires New Tagged Contact

Because a single action can apply several tags, it produces one event per tag. A Zap watching for vip won’t be confused by newsletter arriving in the same breath, but a Zap that reacts to any tag will run twice — filter on Tag Name if that matters.

The same node, configured to remove a tag — this is what fires Contact Tag Removed

That split between flow and Zap is the point. The flow holds the logic and can change as often as you like; the Zap only cares that a named tag moved. Rewrite the DM copy, add a condition, swap the trigger keyword — the Zap keeps working untouched.

Name tags after the state, not the campaign

webinar-yes still reads correctly next March. march-webinar-signup-final doesn’t, and you’ll be rebuilding the Zap when the next one runs. Tags that name a state survive campaigns; tags that name a campaign don’t.

New Tagged Contact

The added tag’s name comes through in the payload, so one Zap can serve several tags — map Tag Name into the action and use a Zapier filter or paths to route on it.

The tag's own name is part of the event, so the Zap knows which tag fired

What people wire it to:

• Bookings. A flow tags call-requested when someone picks that button in a DM → Zapier creates the Calendly invite and emails the link.
• Paid community access. Tag course-paid after a payment node clears → Zapier invites them to Circle, Discord or a shared Notion space.
• CRM stages. Tag qualified → the deal moves to the next stage in HubSpot or Pipedrive, with the Instagram username on the record so your team knows where the lead came from.
• Waitlists. Tag vip-waitlist → a row in a sheet you can sort, count and export when the product opens.
• Fulfilment. Tag sample-requested → a shipping label task in Trello or Asana, no one retyping an address.

Contact Tag Removed

The mirror image, and the one people forget to build. Removing a tag is how access ends, and it’s worth automating for the same reason granting it is — the manual version gets skipped.

Contact Tag Removed carries the contact, so the Zap knows whose access to revoke

• Revoke on churn. A flow strips subscription-active → Zapier removes them from the paid community, unshares the Drive folder, and appends a line to a churn log.
• Win-backs. trial coming off a contact is the cue to start the win-back sequence in your email tool.
• Keeping lists honest. Removing newsletter in LinktoDM unsubscribes them in Mailchimp too, so the two never disagree about who opted out.

Both directions, one system

Flow: payment clears → Add tag (course-paid)    → Zap: invite to community
Flow: refund issued  → Remove tag (course-paid) → Zap: revoke community access

Built as a pair, membership follows the tag automatically in both directions, and the tag on the contact is a reliable answer to “does this person have access?” — because it’s the same fact both Zaps are reading.

Test revocation before you trust it

A revoking Zap acts on a real account in a real app. Run it against your own second Instagram account first and confirm what it removes, because a Zap wired to the wrong tag will happily lock out paying customers.