All production webhook URLs on my n8n Cloud instance are returning 404 (Not Found) when called externally. Test webhooks work fine when the workflow is in listen mode, but production URLs never trigger.
Workspace: n8n Cloud instance Affected Workflow ID:jNOpppc8Vg5hBbJL (Universal Apollo - Contact Search) Webhook Path:/webhook/apollo-contact-search Method: POST
What is the error message (if any)?
HTTP 404 Not Found when hitting the production webhook URL externally via curl or ReqBin.
Share the output returned by the last node
No executions are triggered at all. The executions tab shows zero entries from external webhook calls.
Information on your n8n setup
n8n version: Cloud (latest)
Running n8n via: n8n Cloud
Operating system: N/A (cloud hosted)
Steps already tried
Toggled workflows inactive and back to active
Deleted and recreated the Webhook node with identical configuration
Republished the workflow with new versions
Tested via external HTTP clients (ReqBin, curl)
The webhook config:
HTTP Method: POST
Path: apollo-contact-search
Response Mode: Using Respond to Webhook Node
Authentication: None
The test URL works in listen mode, but the production URL consistently returns 404. I have also seen similar reports on GitHub (issue #14020 regarding webhook routing on cloud instances).
Any help from the community or n8n team would be appreciated. This is blocking production integrations.
you physically cannot fix this from the n8n interface. toggling the active status, rebuilding nodes, or changing paths won’t force the cloud router to resync.
you have to contact n8n cloud support directly (usually via [email protected]). tell them explicitly that you are experiencing a “workspace-specific tenant-level routing issue where all production webhooks return 404.” using that exact phrasing tells n8n team exactly what is broken so they can manually rebuild the routing table for your instance.
you can verify by yourself before :
Double‑check the exact production URL and method.
In the Webhook node, switch to Production URL and copy that URL exactly.
Confirm your external client is using POST, since the node is configured for POST. A mismatch (e.g. sending GET) will not match the webhook and can result in 404.
Confirm the workflow is really active/published
The workflow must be switched to active for the production webhook to be registered. Saving alone is not enough.
After activating, wait a few seconds and then call the production URL again.
Check Executions (not the editor canvas)
For production webhooks, you will not see data appear live on the canvas; you must open the Executions tab and look for new runs.
If all of the above are correct and you still get 404 with no executions at all, then only n8n support can fix:
This is a known cloud infrastructure issue, not anything wrong with your workflow config. When test webhooks work but production URLs return 404 across your whole workspace it’s a tenant-level routing problem on n8n’s side that you can’t fix through the UI. You’ve already done all the right troubleshooting steps, at this point you need to reach out to [email protected] and ask them to reset/re-sync the webhook registrations for your workspace. There’s a GitHub issue (#22782) documenting the same thing if you want to reference it in your ticket.