Workflow:
When it reaches the sub-agents they never activate the tools.
Version: Version 2.6.4 (Self-Hosted)
Hi @Bruno_Dalla_Costa Welcome to the community the problem almost always is linked to the system and instructions you have provided , i mean the AI prompt and System prompt, when we use Sub AI Agent nodes we have to clearly define the sub AI Agent as a tool in the description and also in main agent in the AI prompt and the system prompt you have to explicitly mention how to use that and how that would work!
the description field on the sub-agent tool is what the parent agent uses to decide when and how to call it. if it’s vague, the parent skips it.
make the description extremely explicit — something like “call this tool when the user asks about contracts. it returns X format.” also add in the parent’s system prompt: “you MUST call [tool name] for [specific trigger]”. that usually fixes it.
+1 — hitting this in n8n 2.10.4 with agentTool typeVersion 3 having any tool wired (toolCode, toolWorkflow, or native HTTP Request tool). The V3 engine request fires on the first LLM tool-call decision, before the tool itself runs. V2 works because AgentExecutor.fromAgentAndTools runs the tool loop inline. Workaround works but blocks our V3 upgrade path. Would love to see a timeline on fixing V3’s tool invocation through the agentTool boundary.
This is expected. Gemini is not known for making tool calls reliably.
You may have to change to OpenAI or Claude for LLM
Yes, I use openAI for Gemini…