Get the Instagram contact into the system your team uses

For a simple CRM handoff, you might need the email, Instagram handle and campaign source. Don't require a phone number if the campaign doesn't collect one.

Write down what should happen when a person requests a second resource. Creating another record may be wrong if your CRM expects one contact with several activities.

Create a ReplyMagnet account to test the capture side. The plan guide places outbound webhooks on Pro, from $29 monthly.

The chain is short. A comment matches your keyword, ReplyMagnet captures the lead, and that moment fires a webhook: one signed POST request carrying the lead as JSON to the endpoint you set.

Zapier and Make are the two automation tools most teams already run, and both accept an inbound webhook as a trigger: Zapier calls it a Catch Hook, Make calls it a custom webhook.

Paste the URL either one gives you into ReplyMagnet as the endpoint, and 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 spreadsheet, a Slack channel, or a mailing list the same way.

You don't have to use either tool. The webhook is a plain signed POST request, so if you run your own backend you can receive it directly and skip the automation platform entirely.

Only four events send, and each is a real step a lead took, not something invented for the payload:

• Lead created: a matched comment becomes a lead, before any gate.
• Email captured: someone submits the email gate on the capture page.
• Phone captured: someone submits the phone gate.
• Follow confirmed: Instagram's own follow check verifies a follow; the payload marks it checked, not self-reported.

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, or watch for just one event type if that's all a particular destination needs.

1. Create the receiving hook in your chosen integration service.
2. Add the receiver URL to ReplyMagnet using the webhook setup guide.
3. Complete a resource request with test contact details.
4. Inspect the received event before choosing destination fields.
5. Run the destination action and open the resulting record.

A receiver only shows its real fields after it has seen one delivery, so send the test lead before you start mapping. Guessing at field names ahead of the first event is how a mapping goes stale the moment the real payload differs.

Use a throwaway or clearly test-labelled record when you do this, so a real teammate doesn't mistake it for a genuine inquiry later.

Follow the receiver's current documentation for its setup and account requirements: Zapier webhooks or Make webhooks. Their plans and controls are separate from ReplyMagnet.

Three things matter when you create the endpoint:

• The endpoint URL: the catch-hook address Zapier or Make gives you, or your own backend URL.
• The events: which of the four you want that endpoint to receive.
• The secret: shown once, at creation time, so copy it then.

ReplyMagnet shows the signing secret only once. Copy it immediately and store it the way you'd store any other API key, not in a screenshot or a shared test log.

The signature proves the request came from ReplyMagnet and wasn't forged or replayed. Recompute the HMAC over the timestamp and raw body with your secret, then compare it to the header ReplyMagnet sent.

Hash the timestamp, a period, then the raw request body, using your secret as the HMAC key. Read that raw body before any JSON parsing touches it: re-serializing the payload changes the bytes and breaks the comparison.

Webhooks are a Pro-plan feature, priced flat at $29 a month with no per-lead or per-event charge, so a post that suddenly takes off doesn't cost more to deliver. The 30-day trial runs on Pro with no card, long enough to wire a real endpoint and watch a live lead arrive.

Don't assume every received request represents a new person. A retry may repeat an event because a service was slow or unavailable.

Test an existing email and a missing optional field. Decide whether the destination should update the contact, attach a note or reject the record for review.

If you build a custom receiver, follow ReplyMagnet's signature-verification instructions rather than trusting an unverified request. Keep secrets out of screenshots and shared test logs.

Two routes carry a lead out of ReplyMagnet, and they suit different destinations: the native ESP sync, or an automation webhook.

The native sync is the simpler path when your list already lives in Mailchimp or Kit: connect the account once and every captured email pushes in, tagged with its campaign, with nothing else to configure.

The webhook route is the general one, reaching a CRM, a sheet, a chat tool or a database that the direct sync was never built to reach.

They aren't exclusive. A common setup runs the ESP sync into your mailing list while a webhook copies the same lead into a CRM: one captured lead, two destinations, no double entry.

When a lead doesn't show up on the other end, check both sides separately. A practical order:

• Did the campaign capture the expected details?
• Did the webhook reach the receiver?
• Did the field mapping produce valid data?
• Did the destination accept the create or update action?
• Did the automation platform's own run history show an error?

Each layer can succeed on its own while the one right after it silently fails, which is why checking only the first is never enough.

If the only destination you need is Mailchimp or Kit, the native connection starts at $9 with no automation tool required. Fewer moving parts can make a simple subscriber handoff easier to maintain.