n8n Webhook Works in Test but Not Production: How to Diagnose the Problem
When an n8n webhook works in test but not production, the test URL and the production URL differ. The test proved the logic works, but production uses a different endpoint, activation state or networking setup. Compare the test and production webhook configurations to find the difference, because the failure is an environment difference, not a logic problem.
Table of Contents
- 01.Test versus production in n8n
- 02.What to check first
- 03.Is the workflow activated
- 04.Test URL versus production URL
- 05.Reachability and hosting
- 06.HTTP method and authentication
- 07.How to test it
Test versus production in n8n
n8n distinguishes between test execution and production execution. A webhook trigger has a test URL and a production URL. The test URL works when you are editing the workflow. The production URL works only when the workflow is activated. If the source sends the event to the test URL, the production workflow never runs. The logic is fine, the URL or the activation is the problem.
| Aspect | Test | Production |
|---|---|---|
| Webhook URL | Test URL | Production URL |
| Activation | Runs when editing | Requires workflow active |
| Execution | Manual or test | Automatic on trigger |
| Data | Sample data | Real data |
What to check first
- Confirm the workflow is activated for production execution.
- Confirm the source sends to the production webhook URL, not the test URL.
- Check the webhook URL is reachable from the internet.
- Check the HTTP method matches what the source sends.
- Check authentication if the webhook requires it.
Is the workflow activated
The production webhook URL only works when the workflow is activated. If the workflow is not active, the production URL does not accept requests. The test URL works because you are editing the workflow, but production does not. Confirm the active toggle is on. This is the most common cause of a webhook that works in test but not production.
Test URL versus production URL
The test and production webhook URLs are different. If the source application is configured with the test URL, production events go to the test endpoint and the production workflow never runs. Confirm the source sends to the production webhook URL. This is easy to miss because the test URL works when you test manually.
Reachability and hosting
The production webhook URL has to be reachable from the internet. If n8n is self-hosted behind a firewall or a network that blocks inbound requests, the webhook URL is not reachable and production events never arrive. Check the hosting setup and confirm the webhook URL is publicly accessible. This is a common issue with self-hosted n8n and does not affect cloud-hosted instances the same way.
HTTP method and authentication
The webhook trigger expects a specific HTTP method. If the source sends a POST but the trigger expects GET, the request fails in production even if the test used the right method. Check the method matches. Authentication also matters. If the webhook requires authentication and the production request does not include it, the request is rejected. Confirm the production request includes any required authentication.
How to test it
- 1.Confirm the workflow is activated.
- 2.Check the production webhook URL the source sends to.
- 3.Send a manual request to the production webhook URL and check the response.
- 4.If the request is rejected, check the HTTP method and authentication.
- 5.If the request times out, check the hosting and network reachability.
- 6.Confirm the source sends real production data to the production URL.
Frequently Asked Questions
Why does my n8n webhook work in test but not production?
The workflow may not be activated or the source may be sending to the test URL instead of the production URL. The production webhook URL only works when the workflow is active.
Can hosting affect my n8n webhook in production?
Yes. If n8n is self-hosted behind a firewall or a network that blocks inbound requests, the production webhook URL is not reachable. Check the hosting setup and confirm the webhook URL is publicly accessible.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
n8n Workflow Not Triggering: What to Check First
A workflow that works manually but not in production is almost always not activated. Confirm the active toggle, then check the trigger node type and credentials.
n8n Workflow Stops at a Node: How to Find and Fix the Failed Step
A node that stops tells you what it needed and did not get. Read the error message, check the input items and confirm required fields are present.
Webhook Works in Testing but Not in Production: What to Check
A test that passes proves the logic works. The production failure is an environment difference, so compare the endpoint, authentication, payload and trigger between the two.