Webhook issue not working?

Hi i’m sorry but i am very new to this. i want to try to trigger a workflow from another workflow using a webhook. in my knowledge the way to do that is from using an HTTP node that inputs the webhook trigger link,but in my case when i do that it shows an error. HOWEVER when i test it by just putting the link in a new tab it was successfully able to do it. can anyone tell me what’s the issue?

The error message is:
Error code

ECONNREFUSED

Full message

connect ECONNREFUSED ::1:5678

Request

{ "headers": { "username": "Tessa", "wanumber": "62811393842", "accept": "application/json,text/html,application/xhtml+xml,application/xml,text/*;q=0.9, image/*;q=0.8, */*;q=0.7" }, "method": "GET", "uri": "http://localhost:5678/webhook/b25d01d4-465b-42b9-a40d-f097c98a0e48", "gzip": true, "rejectUnauthorized": true, "followRedirect": true, "resolveWithFullResponse": true, "followAllRedirects": true, "timeout": 300000, "encoding": null, "json": false, "useStream": true }

Item Index

0

Node type

n8n-nodes-base.httpRequest

Node version

4.2 (Latest)

n8n version

1.76.3 (Self Hosted)

Time

2/12/2025, 8:04:47 PM

Stack trace

NodeApiError: The service refused the connection - perhaps it is offline at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:525:33) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:632:19) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:881:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1215:20




Information on your n8n setup

  • n8n version: 1.76.3
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Mac Os

Try an Execute Sub-workflow instead?

You can now define the expected data in the Execute Sub-workflow Trigger-node, making data transport really easy.

1 Like

oh i guess that works. thank you!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.