Designing a Multi Agent Workflow | Multi Agent Workflows for Beginners | Part 5

Key Takeaways

So in today's session, we are going to build a similar supervisor agent and I'm going to share the notebook with you guys after this uh after this entire webinar as well. So you guys can go ahead and try it and then tweak it as per your u requirement and then you can move forward with how you actually want it to be. So this would be a user you can call it as uh any customer if you are trying to fulfill any request you can uh call it. So there was one one scenario we have been working on for quite some time. Let's say uh this is this supervisor agent is is built up for an healthcare industry. So think of some uh agents that a person who has been diagnosed with some issues. Uh let's say a person is a uh is a cancer patient. So think of some agents that this cancer patient actually need. Uh think of some doctors, think of some consulting appointments that this cancer patient really want so that he can actually uh move forward in his life with certainity. So the agent one would be a doctor that knows all of the all of his history, a doctor that has all of his medical records. And then the second doctor would be uh his nutritionist or anyone who who has all the knowledge of his past history, of his past medical records. Uh so this could be his personal nutritionist and the third agent would be uh anyone who would be there for his paliative care. So now as a cancer patient if I ask about some questions related to uh uh related to what was what was the summary of my last city scan. So this supervisor uh last city scan summary. So this supervisor going to route this question towards this agent one. What if I ask uh what vitamins should I consider while I'm taking this tablet? What vitamins uh should I take when I'm on these tablets? when I am taking XYZ tablets. So this question would be routed towards the second agent towards the nutritionist who have the complete understanding of what are the uh tablets uh this person is taking and how he can perfectly align it towards the nutritionist. And then the third question would be if if your uh cancer patient is uh is having some issues with his health this if if he's having any health issues it is going to directed towards the paliative care uh person. So consider all of these agents. They have their own personalities. They have their own skills. They have their own personas. They have been built meticulously based on the uh agentic information we have built on it. And having said that, then you build a supervisor or a router agent that is actually going to route these queries towards a certain ideas. Or think of an idea that it needs a consolidator. Sometimes and the consolidator would look like something that this agent would be directed towards uh from this after getting this medical after getting this medical records it is going to send all of this information to the nutritionist send information and based on this information I'm going to get the final answer. So this is the context I'm sending it towards the nutritionist and having said that this would be a this would be a consolidator workflow. It would look something similar to what we have learned here that this is your nutritionist agent or or you have your medical records over here and then you pass those medical records to the third agent to actually give you some ideas about what medical uh what is your medical history and then once you have your medical records and then you can pass it towards The third agent which is going to which will be your nutritionist and it is going to advise you based on that. So it is going to give you advice uh on what vitamins you should take. So that's the overall uh theoretical part of it. Why do we really need workflows? What are router workflows? God.