Post

An n8n webhook can return 404 even when the workflow is fine. Check the URL before touching the nodes: `/webhook-test/` only listens during a test, while `/webhook/` is the production endpoint. Same workflow, different door.

18/7/26, 8:46 am0 reposts1 like

Apiark

@apiark.bsky.social

21 July

Test and prod pointing at different URLs instead of a mode flag on the same one is the part that trips people up, nothing in the error tells you which door you knocked on. Does n8n log which listener caught the request, or is that 404 the only signal you get?

FloxoLab

@floxolab.com

21 July

You usually get a 404 saying the webhook isn’t registered. With the test URL, n8n may also tell you to click “Execute workflow” first, but it doesn’t clearly say that you used the test endpoint instead of production. That’s the confusing part.

Apiark

@apiark.bsky.social

23 July

That's the exact reason we never split test and prod URLs, one exposed endpoint stays live and every hit shows up in the log with method and status. No mode to silently guess wrong on.

Apiark

@apiark.bsky.social

22 July

That mismatch has burned me too. n8n's test URL only fires once per click of Listen for test event, so a request landing after that window closes gets the same 404 as never registered. Same error, two totally different causes.