So.. I’ve build a team of multiple make agents as I feel that there are too many tasks/tools to be handled by a single agent. (I haven’t found any design directions by Make.com on how to set this up, or if it’s even advisable?)
My current setup involves 1 main (director) agent and 3 subagents (CRM, Calendar, Search):
The goal is for me to only communicate with the director agent so it can handle instructing the subagents by delegating tasks and then report the outcomes back to me.
I’ve written their system prompts accordingly (so they are aware of their roles and responsibilities).
My setup seems to work quite well although my director agent is struggling to differentiate between messages coming from me and questions coming back from a subagent.
How it works is that I chat with Director Agent through Telegram:
Then the director agent calls its delegation tool/scenario:
in scenario inputs it defines which subagent to call and what message to send to it
subagents then do their thing through calling their own tools and feed back result through scenario output, this works well when subagents understand the task right away.
This is where it goes wrong: in the situation where the subagents reply with a question to the director agent, The director agent replies to that question by answering in Telegram conversation (to me).
Any idea how I could change this architecture so Director Agent can finish its conversation with subagents before replying to me? (it would basically need to be in multiple conversations at once)