Workflows
Workflows
A workflow chains agents, branching logic, loops, and human approvals into one executable graph. Build it on a visual canvas, version it, ship it.
What you'll learn
- What a workflow is and how it differs from a single agent
- When to choose a workflow over an agent
- The three execution patterns: Workflow, MapReduce, Manager-Worker
- The full node palette you have to work with
Workflow vs. single agent
Use a single agent when one LLM with one tool list can do the job — ticket triage, a Q&A bot, a single Slack responder. Reach for a workflow when you need deterministic branching, parallel fan-out over a list, a human approval gate, or coordination between specialist agents. Workflows appear in the sidebar under Multi-Agents.
The three execution patterns
Every workflow you build maps to one of three patterns. Pick the right one before you start dragging nodes.
- 1
Workflow (sequential graph)
A directed graph of agents, conditions and approvals. Best when each step depends on the previous one — classify, then enrich, then act. - 2
MapReduce (fan-out)
Iterate a mapper agent over a list of items in parallel, then collapse with a reducer agent. Best for batch processing — score 500 leads, summarize 100 tickets. - 3
Manager-Worker (delegation)
A manager agent decomposes a task and dispatches sub-tasks to specialist worker agents, then assembles the result. Best for open-ended research and multi-skill execution.
The node palette
Drop these node types onto the canvas: Trigger (entry point), Agent (executes one configured agent), Condition (branching), Loop (map-reduce), Approval (human-in-the-loop), Sub-Workflow (nest another workflow), and Output (final result). Edges connect them in the order execution flows.
Frequently asked questions
- Can a workflow call another workflow?
- Yes. Drop a Sub-Workflow node and pick the target. The parent waits for the child to complete, then continues with the child's output.
- Are workflows versioned?
- Every Save & Publish creates a new version. You can roll back to a previous version at any time without losing the current draft.
- How are workflows different from a chain of tool calls in a single agent?
- A single agent decides what to do at runtime. A workflow encodes the structure up-front — which means you get deterministic branching, parallel execution, approval gates, and clean audit trails that ad-hoc tool chaining cannot provide.
- Can a workflow start without a Trigger node?
- No. Every workflow needs exactly one Trigger node as its entry point. The trigger defines how the workflow is invoked — webhook, schedule, chat, email, Slack, or manual.