At a glance
- Two URLs, two rulesIf the sender is a live system, such as Shopify, Stripe or a form, give it the production URL and activate the workflow.
- Testing an inbound workflowTo build the workflow, click "Listen for test event", then send one request with curl or the sending app's test button.
- Other common causesWrong method: the node accepts GET or POST, not both, unless you set it to.
Two URLs, two rules
- The test URL contains /webhook-test/. It only listens after you click "Listen for test event" in the editor, and only for one call. After that call, or after about two minutes, it stops.
- The production URL contains /webhook/. It only listens while the workflow is active (published). Runs appear in the executions list, not on the canvas.
If the sender is a live system, such as Shopify, Stripe or a form, give it the production URL and activate the workflow.
Testing an inbound workflow
- To build the workflow, click "Listen for test event", then send one request with curl or the sending app's test button. The data appears on the canvas.
- To test the finished workflow, activate it and send to the production URL. Check the result under Executions.
- If the request reaches n8n but the run fails, open that execution to see which step stopped and with what data.
Other common causes
- Wrong method: the node accepts GET or POST, not both, unless you set it to.
- Self-hosted behind a proxy: set WEBHOOK_URL to your public address, or n8n shows an internal URL such as localhost.
- A path used by two active workflows: only one of them can register it.
Updated 2026-11-01. General guidance, not advice for your situation; we scope each project in writing before any work starts.
Questions people ask first
Why does it work in the editor but not live?
The editor uses the test URL. Live systems need the production URL and an active workflow.
Can I keep the test URL listening?
No. It stops after one call. Use the production URL for anything that sends on its own schedule.
Where do production runs show up?
In the Executions list for the workflow, not on the editor canvas.
Tell us what you need built.
Tell us the process and the tools involved, or call. We reply with questions or a written scope.
hello@pushbuild.com