Webhooks, Zapier, Make and n8n

A webhook sends each new lead as JSON to a URL you choose: your own code, or an automation tool like Zapier, Make or n8n that passes it on to thousands of other apps. Admins can connect one for every lead in the organisation; anyone can connect one for the leads on their own cards.

Zapier, Make or n8n

1. In your tool, start a new workflow with a webhook trigger: Webhooks by Zapier → Catch Hook, a Make Custom webhook, or an n8n Webhook node (method POST). Copy its URL.
2. In Fronko, open Integrations, choose Zapier, Make or n8n, and click Connect.
3. Paste the URL and save, then click Send test lead so your tool sees an example.
4. Add the next steps in your tool: a row in a sheet, a deal in your CRM, a message in Slack…

Your own endpoint

1. Create an https endpoint that accepts a JSON POST and answers with a 2xx status within 20 seconds.
2. Open Integrations → Webhook, paste the URL, and optionally click Generate for a signing secret. Copy it before you save.
3. Save and click Send test lead.

Each request looks like this:

{
  "event": "lead.created",
  "version": 1,
  "test": false,
  "data": {
    "id": 1042,
    "created_at": "2026-10-08T09:20:00Z",
    "name": "Ada Lovelace",
    "email": "[email protected]",
    "phone": "+447700900123",
    "notes": "Loved the talk.",
    "source": "nfc",
    "card": { "id": 3, "slug": "maya-chen", "name": "Maya Chen", "url": "https://app.fronko.com/p/lumen/maya-chen" },
    "owner": { "id": 12, "username": "maya", "email": "[email protected]" },
    "organisation": { "id": 1, "name": "Lumen Labs", "handle": "lumen" }
  }
}

Checking the signature

With a signing secret, every request has an X-Fronko-Signature: t=<time>,v1=<signature> header. v1 is the HMAC-SHA256 of <time>.<request body> with your secret, in hex. Compute it, compare it in constant time, and reject requests whose time is more than a few minutes old.

Failures and retries

If your endpoint fails or doesn’t answer, Fronko retries several times with growing delays. The connection’s activity log shows every delivery with the status your endpoint returned.