Integrations

Connect ReplyMagnet to Make

ReplyMagnet sends one signed POST per lead event. Catch it with Make's Custom webhook module and route every lead into any scenario — Google Sheets, Airtable, your CRM, an email sequence. About five minutes.

Step 1 — Create a scenario with a custom webhook

  • In Make, create a scenario and add Webhooks → Custom webhook as the first module.
  • Click Add to create a new hook and copy its URL.

Step 2 — Add the endpoint in ReplyMagnet

  • In ReplyMagnet, open Settings → Integrations → Add endpoint, paste the Make URL, and pick the events you want (list below). Save, and copy the signing secret — it's shown once.
  • With the Make module in "waiting for data" state, click Send test in ReplyMagnet. Make catches the test.ping and determines the data structure automatically.

Step 3 — Build the rest of the scenario

Add your next modules and map fields from data.lead and data.campaign. Schedule the scenario to run immediately, and switch it on.

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.email_captured",
  "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": "priya@example.com"
    },
    "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 Make, enable "Get request headers" on the webhook and compare against the output of a Crypto → HMAC module (message = timestamp + "." + body, key = your signing secret, digest = hex). Filter the scenario on a match.

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 scenario 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 Zapier instead? Same mechanic: Connect ReplyMagnet to Zapier.