Solution skill
Fix n8n "webhook is not registered" 404s
Complete solution
Shows how to fix n8n "webhook is not registered" 404s. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Do not change the workflow logic; the problem is registration, activation state, or which URL the caller is using. Classify FIRST from the observable evidence, then apply the matching fix.
When to use
You are seeing this: n8n registers two different endpoints for every Webhook node. Use this skill when you run into "Fix n8n "webhook is not registered" 404s".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Use this when an external caller gets a 404 with a body like:
{"code":404,"message":"The requested webhook \"POST my-path\" is not registered.","hint":"The workflow must be active for a production URL to run successfully..."}The message means n8n's router has no in-memory route for that method + path, the request never reached a workflow. Do not change the workflow logic; the problem is registration, activation state, or which URL the caller is using. Classify FIRST from the observable evidence, then apply the matching fix.
1. Read the URL: test (/webhook-test/) vs production (/webhook/)
n8n registers two different endpoints for every Webhook node. They have completely different lifecycles:
Test URL (
https://example.com/webhook-test/[path]): live only while the workflow editor has "Listen for Test Event" actively waiting on that node, and it fires exactly once, the second call gets a 404 even if nothing changed.Production URL (
https://example.com/webhook/[path]): live only while the workflow is active (toggle ON and saved). Editing or testing in the editor does nothing to it.
Failure mode 1, "it worked in testing, then 404 in production": the caller is still hitting the test URL. Switch the caller to the production URL. Note the UI quirk: the Webhook node dialog always opens on the Test URL tab even when the workflow is active, that is display-only and does not mean production is broken.
Failure mode 2, "the first test call worked, the second 404s": that is the test listener being consumed. Click "Listen for Test Event" again for each test call; do not diagnose this as a registration bug.
2. Confirm the workflow is really active
Production routes are registered when the workflow is activated, not when it is saved. The toggle in the editor shows the saved state; a workflow saved as inactive while the editor showed it "green" is a classic source of 404s.
Toggle the workflow OFF, wait a few seconds, toggle ON, save, then retry the production URL.
In the Executions list (not the canvas): if the call produced zero executions, not even failed ones, the request was rejected at the router, which confirms registration/activation rather than a node error. This is also a blind spot: webhook 404s leave no trace in n8n, so monitor them from the caller's side.
3. Check the method and path the caller is actually using
Registration is per HTTP method plus path. A caller sending GET to a Webhook node configured for POST gets "not registered", not a method error.
Compare the method in the error message (
"POST my-path") with the Webhook node's HTTP Method setting.Compare the full path segment-by-segment with the production URL shown in the node after activation. Duplicating a workflow or re-saving can regenerate the webhook path/ID, leaving the caller with a stale path.
No two active workflows may share the same method + path. If another workflow uses the same path, deactivating one can deregister the route for the other.
4. Handle the registration desync: active in the DB, missing in memory
The known hard case: the workflow is active, the URL and method are correct, and the caller still gets not registered. n8n keeps webhook routes in memory; the in-memory table can fall out of sync with the database (seen after API-driven activate calls, database permission resets, and on n8n Cloud tenant routing issues). Evidence: POST /rest/workflows/{id}/activate returns 200 with "active": true, the DB row is active, but POST /webhook/{path} still 404s.
Apply these in order:
POST /rest/workflows/{id}/deactivate, thenPOST /rest/workflows/{id}/activate, this forces the in-memory state to rebuild. Retry the webhook.If that fails, restart the n8n container (
docker restart n8n), webhook registration runs at container startup, so a restart re-registers every active route.If it still fails on n8n Cloud, this is tenant-level routing desync: contact n8n support and describe it as a workspace routing issue where production webhooks return 404 despite the workflow being active, they rebuild the routing table manually.
5. Checklist
- Caller URL test vs production, match the lifecycle you need.
- Workflow toggled active and saved (off/on cycle to be sure).
- Method and path match the node's settings exactly; no stale or duplicated path.
- Desync: deactivate/reactivate via API, then container restart, then support.
- Zero executions in the list = router rejection; fix registration, not the flow.
Evidence
Built from recurring community.n8n.io threads on production webhook 404s (test-vs-production URL lifecycle, UI defaulting to the Test URL tab, workflow activation as the real enabler) and GitHub issue n8n-io/n8n#34038 documenting the activate-API registration desync with the deactivate/reactivate and container-restart workarounds.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_GYJ3VbobeSAULi5DV4TFJQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Fix n8n "webhook is not registered" 404s <span>— Vectle</span></a>