Integrations

Connect ReplyMagnet to Zapier

ReplyMagnet sends one signed POST per lead event — a new commenter captured, an email collected, a follow verified. Point those at a Zapier webhook and every lead lands in any of Zapier's 8,000+ apps: Google Sheets, Slack, HubSpot, Notion, your CRM. No ReplyMagnet-side code, about five minutes.

Step 1 — Create a Zap with a webhook trigger

  • In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger.
  • Pick the Catch Hook event (or Catch Raw Hook if you plan to verify signatures — see below), then copy the webhook URL Zapier shows you.

Step 2 — Add the endpoint in ReplyMagnet

  • In ReplyMagnet, open Settings → Integrations → Add endpoint and paste the Zapier URL.
  • Choose which events to send (see the list below). Save, and copy the signing secret — it's shown once.
  • Click Send test. ReplyMagnet fires a test.ping so Zapier has a sample to map fields from.

Step 3 — Map fields and switch it on

Back in Zapier, the test payload appears in the trigger step. Add your action — a spreadsheet row, a Slack message, a CRM contact — and map fields from data.lead and data.campaign. Turn the Zap on. Done.

Events

  • lead.created — a commenter matched a trigger and entered your funnel.
  • lead.email_captured — the lead typed their email on your capture page.
  • lead.followed — the follow happened. The payload carries a verification field: api_verified means Instagram's API confirmed it; we never report more certainty than the platform gives us.
  • test.ping — the test button in settings.

Payload shape

{
  "event": "lead.created",
  "created_at": "2026-07-17T12:34:56.789Z",
  "workspace_id": "9deb2631-…",
  "data": {
    "lead": {
      "id": "c0a80121-…",
      "platform": "instagram",
      "username": "priya.designs",
      "platform_user_id": "1784…",
      "is_follower": false,
      "email": null
    },
    "campaign": {
      "id": "b3db6852-…",
      "name": "GUIDE — 100k Playbook",
      "platform": "instagram"
    }
  }
}

Verifying signatures (optional, recommended)

Every delivery carries X-Magnet-Signature and X-Magnet-Timestamp headers. The signature is sha256=HMAC-SHA256(secret, timestamp + "." + rawBody). In Zapier, use Catch Raw Hook plus a Code step:

// Code by Zapier (Node) — verify X-Magnet-Signature
const crypto = require("crypto");
const expected = "sha256=" + crypto
  .createHmac("sha256", "YOUR_SIGNING_SECRET")
  .update(inputData.timestamp + "." + inputData.rawBody)
  .digest("hex");
if (expected !== inputData.signature) throw new Error("Bad signature");
return { verified: true };

Your webhook URL is unguessable, so many workflows skip verification — but it's the only way to be certain a payload came from ReplyMagnet.

Delivery guarantees

  • Deliveries ride ReplyMagnet's durable job queue: a failed POST retries with backoff (1 → 5 → 15 → 60 → 240 minutes).
  • After 8 consecutive failures the endpoint auto-disables so a dead Zap can't pile up retries; one click in settings re-enables it.
  • A webhook failure never delays or breaks a DM — delivery to your lead always wins.

Using Make instead? Same mechanic: Connect ReplyMagnet to Make.