n8n · Data Sync
Webhook event router
- n8n
- intermediate
- 6 nodes
- ~4 min setup
Tested on n8n 2.25.7 · Last verified 2026-06-21 · v1.0
- Trigger Webhook POST /webhook/route Receives an event with an { event } field
- Logic Switch Route by event type order · signup · support + a fallback output
- Action Respond to Webhook ×4 Answer per branch Each branch returns its routing target; swap for real actions
What it does
One webhook endpoint that routes incoming events to the right place. A Switch node reads the event type and sends orders, signups and support requests down separate branches — with a fallback for anything else. Zero credentials.
- Webhook
- Switch
- Respond to Webhook
How to import it into n8n
- Copy the workflow JSON Use the Copy JSON button above (or download the .json file).
- Open your n8n canvas In n8n, open Workflows and create a new, empty workflow.
- Paste to import Press Ctrl/Cmd+V on the canvas, or use the ⋯ menu → Import from File / Import from URL. n8n recreates every node.
- Connect your credentials Open each node flagged with a credential placeholder and select your own account — see the credentials table below.
- Test, then activate Run once with test data to confirm the path end-to-end, then toggle the workflow Active.
Notes for this template
- Open the Webhook node and copy its Production URL — POST events to it with an "event" field.
- Edit the Switch node rules to match your own event names.
- Each Switch output is a separate branch — replace the Respond nodes with real actions (notify, create a record, call an API).
- The fallback output catches any event that matches no rule.
Credentials you’ll connect
No external credentials required.
Live end-to-end test on n8n 2.25.7
Request
POST /webhook/route
Content-Type: application/json
{ "event": "refund" }Response
order → { routed: orders-service }
signup → { routed: onboarding }
support → { routed: helpdesk }
refund (unmatched) → { routed: default-queue }
(all HTTP 200)Frequently asked questions
Do I need any credentials?
No. It uses only built-in nodes (Webhook, Switch, Respond to Webhook) — no API keys or accounts.
What does the Switch node do?
It routes each incoming event down a different branch based on a field, so one endpoint can handle many event types cleanly.
Has this really been tested?
Yes. On a real n8n 2.25.7 instance, four event types (order, signup, support and an unmatched one) each routed to the correct branch, all returning 200.
How do I add a new route?
Add a rule to the Switch node and connect its new output to an action node for that event.
Is it free?
Yes — free to download and use, no signup and no email required.