Flow actions
The action is what a flow does once its trigger and filters match. You choose it on the then row of the flow editor. This page explains the three actions and when each is available.
Available actions
Action | What it does | Available for |
|---|---|---|
Start an agent run | Starts the agent you choose on the target you choose | All triggers |
Move the task to a state | Moves the task that triggered the flow to another workflow state | Task enters a workflow state, Interactive run is approved |
Merge into | Merges the task's working branch into a branch you name | Task enters a workflow state, Interactive run is approved |
For GitHub, GitLab and schedule triggers, Start an agent run is the only action.
Start an agent run
On the then row, choose Start an agent run.
After using, choose an agent. Agents that can't work on your chosen target are greyed out; hover to see why.
On the on row, choose where the agent works. See Flow targets.
For GitHub and GitLab triggers, you can also open + branch overrides:
base – agent checks out: the branch the agent starts from, such as
{base_branch}orrelease/2026.04.task – branch is: the branch the agent works on. Use
{task_branch}for the agent's own working branch.
The run then follows the agent's own settings, including whether it needs approval. You can follow it in Activity.
Move the task to a state
On the then row, choose Move the task to a state.
After to, choose the destination state.
Use this to move work along automatically, for example from Approved to Ready to ship. If the task is already in the destination state, nothing happens. Moving a task can start other flows that watch the new state. The move appears in the task's activity history.
Merge into
On the then row, choose Merge into.
After into branch, enter the branch to merge into, such as
main. You can use{base_branch}to merge into the task's base branch.
Helpin merges the task's working branch into that branch. The task needs a repository and a working branch; if either is missing, the flow does nothing. After a successful merge, the task's delivery status changes to merged, and the merge appears in the task's activity history.
Where to see results
Agent runs appear in Automation → Activity and in the flow's Recent runs. State moves and merges appear in the task's activity history instead.
Related articles
Was this article helpful?