Why workflow tools love webhooks
Workflow tools turn a webhook into a chain of steps: a form submission becomes a CRM contact, a Slack message and a row in a spreadsheet. Both n8n and Zapier give you a URL that starts a workflow when a request arrives. They behave a little differently, and most problems come from those differences.
n8n: the Webhook node
Add a Webhook node as the first step. It shows two URLs:
| URL | Path | When it works |
|---|---|---|
| Test URL | /webhook-test/<path> | Only while you have clicked Listen for test event in the editor, and only for one request. |
| Production URL | /webhook/<path> | Only while the workflow is active (published). |
Give the node a readable Path (for example stripe-paid) instead of the random default, and choose the HTTP Method your sender uses.
"The requested webhook is not registered"
This 404 is the most common n8n webhook error. It means one of:
- You sent to the Test URL without listening for a test event first.
- You sent to the Production URL while the workflow is inactive.
- The method doesn't match: the node expects POST and the sender used GET, or the other way round.
Responding to the sender
The Respond option decides what the sender gets back:
- Immediately: n8n answers at once and runs the workflow afterwards. Best for most webhooks, because senders time out after a few seconds.
- When Last Node Finishes: the sender waits for the whole workflow.
- Using 'Respond to Webhook' Node: you build the response yourself, for example to answer a provider's verification challenge.
Security in n8n
The node's Authentication setting supports Basic Auth, Header Auth and JWT. Header Auth works for senders that send a fixed secret header. Providers that sign each request (Stripe, GitHub, Shopify) need the signature recomputed over the exact raw body: switch on the node's Raw Body option and check the HMAC in a Code node. The method is explained in webhook signature verification.
Self-hosting behind a reverse proxy? Set the WEBHOOK_URL environment variable to your public address, or n8n shows internal URLs that senders can't reach.
Zapier: Webhooks by Zapier
Zapier's built-in Webhooks by Zapier app (a premium app, so it needs a paid plan) has three triggers:
- Catch Hook: gives you a URL like
https://hooks.zapier.com/hooks/catch/…/…/and parses the JSON body into fields. - Catch Raw Hook: also passes the raw body and headers, which you need to verify a signature.
- Retrieve Poll: polls a URL instead of waiting for requests.
Zapier answers every request right away with its own success response, so you can't return a custom status or body. Use the same app's POST or Custom Request action to send webhooks to other services.
The weak spot: when the workflow isn't running
A workflow tool is another moving part between the sender and your systems:
- An inactive n8n workflow answers 404, and many senders treat a 4xx as final and never retry.
- A crashed self-hosted n8n instance loses whatever arrives while it is down.
- Neither tool keeps a long, searchable history of the raw requests.
That is fine for notifications. For payments and orders, put HookStead in front: it verifies the provider's signature, stores every event, and delivers to your n8n or Zapier URL with retries. Turn on retrying 4xx answers for that destination (retryOn4xx in the API) so a 404 from an inactive workflow is retried too, and replay anything the workflow missed once it is fixed.
Frequently asked questions
- What is the difference between the n8n test URL and production URL?
- The test URL (/webhook-test/) works only while you listen for a test event in the editor. The production URL (/webhook/) works only while the workflow is active.
- Why does n8n say the requested webhook is not registered?
- You called the test URL without listening for a test event, called the production URL while the workflow is inactive, or used a different HTTP method than the Webhook node expects.
- Is Webhooks by Zapier free?
- No. Webhooks by Zapier is a premium app and needs a paid Zapier plan.