Workflows¶
Workflows let you model and run multi-step business processes directly inside BotBoss. You define each step, assign it to an agent or a person, set dependencies between steps, and let BotBoss drive the process from start to finish — handling routing, approvals, and coordination automatically.
What you can do¶
Build multi-step workflows on a visual canvas. A workflow is a directed graph of steps. Drag to connect them, set which steps must complete before the next one starts, and position nodes however makes sense to your team.
Describe a workflow in plain English. Not sure where to begin? Type what you want the workflow to accomplish and BotBoss will propose a starting graph — steps, connections, and all — for you to review and accept before anything runs.
Assign steps to agents or people. Each step has an executor. Assign it to one of your BotBoss agents (for automated work) or to a human team member (for tasks that need a person). You can also designate an accountable owner separately from the executor.
Start with a trigger. A trigger node is the entry point of a workflow. It can fire manually — when someone clicks Run — or on a schedule.
Branch the flow with routers. A router node splits the workflow into branches based on conditions. Use exclusive routing (one branch fires), fan-out routing (all branches fire in parallel), or agent-judged routing (an agent decides which branch to take at runtime).
Loop over collections. A for-each node fans out the downstream work for every item in a list, running multiple branches concurrently.
Gate critical steps with approvals. An approval node pauses the workflow and waits for a designated person to accept or reject before the next step proceeds.
Control autonomy step by step. Each step has an autonomy setting. In Suggest mode (the default), a completed step surfaces the next one for a human to review and accept before it runs. In Auto mode, the next step fires automatically once its dependencies are satisfied.
Save templates and run instances. Mark a workflow as a template to reuse it. Each time you run a template, BotBoss creates a fresh instance with its own run history — the template itself is never modified.
How it works¶
Each step is a self-contained unit of work and can depend on others: a blocking dependency means the downstream step can't start until the upstream one finishes; looser relationships can be non-blocking. When you run a workflow, BotBoss fires the entry trigger and cascades through the graph as steps complete — routing branches, spawning loops, and surfacing approvals — until it finishes. Every step's run history and full transcript are available from the canvas.
Example — monthly close¶
A finance agent closes the AP and AR ledgers in parallel. Once both finish, a bank-reconciliation step assigned to the controller becomes available. After reconciliation, the agent runs flux analysis. A controller-review approval gates the close; on sign-off, the agent publishes the close summary.