Choose a flow action

An action is what a flow does after its trigger fires. You choose it in the then row of the flow composer. Each flow has one action. To do several things in sequence, chain flows together, for example by moving a task into a state that starts another flow.

Available actions

Action in the composer	What it does	Works with
Start an agent run	Runs the agent you choose on the event's task, a specific target, or the whole workspace	Every trigger
Move the task to a state	Moves the task to the workflow state you choose	Task state and run approval triggers
Merge into	Merges the task's working branch into the branch you enter	Task state and run approval triggers

GitHub, GitLab, and schedule triggers can only start an agent run. When you switch to one of these triggers, the composer changes the action to Start an agent run.

Choose the right action

• Put an agent to work. Use Start an agent run to have an agent write code, review a change, triage an issue, or update documentation. See Start an agent run.

• Keep the board in sync. Use Move the task to a state to advance work automatically, for example after an approval. See Move a task to another state.

• Ship approved work. Use Merge into to merge the task's branch once a run is approved or the task reaches a release state. See Merge a task branch.

Add a condition before the action

For event triggers, you can add an optional Semantic condition above the then row. Describe in plain language when the action should run, in up to 500 characters. Helpin checks the event and the task's title and description. The action runs only when the condition clearly matches; otherwise it's skipped and the result appears in Automation → Activity.

Semantic conditions must be enabled for your workspace. If they aren't available, the composer tells you why.

Related

• Trigger types

• Creating a flow