node cookbook
N8N Webhook Node Cookbook
Use the Webhook node to start workflows from incoming HTTP requests, form submissions, app callbacks, or custom event producers.
- Use when
- n8n workflows, webhooks
- First check
- Add the Webhook node as the workflow trigger.
- Time to check
- 5-10 minutes
- Next step
- Run the recommended steps, then verify a production execution.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
Use the Webhook node to start workflows from incoming HTTP requests, form submissions, app callbacks, or custom event producers.
Version awareness
Last reviewed 2026-05-21
Key Facts
- Node role
- Trigger workflow executions from HTTP requests.
- URL modes
- Test URL for development and production URL for active workflows.
- Common pairing
- Respond to Webhook for custom response handling.
- Self-hosting dependency
- Public webhook URLs depend on correct endpoint and domain configuration.
Recommended Steps
- Add the Webhook node as the workflow trigger.
- Choose the HTTP method and path.
- Use the test URL while building the workflow.
- Activate the workflow and switch external apps to the production URL.
- Add Respond to Webhook when the caller needs a custom response.
Verification
- A test request appears in the editor.
- A production request creates an execution after activation.
- The caller receives the expected response.
Warnings
- Public webhook endpoints can receive untrusted data; validate inputs before using them.
- Test URLs are not a replacement for active production workflows.
Production Cookbook
Common production use cases
- Receive SaaS callbacks.
- Accept internal service events.
- Expose a controlled trigger for automation.
Required credentials/scopes
- Webhook itself may not require credentials; protect path secrecy, provider signatures, and network controls where appropriate.
Input fields that usually break
- Test URL vs production URL.
- HTTP method.
- Response mode.
- Path changes after providers are configured.
Common errors
- Production URL 404.
- Provider sends GET while node expects POST.
- Caller times out because response mode waits too long.
{
"headers": {
"content-type": "application/json"
},
"body": {
"eventId": "evt_123"
},
"query": {}
}Small working pattern
Use a stable production path, normalize body fields immediately, and respond with a predictable status/body.
Related recipes using this node
When to use HTTP Request or Code instead: Use Respond to Webhook for caller response logic; use Code to verify signatures or normalize payload after receipt.