Path: /docs/workflows

Custom workflows control how ticket status moves on a project, and optional automation rules on top of that.

Open workflows

text
https://getorchestrator.app/projects/{CODE}/workflow

You need access to the project (via the owning team or shared access).

Status workflow

The status graph defines columns/states and allowed transitions. The board columns follow this graph. Saving the status workflow updates how cards can move.

Typical uses:

• Match your delivery process (Backlog → Ready → In Progress → Review → Done)
• Restrict skips (for example, no jump from Backlog straight to Done)
• Keep multiple projects aligned on the same status names when you want consistency

Automation workflow

Automation rules sit beside the status graph. They can react to ticket changes (move column, assign, notify) when configured for the project.

API surface (session auth):

Method	Path	Purpose
GET	/api/projects/{code}/workflow	Load status + automation graphs
PUT	/api/projects/{code}/workflow	Save statusWorkflow and/or automationWorkflow

Agents can also drive delivery workflows through MCP tools such as workflow.start-next-ticket and workflow.create-pr when those are enabled for your token. See MCP Server.

Board vs workflow

Surface	Job
Board	Day-to-day move cards
Workflow desk	Edit the graph and automations behind those moves

Edit the workflow when the process changes. Use the board for daily work.

Related docs

• Board
• API Reference
• MCP Server