Sync Email and Phone Updates to Zapier

An email address or a phone number is the one thing a DM conversation gives you that outlives the DM. New or Updated Email and New or Updated Phone Number are how it leaves LinktoDM the moment it arrives, instead of waiting for someone to export a CSV on Friday.

Both are driven by the Collect email and Collect phone steps in your automations: the contact answers in the thread, LinktoDM validates and saves the value, and the Zap fires.

New or Updated Email

Map Email into the action and the address flows through.

The captured address mapped into the downstream action

The obvious pairing is your email tool — Mailchimp, ConvertKit, Klaviyo — so the lead magnet someone asked for in a comment reaches their inbox before they’ve closed Instagram. Worth building:

• Deliver, then nurture. Add the subscriber to a list and let your existing welcome sequence do the rest. The DM promised the thing; the sequence keeps the conversation going after Instagram is closed.
• A list you own. Append every address to a sheet or Airtable base alongside the username, so your audience isn’t only reachable through one platform’s algorithm.
• Bounce recovery. An update is a signal in itself. A contact correcting their address usually means the first one bounced — send updates to a “re-check these” view and you’ll catch the ones your email tool quietly gave up on.

New or Updated Phone Number

The same shape, for phone numbers.

Phone numbers arrive with the country code the collect step asked for

This is the trigger high-ticket sellers get the most from. Someone who hands over a phone number in a DM is a warmer lead than someone who hands over an email, and a Zap that texts them a booking link inside a minute converts very differently from one that emails them tomorrow.

• SMS or WhatsApp confirmation. Twilio or your WhatsApp provider, sending the booking link while they’re still in the app.
• A call list that sorts itself. A sheet row per number with the username and timestamp, so your team works down warm leads in the order they arrived.
• Straight into the CRM. Create or update the contact in HubSpot or Pipedrive with the Instagram handle attached, so whoever picks up the call knows where the lead came from.

Both triggers only fire on a real change

Re-saving the same value does nothing — LinktoDM compares against what it already held. So a contact who runs through your automation five times doesn’t produce five identical rows, and you don’t need a Zapier filter to deduplicate.

Ask for the country code

The Collect phone step’s retry message exists to enforce this, and it matters more once Zapier is involved: a number without a country code is ambiguous, and an SMS tool downstream will either reject it or send it somewhere unexpected. Show a formatted example in both the ask and the retry and most failures disappear before they reach your Zap.

A DM answer isn't marketing consent

Someone answering “what’s your email?” in a DM has not opted into a newsletter, and a Zap that adds them to one on their behalf doesn’t change that. Say where the address is going in the ask itself, and keep whatever record your local rules require.

One automation, both triggers

Collect email → New or Updated Email → subscriber added in Mailchimp
Collect phone → New or Updated Phone → row added to the call list

An automation that collects both fires both triggers, one after the other, as the contact answers each question — so two separate Zaps can send each value exactly where it belongs without either knowing about the other.