Run Agents Team¶
Coordinates a team of one or more AI agents to collaborate on a task. You can choose how the conversation is organized (Cycle, Smart, or Manage), limit message count and runtime, and optionally request a final summary. Returns the multi-agent conversation transcript and a condensed summary.

Usage¶
Use this node after creating one or more agents with Create Agent. Connect the agents to agent_1 (and agent_2 ... agent_31 as needed), provide the task, select the team interaction type, and set constraints (message limit and timeout). Useful for complex tasks that benefit from multiple specialized agents discussing and solving a problem.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| agent_1 | True | AGENT | First agent (and minimum required). Defines the initial team member. You can run with only one agent or add more using agent_2 ... agent_31. | AGENT object from Create Agent |
| team_type | True | ['Cycle', 'Smart', 'Manage'] | Interaction mode for the team: Cycle (round-robin speaking), Smart (next speaker chosen by an LLM based on context), or Manage (conversation flow managed by an orchestrator). | Smart |
| task | True | STRING | The task or problem statement the agents should solve together. | Draft a product launch plan for a new mobile app targeting college students. |
| summarize | True | BOOLEAN | If true, returns a concise summary of the agents' discussion and final answer in addition to the transcript. | true |
| max_messages | True | INT | Maximum number of messages the team may generate. 0 means no limit. | 20 |
| max_timeout | True | INT | Maximum execution time in seconds. If exceeded, the run is aborted. | 300 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| messages | STRING | Full transcript of the multi-agent conversation as a single formatted string. | Agent_1: Outlines approach... Agent_2: Adds research... Agent_1: Proposes final plan... |
| summary | STRING | Concise summary of the conversation and answer to the task. May be empty if summarization is disabled. | A three-phase launch strategy with timeline, channels, and KPIs. |
Important Notes¶
- Team organization: Cycle is round-robin; Smart selects the next speaker contextually; Manage uses an orchestrator to guide the flow.
- Agent chaining: Additional agent inputs (agent_2 to agent_31) appear only after the previous agent input is connected.
- Single-agent mode: You can run with only agent_1 connected if you don't need a multi-agent discussion.
- Message limit: Set max_messages to 0 for no limit; otherwise, the team stops when the limit is reached.
- Timeouts: max_timeout bounds the total execution time; ensure it’s large enough for your task complexity.
- Transcript and summary: The transcript includes the full dialog; the summary is a condensed answer and may be empty if summarize is false.
- Agent configuration: Agents inherit their model, tools, role, and system prompt from the AGENT objects you connect (created via Create Agent).
- Capacity: Up to 31 agents are supported (agent_1 through agent_31).
Troubleshooting¶
- Empty or missing summary: Ensure summarize is set to true; otherwise the summary may be empty.
- Run stops early: Increase max_messages if the conversation reaches the message cap; verify that team_type suits your needs.
- Timeouts or failures: Increase max_timeout for longer tasks. Network or service issues may cause failures; retry after adjusting timeout.
- No optional agent inputs visible: Connect agent_1 first; subsequent agent inputs appear only after the previous is set.
- Unexpected conversation quality: Review each agent’s role and system prompt from Create Agent, and consider switching team_type (e.g., Smart instead of Cycle).
Example Pipelines¶