Doctor Debug Join waitlist
n8n

The requested webhook "[METHOD] [path]" is not registered.

What this means

n8n received a call to your webhook URL but isn't currently listening on that address, so it returned a 404 (not found). Usually it means you used the test URL without first pressing the run button, or you used the test URL when you should be using the live one.

Why you're seeing this

  • Using the test URL without clicking 'Execute workflow' first

    Common

    The test webhook URL (the one containing /webhook-test/) only listens for ONE call, and only after you click 'Execute workflow' on the canvas (or 'Listen for test event' inside the webhook node). If you call it before clicking, or call it twice, you get this error. n8n adds the hint: "Click the 'Execute workflow' button on the canvas, then try again. (In test mode, the webhook only works for one call after you click this button)". On the test URL the quoted part shows just the path, without the method.

  • Workflow is not published, but the production URL was used

    Common

    The production URL (containing /webhook/) only works while the workflow is live: published with the 'Publish' button in the editor header (on n8n 1.x, switched on with the 'Active' toggle). If it isn't, n8n adds the hint: "The workflow must be active for a production URL to run successfully."

  • Test and production are different paths, used interchangeably

    Common

    Operators often assume the same URL works in both modes. Test is /webhook-test/<path> and production is /webhook/<path>. They are genuinely different endpoints, not one URL in two modes.

  • Activated via the REST API, or an imported webhook node

    Rare

    There are confirmed reports where activating via API, or reusing an imported webhook node, fails to register the path; saving and publishing through the editor UI fixes it.

How to fix it

  1. 1

    Decide whether you are testing or running live. For a quick test you must use the Test URL; for real/scheduled use you must use the Production URL.

  2. 2

    If testing: open the workflow, click 'Execute workflow' on the canvas (or 'Listen for test event' in the webhook node) FIRST, then immediately send your request to the test URL. It only accepts one call per click.

  3. 3

    If running live: publish the workflow with the 'Publish' button in the editor header (on n8n 1.x, flip the 'Active' toggle in the top-right to ON), then use the Production URL, the one with /webhook/ in it, NOT /webhook-test/.

  4. 4

    If the error instead reads "This webhook is not registered for GET requests. Did you mean to make a POST request?", the path is fine: change the HTTP method your caller uses to the one n8n names.

  5. 5

    If you imported this workflow from another instance and it still fails, delete the webhook trigger node, add a fresh one, save, and publish again.

  6. 6

    If you activated the workflow via the n8n API, re-save and re-publish it through the editor UI to force path registration.

Why this happens (the technical detail)

n8n registers webhook routes dynamically. Test routes are registered only for a short window after you press 'Execute workflow' and are torn down after a single execution; production routes are registered only while the workflow is published (active). A request arriving when no route is registered for that path returns a 404 with this message. If the path IS registered but for a different HTTP method, n8n returns a different message that names the method it expects. The distinct test/production paths exist so test traffic never hits live automations.

Related errors

Sources

Last verified 2026-09-17.