Skip to content
How to better conne...
 
Notifications
Clear all

How to better connect multiple HTTP nodes to my AI agent

20 Posts
3 Users
0 Reactions
6 Views
Blessing
(@blessing)
Posts: 11
Active Member
Topic starter
 

How can I send you a private message?

 
Posted : 20/05/2025 7:02 pm
King_Samuel_David
(@king_samuel_david)
Posts: 55
Trusted Member
 

Hello,

I've put together this to help explain:

This is my primary agent, which has access to sub-workflows containing AI agents. It functions as the central 'brain,' determining which sub-agent should handle a given request.

Subsequently, I link the other agents as tools to the main agent. Each call is directed to these:

  • ResearchAgent
    This agent initiates another AI agent workflow with specific research instructions (e.g., “research current social media trends for skincare” or “explain how RAG works”).
    The main agent forwards the original query along with a clear objective for the sub-agent.
  • Agent Confirm
    This agent has access to administrative tools and its sub-agent can execute workflows, such as the GitHub backup. The instruction is always explicit, for example: "Run the GitHub backup workflow in agent confirm". The agent strictly follows instructions and does not make assumptions.
  • DocumentAgent
    This agent is designed for file operations. It locates a specified file on Google Drive, retrieves it, and then stores it in Supabase for RAG-style access. It is paired with another AI agent that receives instructions such as: "Analyze this invoice and return the total due and due date." or "Answer: What company sent this invoice, and what is the payment method listed?"

:repeat:

All sub-agents operate strictly based on the explicit input provided to them, without making any assumptions.

:bulb:

The main agent consistently provides specific context and objectives for each task.

Each agent resides within its own sub-workflow, equipped with its own callin.io agent and tool configuration.

These trigger various actions, such as:

  • ResearchAgent returning structured data.
  • Agent Confirm executing workflows.
  • DocumentAgent retrieving documents and answering questions about them.

The main agent's role is solely to delegate, await results, and then respond. It never acts independently, only routing tasks to the appropriate tool and returning the output once completed.

This setup is not exhaustive but demonstrates a viable structure for organizing agents.

:slight_smile:

Hope this is helpful.

 
Posted : 21/05/2025 6:25 am
Blessing
(@blessing)
Posts: 11
Active Member
Topic starter
 

Hi, thanks for your response.

How can I share my workflow for you to review?

 
Posted : 21/05/2025 7:17 am
Wouter_Nigrini
(@wouter_nigrini)
Posts: 31
Eminent Member
 

It's a good practice to establish a "default" set for a switch node using the fallback option. This ensures that even when none of the specified conditions are met, the workflow continues along a default path instead of halting.

 
Posted : 21/05/2025 11:39 am
King_Samuel_David
(@king_samuel_david)
Posts: 55
Trusted Member
 

Feel free to share it via a Google Drive link, or send it to me directly via direct message if you prefer.

 
Posted : 21/05/2025 12:22 pm
Page 2 / 2
Share: