Workflows are in beta. This area is under active testing and is not recommended for production traffic yet. Pin business-critical automations to Agent actions & Tools or Agent Tasks for now, and use Workflows for experiments and internal tooling.
A workflow is a multi-step automation built from triggers, conditions, agents, and actions. Use one when the work spans more than a single conversation or task.
Agent vs Task vs Workflow
- Agent — handles a single conversation in real time
- Task — does background work, often on a schedule, alone
- Workflow — orchestrates multiple steps, often across multiple agents and external systems
What's in a workflow
- Trigger — what starts it. A new lead, a webhook, a schedule, a message containing a keyword
- Conditions — branches based on data ("if the lead is enterprise, route to sales; otherwise, drop into the self-serve flow")
- Agent calls — one or more agents handling specific steps
- Actions — the same custom and built-in actions your agents have, callable from any step
- Outputs — where final results go
When to reach for a workflow
- The flow has clear branching ("if X, do A; if Y, do B")
- Multiple agents collaborate (qualifier → researcher → writer)
- You need a deterministic path, not an open-ended conversation
- The flow gets triggered by something outside Chatzuri (a CRM event, a webhook from your billing system)
Tip
If you can describe the work as a flow chart, it belongs in a workflow. If it's an open-ended conversation, an agent is the right tool.
Where to find workflows
From your team page, click the Workflows section, or use the agent / workflow switcher in the header.