Start a flow when a run is approved
Use the Interactive run is approved trigger to continue work after a person approves an agent's interactive run on a task. For example, when a reviewer approves a coding agent's run, move the task to Ready for release or merge its branch.
How the trigger works
The flow starts when someone explicitly approves a paused, interactive agent run on a task, and the task is in the workflow state you chose for the flow. Approvals on runs that aren't about a task, such as runs on an epic or a repository, don't start this trigger.
The state filter lets you use different follow-ups for the same approval. For example, one flow can handle approvals while a task is In Review and another while it's In QA.
Before you start
You need permission to edit flows in the workspace.
The task's agent must use interactive runs that ask for approval. Approval settings are part of each agent's setup.
Create an approval flow
Go to Automation → Flows and create a flow. Choose Build a custom flow, or start from a template.
Enter a Flow name.
In the When row, choose Interactive run is approved.
In the if row, choose the workflow after workflow is, then the state after and state is. This is the state the task must be in when the run is approved.
Optionally, add a Semantic condition.
In the then row, choose one action:
Start an agent run – for example, start a review or documentation agent.
Move the task to a state – choose the destination state.
Merge into – enter the branch to merge the task's working branch into.
Select Create flow.
Settings
Setting | What it does |
|---|---|
Workflow | The workflow the task uses |
State | The state the task must be in when the run is approved |
Semantic condition (optional) | A plain-language check that must clearly match before the action runs |
Action | The follow-up step. See Choose a flow action |
Things to know
Only an explicit approval starts the flow. Cancelling a run or sending a message to it doesn't.
If the action moves the task into a state that starts other flows, those flows run as part of the same chain.
To see whether the flow ran or was skipped, open Automation → Activity.
Related
Was this article helpful?