how to

n8n Test vs Production Webhook URLs: When to Use Each One

Use the test webhook URL while building a workflow in the editor, and use the production webhook URL only after the workflow is active.

Primary query: n8n test webhook production webhook Intent: troubleshooting Applies to: n8n workflows, webhooks Opportunity: 98 Source-backed draft

Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.

Quick Answer

Use the test webhook URL while building a workflow in the editor, and use the production webhook URL only after the workflow is active.

Problem Pattern

The workflow works during manual editor testing but fails after the URL is pasted into a real third-party service.

Key Facts

Test URL: Designed for testing while the workflow is open and listening.
Production URL: Designed for active workflows and real integrations.
Common mistake: Pasting a test URL into a third-party production webhook configuration.
Activation: Production webhooks require the workflow to be active.

Recommended Steps

During workflow design, copy the test URL from the Webhook node.
Trigger the test URL while the editor is waiting for input.
Once the workflow works, activate it.
Copy the production URL and paste it into the external app.
Send one production request and verify the execution appears.

Verification

Test calls appear while the editor is listening.
Production calls appear after activation.
The external app stores the production URL, not the test URL.

Warnings

Do not use test URLs for real production integrations.
If a production webhook does nothing, check workflow activation first.

Best For

Users confused by the two URLs shown in the Webhook node.
Workflows that pass editor tests but do not run from a live app.
Teams preparing to move a webhook workflow from development to production.

Not For

Non-webhook trigger nodes.
Outgoing API requests from the HTTP Request node.
Cases where the workflow should intentionally stay manual-only.

Common Mistakes

Saving the test URL in Stripe, Typeform, GitHub, or another external app.
Expecting a production webhook to work while the workflow is inactive.
Changing the webhook path after a third-party app already stores the old URL.
Testing only in the editor and never making an external production request.

Examples

URL selection rule Use this as the simple decision tree.

Building the workflow in the editor? Use the test URL.
Connecting a real third-party app? Activate the workflow and use the production URL.
Changed the path or domain? Update the third-party app.

Production handoff checklist Run this before handing the URL to another tool.

Workflow active: yes
Production URL copied: yes
Public domain correct: yes
HTTPS valid: yes
External smoke test received: yes
Execution history checked: yes

FAQ

Can I use a test webhook for production?

No. Test URLs are for development while the editor is listening. Production integrations should use the production URL on an active workflow.

Does activating a workflow change the URL?

The Webhook node exposes a production URL intended for active workflows. Always copy the production URL after the workflow path and public domain are final.

Why did a third-party app keep calling the old URL?

External apps store the URL you give them. If you change path, domain, or test versus production mode, update that app's webhook settings.

Sources

n8n Webhook Node Accessed 2026-05-07