Webhooks
Send the leads a lead form captures to Zapier, Make, n8n, your CRM or any HTTPS address, signed so your receiver can verify it.
Send the leads a lead form captures to a public HTTPS address — Zapier, Make, n8n, your CRM or your own backend, and through them on to tools such as Google Sheets, Notion or Airtable. You set it up in Dashboard → Integrations, on the Webhooks tile. How that screen works is covered in Integrations.
What it does
Each time a visitor leaves their details, we send a POST request with a JSON body to the address you choose. The event is lead.captured — a visitor submitted the contact form — and it carries the fields your lead form collects, the lead's ID, the website's and the conversation's IDs, and the form's name. A Slack or Discord incoming-webhook address gets a short text message in the format that app accepts instead.
A webhook hangs off a lead form: each form has its own delivery address. That is why webhooks rely on Lead Capture, which is set up for your website when we first crawl it.
To have the assistant fetch something from your systems during a chat, use Custom Actions instead — webhooks only tell your systems that something happened.
What you need
- An HTTPS address that accepts a
POSTrequest with a JSON body. Zapier, Make and n8n each give you one when you add their "catch a webhook" step. - If your receiver insists on it, the value it expects in an
Authorizationheader.
Which plans include webhooks: What each integration allows, by plan.
How to connect
- Configure. Open the Webhooks tile. Each lead form of the website is a Lead webhook row that names its form; click Configure on the form whose leads you want to send, choose your receiver, paste its address and click Save. Save stays unavailable while the address is empty. Cancel closes the form and keeps the saved settings; Save and Cancel sit at the start of the form.
- Verify. Click Send test webhook and confirm the test request arrived in your tool.
Settings
- Receiver — six presets: Zapier, Make (Integromat), n8n, Slack (incoming webhook URL), Discord and Custom HTTPS endpoint. The preset fills in an example address and links that tool's setup guide.
- Receiver URL — where the request goes. It is stored encrypted: for Slack, Discord, Zapier, Make and n8n the secret part is inside the address itself, so the address is treated as a credential. The website's owner sees it again in these settings; a teammate with access sees only that one is set. It is redacted from our logs and audit trail, and the API reports only that one is set (and, for chat apps, its host).
- Authorization header (optional) — sent as the
Authorizationheader with every request, stored encrypted. Leave it empty to keep the value already saved — unless the new address is on another site (a different scheme, host or port): then the saved header is dropped, because it was given to the old receiver, and you enter it again if the new one needs it. - Webhook security key — the key we sign requests with. See Signed and verifiable below.
- How to receive events in Make, n8n, Zapier or your CRM — a short guide inside the panel, with an example payload.
Signed and verifiable
Every request is HMAC-signed, so your receiver can prove it came from us, and a request we cannot sign is never sent: if a form's key cannot be read, nothing goes out until you generate a new one. Each form gets a signing key when it is created. To verify signatures you need your own copy of the key: click Generate a new key once and copy the key it shows you. Each request carries these headers:
X-NovixAgent-Signature— the HMAC fingerprint. It signs the timestamp joined to the body (<timestamp>.<body>), not the body alone, so a captured request cannot be replayed with a rewritten timestamp. Re-compute it with your key and reject a mismatch.X-NovixAgent-Webhook-Id— a unique ID for each delivery attempt. An automatic retry of the same lead gets a new ID, so de-duplicate on the payload'sleadIdrather than on this header.X-NovixAgent-Timestamp— when we sent it (ISO 8601). It is part of what the signature covers, so you can reject old, replayed requests.Authorization— your own header, if you set one.
The panel includes a copy-paste Node.js example of the check. Zapier, Make, n8n, Slack and Discord trust the address and do not need it; verifying the signature matters mostly for your own backend or a custom CRM endpoint.
The key is shown once. Generate a new key first asks you to confirm in a Get a new security key? dialog, then shows the key a single time: copy it into your receiver and click I have saved the key. If you try to close the panel before that, it asks first, because the panel shows each key only this once. Generating a new key stops the old one working at once; your receiver rejects our requests until it has the new key, and in the meantime we keep retrying, as described below.
Check that it works
Click Send test webhook. We send a sample payload to your address straight away and show the result: Delivered — HTTP 200 (or whatever your receiver answered), with the time it took and the body your receiver sent back. Then check that the test request appeared in your tool. It carries the event webhook.test instead of lead.captured, so a step that filters on the event can tell it from a real lead.
If it isn't working
The panel names what went wrong with a test. Under Test & history, Refresh history loads Recent delivery failures for the address — each failed lead with its number of tries, and as pending, delivered or abandoned:
| What the panel says | What to do |
|---|---|
| DNS lookup failed — check the hostname | The address has a typo, or the domain does not exist. Copy it again from your tool. |
| Connection refused by the receiver / Receiver closed the connection / Receiver's network is unreachable | Nothing is listening at that address, or it rejected us. Check the address and that the receiving step is switched on. |
| Receiver did not respond in time | Your receiver is slow or down. Try again; if it persists, check the receiving service. |
| Receiver's TLS certificate was rejected | The receiver's HTTPS certificate is invalid or expired. It has to be fixed on the receiver's side. |
| Receiver responded HTTP 4xx / 5xx | We reached it and it refused. A 401 or 403 usually means the Authorization header or the signature check does not match. |
| Rate-limited — wait a moment | Too many tests in a row. Wait for the time the panel gives and try again. |
| Nothing was sent: the signing key could not be read — generate a new key and test again | The form's signing key could not be read, so we sent nothing rather than send it unsigned. Click Generate a new key, put the new key into your receiver, and test again. A lead that could not be sent in the meantime is listed under Recent delivery failures as Nothing was sent: the signing key could not be read — generate a new key and tried once more about 5–10 minutes later: if a new key exists by then, it is sent signed with that key; if not, it is abandoned and not sent. |
| Nothing was sent: the address points to a private network — use a public one / Nothing was sent: the address must start with https:// | A lead was not sent because we do not deliver to that address: it leads into a private network, or it is not HTTPS. Change the Receiver URL to a public https:// address; leads already refused this way are not sent to it. |
| The request failed before the receiver answered / The test could not be completed — try again | Something between us and the receiver failed. Try again; if it repeats, email support@novixagent.ai. |
A failed delivery of a real lead is retried automatically — three quick attempts, then after 5 min → 30 min → 2 h → 12 h → 24 h, about a day and a half in total — before it is abandoned. The lead is saved in Dashboard → Leads before the webhook is sent, so a failed delivery does not lose it; the Delivery card of each lead reads Webhook delivered once the lead got through, on the first attempt or on a later retry, and Webhook not sent until then.
While a delivery is still pending under Recent delivery failures, you can act on it yourself. Retry now sends it again at once; refresh the history in a moment to see how it went. Skip stops it for good: it asks first in Skip this delivery?, because we then stop sending that lead to your receiver. Each person can retry or skip 10 deliveries an hour on one website, and 30 an hour across the websites they manage.
Disconnect, and what happens to your data
To stop sending a form's leads, open the Webhooks tile, click Remove webhook on that form's row (the same button sits in the form after Edit) and confirm in Remove this webhook?. New leads stop going to that address at once, the saved Authorization header is deleted with it, and lead capture stays on. Save stays unavailable while the Receiver URL is empty, so this button is how you remove an address.
A lead whose delivery had already failed is retried (above) only while its form still holds the address it was first sent to, with the header saved at that first attempt. Removing the webhook or changing its address abandons its waiting retries at once: they are not sent to the old address, and not to the new one either.
Leads already delivered stay in your tool and in Dashboard → Leads.
Plan and limits
Webhooks are not metered: there is no monthly allowance and no cap on deliveries, and each lead form has one address. Which plans include them: What each integration allows, by plan.