Hello,
I’m using n8n Cloud under the workspace ventunosrl.app.n8n.cloud.
In my workflow named “Ospedale Centrale Murgante”, the Webhook node only shows the Test URL button as active, while the Production URL button remains disabled and cannot be selected.
Even though the workflow status shows “Active”, the node continues to display only the test endpoint (n8n.io - Workflow Automation…) and never registers or shows the corresponding Production URL.
I have already tried the following:
Deactivating and reactivating the workflow
Reloading the editor
Logging out and back in
…but the issue persists.
It seems that the webhook is not being correctly registered in production mode.
Could you please check this and, if possible, force the activation of the Production URL for this workflow?
Thank you very much for your help.
what is your n8n version ?
If possible, try upgrading
The button itself it’s not a choice.
It’s showing you what’s the test url and production url is.
Even you Activate the workflow. It defaults shows you the test url which is normal.
You just need to copy the production url to the place you need to paste.
Then you should receive the request.
Hello,
thank you for your reply.
I have already tried with different n8n versions, but the same issue happens — the webhook still doesn’t switch visually to the production URL even after activating the workflow.
So it doesn’t seem related to the version.
Hello,
thank you very much for your explanation.
I just want to make sure I fully understand, because the behavior we’re seeing is a bit unusual.
Even when the workflow “Ospedale Centrale Murgante” is fully activated, the Webhook node always keeps the “Test URL” button highlighted — the “Production URL” button never appears active.
The webhook still works in test mode, but the production endpoint doesn’t seem to receive any request when triggered from external sources (for example, from our GPT-based medical team integration).
Before we added the other “doctor” nodes (the AI assistants inside the same workflow), the webhook behaved normally — it switched to production and accepted external connections correctly.
After expanding the workflow with those additional nodes, the production mode stopped responding and remained visually stuck on “Test URL”.
Could this be related to the workflow complexity or to how n8n Cloud registers the webhook in production mode?
Please let me know if there’s a specific way to reset or re-register the webhook so the production endpoint becomes fully active again.
Workspace: ventunosrl.app.n8n.cloud
That “buttons” are only to switch and see the actual URL there(if is localhost on both, you need to setup WEBHOOK_URL in your environment variables).
The active/non-active “Toggle button” is making public your endpoint.
I think you misunderstood the UI .
Hello,
thank you very much for clarifying — that helps a lot.
Just to be sure we’re on the same page:
I fully understand that the buttons are only for displaying the URLs and that the Activate Workflow toggle is what actually makes the endpoint public.
However, in my case, even with the workflow activated (status “Active”), external requests sent to the production URL don’t seem to trigger any execution, while the test URL works correctly when the workflow is running in test mode.
So it seems that the production endpoint isn’t receiving data, even though the workflow is active.
Could this be related to the webhook registration inside n8n Cloud, or perhaps to the recent expansion of the workflow (we added multiple AI “doctor” nodes)?
If you have any suggestion to re-register or refresh the production webhook endpoint, I’d be glad to try it.
Thank you again for your time and patience!
You got it now.
Is a public URL?(not localhost).
What do you use to test out as trigger, Webhook trigger, Chat trigger ?
Hello Parintele,
thank you for the follow-up!
Yes — it’s a public URL on n8n Cloud, not localhost.
The domain is:
https://ventunosrl.app.n8n.cloud
The workflow uses a Webhook Trigger node as the entry point (not a Chat Trigger).
The webhook works correctly when using the Test URL during “Execute Workflow”, but once the workflow is activated, requests sent to the Production URL don’t start any execution — nothing appears in the execution list.
So the issue is not with visibility or the workflow status, but that the production webhook endpoint doesn’t actually trigger executions, even though it’s active and publicly reachable.
Please let me know if there’s a way to refresh or re-register the production webhook on n8n Cloud.
Thanks again for your time and help!
Since you know what informations your webhook receives , make a curl request (Postman/ CLI using cUrl) to your webhook , and see the response.
Share an image with the webhook settings …
Hello Parintele,
thank you for the follow-up.
I’ll run a direct test as you suggested with REQBIN . (see attache file workflow001 with error message 500 (Internal Server Error))
I know exactly what the webhook expects (patient_id, text, attachments), so I’ll send a manual POST request using cURL / Postman (or ReqBin) to the production URL and check if any response is returned.
file worrkflow002 and workflow003 show setting in testurl and productionurl
thank you
Alberto
As you can see in the body response, you have a respond to webhook node at the end of your workflow (it seems that your Webhook trigger has other options selected , it will respond anyway.) .
Remove that at the end, or change the option.
Hi Parintele,
thank you very much for your support and patience!
We identified the issue with the n8n webhook that remained stuck in Test URL mode and, after several checks, we successfully fixed the configuration by correctly linking my AI Medical Team with n8n.
Everything is now stable — the data is being sent and stored automatically, and the whole workflow runs as expected.
Thanks again for your help!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.