LinktoDM Trigger Events in Zapier
Six trigger events are live. Every one is instant — it fires on a webhook the moment the event happens in LinktoDM, so nothing waits on a polling interval.
| Trigger | Fires when | Try it for |
|---|---|---|
| New Contact | Someone interacts with one of your automations for the first time | Logging every lead as it arrives |
| New or Updated Email | A contact’s email is captured or changed | Starting an email sequence |
| New or Updated Phone Number | A contact’s phone number is captured or changed | WhatsApp or SMS follow-up |
| New Tagged Contact | A tag is added to a contact | Segment-triggered onboarding |
| Contact Tag Removed | A tag is removed from a contact | Churn and revoking access |
| New or Updated Custom Field | A custom field value is set or changed | Tier changes, codes, preferences |
New Contact
Section titled “New Contact”The widest net there is. LinktoDM creates a contact the first time someone interacts with any published automation — a comment on a post automation, a story reply, a DM that matches a flow trigger — and this event fires on that moment. Every automation you run feeds it, so it’s the trigger to reach for when you want everything recorded.
Because it depends on an automation existing, it’s worth setting up in that order: build your first Zap walks through the LinktoDM half first. Note that it fires once per person — later interactions update the existing contact instead.
Send it to a Google Sheet or a Notion database and you have a lead log that builds itself. Or point it at Slack, so the reel going viral at 2am arrives as a channel message with the username attached instead of as a surprise the next morning.
New or Updated Email and New or Updated Phone Number
Section titled “New or Updated Email and New or Updated Phone Number”These two fire when a collected email or phone number lands on a contact, or when a value that was already there changes. Both compare against what LinktoDM already held, so re-saving the same value does nothing.
They get their own page: Sync email and phone updates to Zapier.
New Tagged Contact and Contact Tag Removed
Section titled “New Tagged Contact and Contact Tag Removed”Tags are how a flow says “this specific thing just happened” to the rest of your stack. Both triggers fire from the Add contact tag and Remove contact tag actions in your flows, and the added tag’s name travels with the event.
They get their own page, with the flow side included: Trigger Zaps when contact tags are added or removed.
New or Updated Custom Field
Section titled “New or Updated Custom Field”Custom fields hold values rather than labels, so this trigger carries the most detail — including the field’s previous value alongside the new one. You pick which field to watch when you set the trigger up, so it’s one Zap per field.
See Sync custom field changes to Zapier.
What every trigger hands you
Section titled “What every trigger hands you”Each event arrives with the whole contact attached, not just the value that changed — username, name, email, phone number, the previous value, the platform user ID, the event type, and a timestamp. Anything in this panel can be dropped into any field of your action.
Because the username travels with every event, you can keep one row per contact in a sheet or one record per contact in your CRM and have all six triggers write to the same place, rather than scattering one person across six lists.