The LinktoDM Zapier Integration
Your automations already collect the things a business actually runs on — an email, a phone number, a plan tier, a tag that marks someone as ready to buy. Until now that lived in LinktoDM and left as a CSV. Zapier is how it reaches the rest of your stack the second it’s captured: Google Sheets, Notion, Airtable, Mailchimp, HubSpot, Slack, Twilio, Calendly, Shopify, and thousands more.
LinktoDM is the trigger, your other app is the action
Section titled “LinktoDM is the trigger, your other app is the action”The integration works in one direction. LinktoDM starts Zaps; it doesn’t receive them.
LinktoDM event → Zapier picks it up → your app does somethingSo “a contact hands over their email in a DM” can become a row in a sheet, a subscriber in Mailchimp, and a Slack message — but Zapier can’t reach back in to send a DM for you. Sending stays in your flows.
Six events, all instant
Section titled “Six events, all instant”Every one is instant: it fires on a webhook the moment the event happens, rather than waiting for Zapier to poll on a schedule. The gap between a comment landing and your Zap running is seconds, which is the difference between following up while someone is still holding their phone and following up tomorrow.
| Event | Fires when |
|---|---|
| New Contact | Someone interacts with one of your automations for the first time |
| New or Updated Email | A contact’s email is captured or changed |
| New or Updated Phone Number | A contact’s phone number is captured or changed |
| New Tagged Contact | A tag is added to a contact |
| Contact Tag Removed | A tag is removed from a contact |
| New or Updated Custom Field | A custom field value is set or changed |
What you can build
Section titled “What you can build”The obvious version is “copy the email into a sheet”. These are the ones worth the setup time.
A contact sheet that keeps itself current. Google Sheets has a
Lookup Spreadsheet Row
action with a create the row if it doesn’t exist yet option. Look the contact
up by username, then update. Point all six triggers at the same sheet and each
person gets one row that fills in over time — email in column C when they hand it
over, plan_tier in column E when it changes — instead of six lists you have to
reconcile.
One digest instead of two hundred pings. Digest by Zapier collects entries and releases them on a schedule — daily, weekly, monthly, or once a set number have piled up. Point New Contact at it and a reel that goes off overnight becomes one summary at 9am rather than a Slack channel nobody can read.
Speed-to-lead on phone numbers. New or Updated Phone Number → Twilio → an SMS with your booking link, inside a minute of them typing it. For anything high-ticket this is the single highest-leverage Zap on the list: the number came from a DM conversation, so they’re expecting you.
Sell without a checkout page. A flow’s
payment node clears → it adds a course-paid
tag → Zapier invites them to your Circle or Discord community, raises the invoice
in QuickBooks, and adds them to the onboarding sequence. The buyer never leaves
Instagram.
Access that ends by itself. The mirror image, and the one people forget.
A flow removes subscription-active → Zapier revokes the community seat,
unshares the Drive folder, logs the churn. Built as a pair with the one above,
membership follows the tag in both directions and nobody has to remember.
Route by tag instead of building five Zaps.
Paths
splits one Zap into as many as ten branches on conditions you set, so a single
New Tagged Contact Zap can send vip to your CRM, refund-requested to a
support queue, and webinar-yes to Calendly.
Quiz answers you can actually read. A flow that stores replies with Set user field turns a DM quiz into research: every answer lands in a sheet, already attached to the person who gave it.
Where to go next
Section titled “Where to go next”Connect LinktoDM to Zapier takes about a minute, then build your first Zap walks through one end to end — starting with the LinktoDM automation that creates the contacts in the first place.