N8n Webhook stays in Test mode after Save/Publish -> how to use Production URL?

Saman_Salari · December 26, 2025, 8:13am

Hi everyone,

I have an n8n Webhook node, and I want to use the production (non-test) webhook URL on my website.

However, no matter what I do, the webhook remains in Test mode after Save/Publish. As a result, I can’t use the production webhook URL as an input on my website.

Is there a way to keep the webhook in Production mode so I can use its production URL?

For clarity :

The workflow is Active.

I click Save / Publish

I do not manually click the Test option.

But after saving, the webhook still behaves as if it’s in test mode, and the issue remains.

If anyone has faced this challenge before or knows how to fix it, I’d really appreciate your help.

I really appreciate any help you can provide.

wandinie · December 26, 2025, 8:32am

Hi @Saman_Salari. This is actually a common confusion with how n8n webhooks work.

So the Test/Production toggle you see in the webhook node, that’s just for viewing which URL you want to copy. It doesn’t actually control which webhook is “active” or working.

The real deal is this:

Workflow is Active = production webhook is live and working
Workflow is Inactive = only test webhook works (when you manually click “listen for test event”)

So even if after you save and it shows “Test URL” again, don’t worry - if your workflow is active (the green toggle at top), your production webhook URL is already working fine. The UI just defaults back to showing test URL but that doesn’t mean production stopped working.

What you should do:

Make sure workflow is Active
Copy the Production URL (click to switch view to production, then copy it)
Use that production URL on your website
Test it by sending actual request from your site

It should work even though the UI keeps switching back to test mode when you reopen the node.

Now if the production webhook truly isn’t receiving any requests even when workflow is active, that’s different - could be firewall issue, webhook path problem, or something with your hosting setup.