Fix: n8n 404 "The requested webhook is not registered"
n8n only answers webhooks that are registered right now: the test URL for one call after you click Execute, the production URL while the workflow is active. Everything else is a 404.
Symptoms — what you're seeing
- Calling your n8n webhook returns
404withThe requested webhook "POST my-path" is not registered. - The hint says to click "Execute workflow" and try again, or that the workflow must be active for a production URL
- It worked once in testing and then 404'd on the second call
- GoHighLevel, Stripe, Typeform or your app fires the webhook and nothing shows up in n8n's executions
Why this happens
n8n only answers a webhook path that is currently registered. Registration happens in exactly two ways, and the 404 means neither is true for the URL and method you called.
The test URL (/webhook-test/...) is registered only while the editor is listening. You click "Execute workflow" (or "Listen for test event"), n8n accepts one call, then the registration is gone. Calling it a second time, or with the editor closed, returns this 404. That's by design, not a bug.
The production URL (/webhook/...) is registered only while the workflow is active. An inactive workflow has no production webhook, however correct the URL looks.
The rest are mismatches. The error message quotes the method and path n8n received, so compare them to the node. A GET to a POST-only webhook is "not registered" even though the path exists. A path edited after you copied the URL is a different path. And in queue mode, a webhook processor that can't see the registration answers 404 for every call.
The fix, step by step
- Read the method and path in the error. The message tells you exactly what n8n received:
{"code":404, "message":"The requested webhook \"GET lead-intake\" is not registered.", "hint":"..."}Compare it with the Webhook node's HTTP Method and Path. If the caller sends GET and the node expects POST, change one to match. You can also allow multiple methods on the node. - Use the production URL for anything real. In the Webhook node, switch from "Test URL" to "Production URL" and copy that into GHL, Stripe or your app. It contains
/webhook/, not/webhook-test/. - Activate the workflow. Turn on the Active toggle (in recent n8n versions, publish the workflow) and save. The production URL is registered at that moment. If activation fails with a "conflict" message, another active workflow already owns the same method and path; give one of them a unique path.
- Re-copy the URL after any path change. Editing the path, renaming it, or duplicating the workflow changes the URL. Paste the new one into the sending system. A duplicated workflow gets a new path, so the caller is still hitting the old one.
- Check that the copied URL uses your public domain. If the URL shown on the node starts with
http://localhost:5678, setWEBHOOK_URL=https://n8n.yourdomain.com/and restart. Otherwise you'll keep copying an address the sender can't reach. - In queue mode, restart the webhook processors. If you run separate
webhookprocesses, they must use the same database and encryption key as the main instance. After activating, restart them and test again:docker compose restart n8n-webhook curl -i -X POST https://n8n.yourdomain.com/webhook/lead-intake \ -H "Content-Type: application/json" -d '{"test":true}'A 200 (or your Respond to Webhook output) and a new execution in the list confirms it's fixed.
Common variations
- "It works once, then 404s" — you're on the test URL, which accepts a single call per "Execute workflow" click. Switch to the production URL and activate.
- "The production URL 404s and the workflow is active" — the method doesn't match, the path changed after you copied it, or another instance is answering (queue mode, a second container, an old server behind the same domain).
- "It 404s only from GoHighLevel" — the GHL Webhook action is sending GET, or it's still pointed at the test URL. Set the action to POST with the production URL. The GHL side is covered in GHL webhook not receiving data.
- "It broke after an n8n upgrade" — re-save and re-activate the workflow so its webhooks re-register, then restart webhook processors.
- "The path has a parameter like /:id" — dynamic paths only match the shape you defined. A missing segment is a different, unregistered path.
When this isn't the issue
- If the webhook returns 200 but nothing downstream happens, registration is fine. See n8n webhook not triggering and n8n data not reaching the output.
- A 502, 504 or timeout (not a 404) points at the reverse proxy or the n8n process, not registration.
- A 401/403 from the webhook means you've enabled header or basic auth on the node and the caller isn't sending it — see n8n webhook error: wrong URL, method or auth.
Wiring GHL into n8n? The connect GoHighLevel to n8n guide sets up the production webhook end to end, with a downloadable starter workflow.
Need this workflow customized or debugged? Book a 30-min scope call →
Stuck configuring this workflow?
I build and fix n8n workflows for agencies and SaaS teams. 30-minute scope call — bring the problem, leave with an estimate.