Skip to content

Commit 7d20b52

Browse files
authored
new FAQ - Workflow vs Team (#210)
1 parent a34a823 commit 7d20b52

File tree

2 files changed

+42
-1
lines changed

2 files changed

+42
-1
lines changed
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
title: When to use a Workflow vs a Team in Agno
3+
sidebarTitle: When to use a Workflow vs a Team in Agno
4+
---
5+
6+
Agno offers two powerful ways to build multi-agent systems: **Workflows** and **Teams**. Each is suited for different kinds of use-cases.
7+
8+
---
9+
10+
## Use a Workflow when:
11+
12+
You want to execute a fixed series of steps with a predictable outcome.
13+
14+
Workflows are ideal for:
15+
16+
- Step-by-step agent executions
17+
- Data extraction or transformation
18+
- Tasks that don’t need reasoning or decision-making
19+
20+
[Learn more about Workflows](https://docs.agno.com/workflows/introduction)
21+
22+
---
23+
24+
## Use an Agent Team when:
25+
26+
Your task requires reasoning, collaboration, or multi-tool decision-making.
27+
28+
Agent Teams are best for:
29+
30+
- Research and planning
31+
- Tasks where agents divide responsibilities
32+
33+
[Learn more about Agent Teams](https://docs.agno.com/teams/introduction)
34+
35+
---
36+
37+
## 💡 Pro Tip
38+
39+
> Think of **Workflows** as assembly lines for known tasks,
40+
> and **Agent Teams** as collaborative task forces for solving open-ended problems.

mint.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1168,7 +1168,8 @@
11681168
"faq/connecting-to-tableplus",
11691169
"faq/could-not-connect-to-docker",
11701170
"faq/openai_key_request_for_other_models",
1171-
"faq/structured-outputs"
1171+
"faq/structured-outputs",
1172+
"faq/When-to-use-a-Workflow-vs-a-Team-in-Agno"
11721173
]
11731174
},
11741175
{

0 commit comments

Comments
 (0)