# Webhooks (Zapier, Make, n8n)

> Send your site's events — form submissions, button clicks, order success — to Zapier, Make, n8n, or any webhook URL, with one chat message.

Source: https://knowledge.estage.com/capabilities/webhooks/
Part of the ESTAGE knowledge base (https://knowledge.estage.com). Full corpus: https://knowledge.estage.com/llms-full.txt

---
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 — Genesis
sends the data to a webhook URL you provide. From there, your automation tool does the rest.

## You only need a webhook URL

The important part: you build the **automation itself** ("add a row to Google Sheets", "post
to Telegram", "create a CRM contact") inside Zapier or Make — that's their job, not Genesis's.
Genesis only needs the **URL to POST to**. What happens after that is entirely up to your Zap
or scenario.

### Getting the URL

- **Zapier** → create a Zap → trigger **Webhooks by Zapier → Catch Hook** → it gives you a URL
  like `https://hooks.zapier.com/hooks/catch/123456/abcde/`. Copy it. Then build your actions
  and turn the Zap on.
- **Make** → new scenario → **Webhooks → Custom webhook** → it gives you a URL like
  `https://hook.eu2.make.com/…`. Copy it.
- **n8n / your own backend** → use any URL that accepts a `POST`.

## How to trigger it

Just describe it — no special syntax needed. Say **when** to fire and paste the **URL**, and
Genesis infers the provider (Zapier, Make, n8n, or your own server) from the link. For example:

- *"When someone submits the contact form, 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"*

**No URL yet?** Just ask to send form submissions to Zapier (or Make, etc.) and Genesis asks for
the link — with a hint on where to find it in your tool — then wires it up when you paste it.

## What Genesis does

It adds a small **fire-and-forget POST** into the exact handler you described:

- *"on form submit"* → the form's submit handler, sending the field values
- *"on button click"* → that button's click handler
- *"on order success"* → the order form's success callback, sending the order/buyer data

Each payload includes an **`event`** label and a timestamp so you can tell events apart inside
Zapier/Make. The webhook URL is stored **in your site's code** — it's an unguessable endpoint
that acts as its own secret. No backend, no database, no extra setup on your side.

:::tip[Works with any tool]
Because it's just "POST JSON to a URL," the same request works for Zapier, Make, n8n, or your own
server — paste whichever URL you have. Genesis only changes the label (and the where-to-find-it
hint) based on the host.
:::

## Good to know

- **The sending is instant and best-effort.** If the visitor closes the tab the very moment
  an event fires, that one event can be missed — exactly how most no-code webhooks behave.
  It's perfect for "send my leads / sales to a Sheet, CRM, or Telegram." For billing-critical
  flows, rely on your [payment provider's](/project-settings/payments/) own records as the
  source of truth.
- **The automation lives in your tool.** Genesis sends the data; building the steps that act
  on it (and turning the Zap/scenario on) happens in Zapier/Make.
- It never blocks your form or navigation waiting on the webhook, and a failed send never
  breaks the page.