Workflows
Playbooks, not pipelines.
Describe a process in plain markdown. An agent executes it. Typed inputs, schedules and triggers, decision points that wait for a human, and artifacts you can trace.
How it works
Write the process. The agent runs it.
A workflow is a playbook prompt bound to an agent: the steps, the rules, the tone, in markdown anyone can read and edit. No node graphs, no YAML. Personal workflows for your own routines; shared workflows for the whole workspace.
Capabilities
Built for real processes
Triggers
Run manually, on a schedule, from an event, or directly on an entity.
Typed inputs
Structured parameters, including references to Volobox items.
Human decision points
The agent pauses with a structured question; the decision lands in your Inbox.
Journey & artifacts
Every run has a traceable journey, transcript, and produced artifacts.
Coding handoff
A workflow can open a coding session and carry work all the way to a PR.
Dry runs
Test a playbook safely before scheduling it for real.
Example
Release QA test-scenario generation
Point the workflow at a release; the agent reads the changes, drafts test scenarios as structured artifacts, and pauses for review where it matters. One playbook, repeatable every release.
Workflows run under the agent's autonomous authorization profile: approvals, limits, and audit included.
Where it fits
Automate the work between the systems.
CI/CD moves the code, and your tracker keeps the record. In between sits the human work: reading what changed, drafting the plan, asking for a decision, writing it down, telling the team. Playbooks automate that layer. It does not replace your pipeline; it runs the process around it.