Multi-Agent
Category: Agent
Node id: multi-agent
Coordinates multiple AI agents working on sub-tasks using parallel, sequential, or debate strategies
What it does
- Parallel agent execution for concurrent sub-task processing
- Sequential agent execution with context passing between agents
- Multi-round debate strategy for consensus building
- Per-agent model and role configuration
- Accumulated context sharing across sequential steps
- Concurrent execution with goroutines and mutex-safe result collection
Use cases
- Multi-perspective clinical analysis (e.g., specialist panels)
- Ensemble reasoning for higher-confidence answers
- Debate-based verification of clinical recommendations
- Parallel data processing across specialized agents
Runtime
- Performance tier:
slow
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
task | text | Yes | The task for agents to work on |
context | text | No | Shared context for all agents |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Agent results; contains results (array), agents (count), and for debate: rounds and total_rounds |
success | boolean | No | Whether the execution completed without error |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| LLM Endpoint | llm_endpoint | string | Yes | Base URL of the LLM API | ||
| Strategy | strategy | enum | No | parallel | parallel, sequential, debate | Multi-agent coordination strategy |
| Agents | agents | json | Yes | Agent definitions array (name, role, model per agent) |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| API Key | api_key | secret | No | API key for the LLM provider |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Max Rounds | max_rounds | number | No | 3 | min 1; max 20 | Maximum debate rounds (debate strategy only) |
Errors
| Code | Description |
|---|---|
ENDPOINT_REQUIRED | llm_endpoint is not configured |
TASK_REQUIRED | No task input was provided |
AGENTS_REQUIRED | Agent definitions array is empty or missing |
UNSUPPORTED_STRATEGY | Strategy must be parallel, sequential, or debate |
Runtime notes
- Each agent result contains {agent, answer, status}; status may be 'error' with an error field
- Sequential strategy passes each agent's answer to the next agent as accumulated context
- Debate strategy returns 'rounds' (array of arrays) instead of flat 'results'
- Parallel execution uses goroutines; result array indices match the agents config order
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Something unclear? Send documentation feedback by email.