N8n Workflow Tool Invalid URL ERROR

Describe the problem/error/question

What is the error message (if any)? * Invalid URL

  • Execution Error.

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Invalid URL

Error details

From Call n8n Workflow Tool

Error code

none

Other info

Item Index

0

Run Index

0

Node type

@n8n/n8n-nodes-langchain.toolWorkflow

Node version

2 (Latest)

n8n version

1.76.3 (Self Hosted)

Time

5/2/2025, 0:09:16

Stack trace

NodeApiError: Invalid URL at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/routing-node.js:159:23) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:683:23) 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

Call n8n Workflow Tool

Parameters

Settings


Docs

See an example of a workflow to suggest meeting slots using AI here.

Name

Description

This tool will call the workflow you define below, and look in the last node for the response. The workflow needs to start with an Execute Workflow trigger

Source

Workflow

I wish this node would…

Information on your n8n setup

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

Can you please share your workflow code with us?
You can copy and paste it inside a code block.

To create a code block you just have to click here:
image

Your workflow will show up like this:

But try upgrading your n8n instance, just in case.
In your version 1.76.3 there’s a bug that prevents the tool “Call Workflow” from executing correctly.

It’s been fixed on version 1.80.4
So any newer version will do.