Nodes
Nodes are the building blocks of your workflow. Each node type serves a specific purpose.
Node Types
| Node | Purpose | Icon |
|---|---|---|
| Agent | AI agent that performs tasks | Robot icon |
| Document | Shared knowledge/context | Document icon |
How Nodes Connect
[Agent A] ──→ [Agent B] ──→ [Agent C]
│ │
└───→ [Document] ←───┘
- Solid arrows: Execution flow (A runs before B)
- Dashed arrows: Document references (agents can read/write)
Choosing the Right Node
Use Agent Node When:
- You need an AI to perform a specific task
- The task has clear inputs and outputs
- You want model selection (Haiku/Sonnet/Opus)
Use Document Node When:
- Multiple agents need to share information
- You have standards/guidelines to enforce
- You need persistent context across agents
Quick Reference
| Property | Agent | Document |
|---|---|---|
| AI Model | Yes | No |
| Instructions | Yes | Content |
| Tools | Yes | No |
| Feedback Loop | Yes | No |
How Orchestration Works
When you export a workflow, an orchestrator is automatically generated. You don't need to configure it manually.
The orchestrator:
- Executes agents in the correct order based on your connections
- Manages feedback loops and retry logic
- Passes context between agents
Next Steps
- Agent Node - Detailed agent configuration
- Document Node - Sharing knowledge