Error in calling webhook URL

Questions
1

I am using webhook trigger that has URL https://n8n.abc.com/webhook

but when i call this webhook through http node from another workflow, i get this error:

Problem in node ‘Start Workflow via Webhook’ The connection to the server was closed unexpectedly, perhaps it is offline. You can retry the request immediately or wait and retry later

3

Hi @mohamedelnady-406
I suppose that the target webhook flow must be active, and by seeing your webhook URL it seems incomplete maybe you have hide that for now. Let me know if that flow is published, then we can get into the logs and proxy verification.

4

Hey @mohamedelnady-406 , this is almost always one of these two things:

Your webhook is running in test mode. Test mode only works when you are sitting on that workflow page clicking “Listen for Test Event”. The moment you leave, it goes offline. You need to activate your workflow using the toggle at the top right so it stays live permanently.

Once activated, make sure your HTTP node is pointing to the production URL. Test URL contains webhook-test in the path and production URL contains webhook. They are different, so double check which one you are using in your calling workflow.

Fix these two things first and it will most likely start working.

5

the workflow is published
and this is my uel
https://n8n.abc.com/webhook/parallel-subworkflow-target

6

the workflow is published
here is my production URL, i am already using this in HTTP node
“https://n8n.abc.com/webhook/parallel-subworkflow-target”

7

Can you share the url of your published workflow

8

hi @mohamedelnady-406 , good day!

I’d first double-check that the HTTP Request node method matches the Webhook node method exactly and that the path is the exact production path from the Webhook node. n8n has separate test and production webhook URLs, and production executions use the published workflow version. If all of that looks correct, then the error sounds more like a server / reverse proxy / custom-domain webhook config issue than a problem with the workflow itself, because webhook routing on custom domains depends on the instance webhook URL setup being correct.