Move a task to another state
The Move the task to a state action moves a task to another state in its workflow when a flow runs. Use it to keep your board up to date without manual clicks, for example to move a task to In Review when an agent's run is approved.
When you can use it
This action is available with the two workflow triggers:
Task enters a workflow state
Interactive run is approved
It always acts on the task from the triggering event. You can't use it with GitHub, GitLab, or scheduled triggers.
Set up the action
Go to Automation → Flows and create or edit a flow.
In the When row, choose Task enters a workflow state or Interactive run is approved.
In the if row, choose the workflow and the state that starts the flow.
In the then row, choose Move the task to a state.
After to, choose the destination state. The list shows the states of the workflow you selected.
Select Create flow or Save changes.
If you don't choose a destination, the composer shows “Choose the destination state” and you can't save.
What happens when it runs
The task moves to the destination state, and the task's activity records that the flow moved it.
If the task is already in the destination state, nothing changes.
Moving the task counts as the task entering a new state, so flows that start on that state run next.
Build a pipeline with chained flows
Because each move can start the next flow, you can build a simple pipeline from several flows. For example:
When a task enters In Progress, start a coding agent on it.
When that run is approved while the task is In Progress, move the task to In Review.
When the task enters In Review, start a review agent.
Helpin protects you from loops. The same flow won't run twice in one chain, and a chain stops after 10 steps.
Related
Was this article helpful?