Guides
Send Instagram leads to Zapier and Make automatically
The lead is captured in ReplyMagnet the moment someone comments your keyword. A signed webhook then pushes it wherever your stack already lives, without you copying anything by hand.
Last updated
What connects to what
Each lead event fires a signed HTTP webhook to an endpoint you set. Point that endpoint at a Zapier or Make catch hook and the event flows into their app directories, so a captured Instagram lead can land in your CRM, a spreadsheet, or an email tool without a manual step.
The chain is short. A comment matches your keyword, ReplyMagnet captures the lead, and that moment fires a webhook: a single signed HTTP request carrying the lead as JSON. You choose where it goes.
Zapier and Make are the two automation tools most people already run, and both accept an inbound webhook as a trigger. Zapier calls it a Catch Hook; Make calls it a custom webhook. You paste the URL they give you into ReplyMagnet as the endpoint, and from there the event fans out into whatever they connect to. Zapier's own directory lists more than 8,000 apps, so a lead can reach a CRM, a Google Sheet, a Slack channel, or a mailing list the same way.
You do not have to use Zapier or Make at all. The webhook is a plain signed POST, so if you run your own backend you can receive it directly and skip the middle tool entirely.
Which events fire
Four lead events send a webhook: lead created when a comment first becomes a lead, email captured and phone captured when someone fills the gate, and follow confirmed when the API verifies a follow. Each carries the lead and the campaign it came from as JSON.
The webhook is not a single generic ping. Each real step a lead takes sends its own event, so you can wire different destinations to different moments.
- Lead created fires the moment a matched comment becomes a lead, before any gate. This is the one to catch if you want every commenter in your CRM.
- Email captured fires when someone submits the email gate on the capture page.
- Phone captured fires when someone submits the phone gate.
- Follow confirmed fires when a follow is verified through Instagram's own
is_user_follow_businesssignal, so it carries a checked yes, not a self-reported one.
Every payload names the campaign the lead came from, so a Zap or a Make scenario can route a pricing-post lead differently from a giveaway lead. Only these four events send: the webhook reports what actually happened in the pipeline, nothing invented.
Zapier vs Make vs native ESP sync
For Mailchimp or Kit, the built-in ESP sync is the simpler path: connect the account once and captured emails push in automatically. Reach for a Zapier or Make webhook when the destination is something else, a CRM, a sheet, Slack, or a tool the direct sync does not cover.
Two routes carry a lead out of ReplyMagnet, and they suit different destinations.
The native ESP sync is the direct one. If your list lives in Mailchimp or Kit, connect it once in Settings and a captured email pushes straight in, tagged with its campaign, with no automation tool in between. It is a Pro-and-up feature, and it is the least fiddly option when the destination is one of those two tools.
A Zapier or Make webhook is the general one. It carries the raw event to anywhere those platforms reach, which is most of the software a business runs. Use it when the lead needs to land somewhere the direct sync does not go: a CRM like HubSpot or Pipedrive, a Google Sheet, a Slack alert, a Notion database, or several of those at once from a single event. Webhooks are also Pro and up.
They are not exclusive. A common setup is the ESP sync feeding your mailing list while a webhook copies the same lead into a CRM. One captured lead, two destinations, no double entry.
Setting it up
Add the endpoint in Settings, choose the events to send, and copy the shown secret. The webhook signs every request with an X-Magnet-Signature HMAC header your receiver verifies. Webhooks are a Pro-plan feature. See /docs/zapier and /docs/make for the platform-specific steps.
The full walkthroughs, including the exact clicks inside Zapier and Make and how to catch the raw body before either tool auto-parses it, live in the setup docs: Zapier setup and Make setup. This guide covers what to know before you open them.
Three things matter at setup. First, the endpoint URL: the catch-hook address Zapier or Make gives you, or your own backend URL, pasted into ReplyMagnet's Integrations card. Second, the events: pick which of the four you want that endpoint to receive. Third, the secret: ReplyMagnet shows a signing secret once when you create the endpoint, so copy it then.
Every delivery is signed. ReplyMagnet sends an X-Magnet-Signature header, an HMAC computed over the timestamp and the raw request body with your secret, plus an X-Magnet-Timestamp. Your receiver recomputes the same HMAC and compares, which proves the request genuinely came from ReplyMagnet and was not forged or replayed.
Webhooks and the ESP sync are both Pro and up. The cost is the flat plan price: Pro is $29 a month, and there is no extra per-lead or per-event fee no matter how many webhooks fire, so a post that takes off pushes a thousand leads for the same price as ten. ReplyMagnet's trial is 30 days on Pro with no card, which is enough to wire a webhook into a real Zap and watch a live lead arrive before deciding anything about payment.
Common questions
Can I send Instagram leads to Zapier?
Yes. Create a Catch Hook in Zapier, paste its URL into ReplyMagnet's Integrations card as a webhook endpoint, and every captured lead fires a signed request into your Zap, which can route it to any of Zapier's 8,000+ connected apps.
Does it work with Make?
Yes. Make accepts an inbound custom webhook as a scenario trigger the same way Zapier does. Paste the webhook URL Make gives you into ReplyMagnet, pick the events to send, and each lead lands in your Make scenario as JSON.
Which plan includes webhooks?
Webhooks are a Pro-plan feature, available on Pro and Agency. The same tiers include the native Mailchimp and Kit sync. Starter and Basic capture and store leads but do not fire outbound webhooks.
Do I need Zapier if I use Mailchimp?
No. ReplyMagnet syncs captured emails to Mailchimp or Kit directly on Pro and up, with no automation tool in between. Reach for a Zapier or Make webhook when the lead needs to go somewhere the direct sync does not cover, like a CRM or a spreadsheet.
Is the webhook signed and secure?
Yes. Every delivery carries an X-Magnet-Signature header, an HMAC computed over the timestamp and raw body with a secret only you and ReplyMagnet hold, plus an X-Magnet-Timestamp. Recompute the same HMAC on your side and compare to confirm the request is genuine.