Workflows

Workflows let you chain multiple agents together into automated pipelines. Use the visual canvas to define triggers, conditional branches, and sequential agent handoffs โ€” then track per-step execution status in real time.

๐Ÿ”€ Workflow Builder
โ–ถ Run
Save
๐Ÿ””
New Ticket
Trigger
โ–ถ
๐Ÿค–
๐ŸŽต Aria
Code Review
โ–ถ
๐Ÿค–
๐ŸŽป Maestro
Coding Agent
โ–ถ
โœ…
Done
End
โ— Active Ticket Review & Code Pipeline ยท Triggered 4 times this week
The Workflow Builder โ€” design automated multi-step pipelines visually

Visual Workflow Builder

Workflows are built on a React Flow canvas. Nodes represent actions and agents; edges define the execution order and conditions. The builder supports drag-and-drop node placement with snap-to-grid alignment.

๐Ÿ’ก

Use case example: A typical SDLC workflow might look like: Trigger (new Jira ticket) โ†’ Coding Agent โ†’ Code Review Agent โ†’ Update Jira status. Each stage waits for the previous one to complete.

Workflow Starter Templates

Instead of building workflows from scratch, you can use pre-built Workflow Starter Templates โ€” carefully designed multi-agent pipelines that you can use immediately or customize to fit your needs.

โšก
Pre-built blueprints

Each template is a complete, tested workflow that combines multiple agents in a logical sequence โ€” e.g., Planning Agent โ†’ Coding Agent.

๐Ÿ”ง
Auto-agent creation

Missing agents are created automatically when you use a template. If an agent already exists in your workspace, it's reused.

๐Ÿ“‹
Availability checking

Templates show which agents already exist, which will be created, and which are blocked due to missing prerequisites.

โœ๏ธ
Fully customizable

Use a template as a starting point, then edit agent assignments, add branches, or modify the pipeline in the visual builder.

Available Templates

TemplateStepsDescription
Plan โ†’ Code Pipeline Planning Agent โ†’ Coding Agent A two-step workflow that combines analysis and implementation. The Planning Agent creates a detailed plan; the Coding Agent implements the solution based on that plan.

How to Use a Template

  1. Navigate to Templates: Go to the Templates page and select the Workflow Templates tab.
  2. Review the Template: Click the ๐Ÿ“– icon to see the usage guide, or click the card to open the usage modal.
  3. Check Agent Availability: The modal shows which agents exist, which will be created, and any blocking issues.
  4. Confirm: Click Use Template. Missing agents are created automatically, then you're taken to the Workflow Builder with the template pre-loaded.
  5. Customize (Optional): Adjust agent assignments, add branches, or modify the workflow as needed.
  6. Save: Give your workflow a name and save it. You can now trigger it manually or connect it to events.
๐Ÿ’ก

Pro tip: Templates are a fast way to get started. Create your first workflow from a template, then build custom workflows as you learn the patterns.

Node Types

โšก
Trigger Node

Defines what starts the workflow. Triggered manually or by an event such as a new ticket matching certain criteria (status, priority, label).

๐Ÿค–
Agent Node

Executes a deployed agent as a workflow step. The agent receives the ticket context from the trigger and produces output passed to the next node.

๐Ÿ”€
Condition Node

Branches the workflow based on a rule (e.g., if agent output contains "pass", route to Done; otherwise route to review queue).

๐Ÿ
End Node

Marks the terminal state of a workflow branch. Can trigger a status update on the originating ticket.

Execution Tracking

Each workflow execution creates a Job per agent node. All steps appear in the Jobs view, showing per-step status so you can see exactly where the workflow is and what each agent did.

StatusMeaning
PendingStep queued, waiting for the previous node to complete
RunningAgent is actively executing this step
CompletedStep finished successfully; output passed to next node
FailedStep encountered an error; workflow halted at this node