Improve AI Agent 'Call n8n workflow tool'

Feature Requests
1

The idea is:

When using a “Call n8n workflow tool” for an AI Agent it would be extremely helpful if all the parameters, description and specific input definition could be saved with the workflow/tool definition itself. This way once a tool is properly defined it can be hooked up to any Agent without having to copy the configuration. And if something changes it would be changed for all agents and doesn’t have to be done manually for any agent that uses this tool.

This would allow for building practices more like relevance.ai agents which in my opinion is the biggest competitor for n8n to build complex AI Agent systems.

And while you are at it you could also allow multiple "Call n8n workflow tool"s to be defined in one workflow! This would allow much cleaner setups. As example I have an Google Calendar Agent which has 5 tools that are all using google calendar nodes and API. Right now I have to create 5 different workflows and when something changes in the google API I have to find all 5 of them and see if they need to be changed. Would be really nice if they could all be in one workflow with a special tool-trigger node where all the above items can be configured.

My use case:

We are implementing lot’s of complex “Teams of Agents” meaning that for example a Director Agent handles the input and delegates tasks to a number of specialised Agents. (Which are essentially other workflows called as tool)

I think it would be beneficial to add this because:

It would make it far easier to stitch together Teams of Agents and give them other Agents or other complex AI automations as tools.

Are you willing to work on this?

I’d be happy to support! This would really greatly improve the attractiveness of n8n for serious AI Agent builders such as us.

2

I have the same issue. Right now every Call n8n Workflow Tool node keeps its own local copy of the Description prompt, so we have to maintain the same text in several places. And that text can be quite substantial (how to format JSON correctly, what parameters to pass in query etc.).

I’d suggest doing something like:

  1. Add an optional “Tool description” field to the Execute Sub-workflow Trigger (or Workflow Settings).
  2. Make the Call n8n Workflow Tool node pre-populate its Description from that field
  3. Warn—or ideally auto-update—caller nodes if the sub-workflow’s description changes later.