Webhooks (Zapier, Make, n8n)
Send your site's events — form submissions, button clicks, order success — to Zapier, Make, n8n, or any webhook URL by asking in chat.
Connect your site to Zapier, Make, n8n, or your own backend: when something happens on the page — a form is submitted, a button is clicked, an order succeeds — the site sends the data to a webhook URL you provide. From there, your automation tool does the rest.
There's no separate webhook setting: you ask in chat, and the AI adds the request to your site's code.
Before you start: is a webhook what you need?
Several common jobs have a built-in route that needs no webhook:
| You want | Use |
|---|---|
| Form submissions saved as contacts | Form Settings — forms capture into your CRM |
| An email for every submission | Notify admin by email in Form Settings |
| A message in Telegram, Slack, Discord or WhatsApp | Also notify in in Form Settings, after you set up the connector |
| Rows in a spreadsheet | The Google Sheets connector |
Use a webhook when the automation lives in Zapier, Make or n8n, or in your own server.
Getting the URL
You build the automation itself ("add a row", "post to a channel", "create a deal") inside your tool — that's its job. The site only needs the URL to send to.
- Zapier → create a Zap → trigger Webhooks by Zapier → Catch Hook → copy the URL it gives
you (
https://hooks.zapier.com/hooks/catch/…). Then build your actions and turn the Zap on. - Make → new scenario → Webhooks → Custom webhook → copy the URL
(
https://hook.eu2.make.com/…). - n8n / your own backend → any URL that accepts a
POST.
How to ask
Say when to send and paste the URL:
- "When someone submits the contact form, also send it to this webhook: https://hooks.zapier.com/hooks/catch/123456/abcde/"
- "On order success, send the buyer details to https://hook.eu2.make.com/abc123"
- "Fire this webhook when the Buy button is clicked: https://example.com/hook"
Select the form or button first to make it unambiguous. The AI adds a small request in that handler that sends the event's data as JSON. Ask for the details you need in the payload — for example "include an event name and a timestamp" — so you can tell events apart in your tool.
Things worth knowing
- The URL lives in your site's code, which visitors can see. Treat it as public: anyone who finds it could send data to it. Don't use a URL that triggers anything sensitive.
- The sending is best-effort. If a visitor closes the tab the moment the event fires, that one event can be missed — like most no-code webhooks. For billing-critical flows, rely on your payment provider's own records.
- Ask for the request to run in the background ("don't wait for the webhook"), so a slow or failing endpoint never holds up the form or the page.
- Test it end to end after publishing: submit the form on the live site and check that your Zap or scenario received the data.