n8n Webhook Node: Test URL vs Production URL Explained

The Webhook node lets other systems start your workflow by sending data to a URL. It is one of the most useful nodes, and the source of many beginner confusions.

Two URLs

Test URL: works while you are listening in the editor. Click “listen for test event”, send a request, and you see the data. After that the URL stops working.
Production URL: works only when the workflow is active. Runs appear in the executions list.

If your form works in testing but not later, you may still be pointing at the test URL or the workflow is not active.

Choosing the method and path

Match the HTTP method (usually POST) to what the sender uses. Keep the path short and not guessable if it should not be public.

Responding

You can respond immediately, or after the workflow finishes, and decide what the caller receives. A quick “received” response is better when the caller will time out.

Protect your webhook

Anyone with the URL can call it. Use authentication where possible, validate the input and ignore unexpected fields. See the security checklist.

Testing from your computer

Use a simple request tool to send sample data. If n8n runs on localhost, the internet cannot reach it unless you expose it deliberately.

Troubleshooting

If it does not work, read webhook 404 and not working.

Quick answers

Why does my test webhook URL stop working?

The test URL works only while the editor is listening for a test event.

Does the production URL need an active workflow?

Yes. It only receives calls when the workflow is active.

Can anyone call my webhook?

Anyone with the URL can, so use authentication and validate input.