Rules that run when a card moves.
Choose the columns a card moves from and to, add conditions, and list what should happen: assign it, tag it, set its deadline, comment, move it on, hand it to a routine or send it to a webhook.
- Review goes to Rae
When a card moves into Review → assign to Rae, add the tag needs-review and set the deadline 3 days out
- Pair reviews
When a card moves from In Progress to Review → assign to one of Anna or Boris in turns
- Tell the release bot
When a card moves into Review, if it has a pull request and it has commits → send the card to the webhook at hooks.example.com
- Agent cards go to Claude
When a card moves into To Do, if it has the tag agent → hand it to the routine «Hand to Claude»
- Back to the authorOff
When a card moves out of Review, if an AI agent moved it → give back to the previous assignee and comment “Back to you for a look.”
- Old QA lane
When a card moves into a deleted column → assign to Sam
Skipped: it names a column the board no longer has
When a card moves
A rule runs when a card moves between columns. Choose the columns it moves from, the ones it moves to, or both; a side left empty means any column. The Closed column counts only when you choose it, so closing or reopening a card sets off only the rules that name Closed.
Moves made in the app, by an AI agent, by start-work and finish-work, or by a merged pull request that names the card all count. Creating a card doesn’t, even through an incoming webhook.
If every condition holds
Tag
The card has a tag, or lacks it.
Assignee
It is assigned to a particular person, to an AI agent, or to nobody.
Moved by
A particular person, or an AI agent, moved it.
Repository
It carries the repository’s tag, or has commits or a pull request from it.
Pull request
It has a pull request, or none. GitLab merge requests count.
Commits
It has commits linked, or none.
Then, in order
Actions run one after another, each on the card as the one before left it.
Assign
To a person; to one of a group, in turns or whoever holds the fewest cards in the column; to its reporter; to whoever had it before a column; back to the previous assignee; to whoever moved it; or to nobody.
Reporter and observer
Make a person, whoever moved the card or whoever had it before the reporter or the observer, or clear it.
Tags
Add tags, or remove them.
Deadline
Set it a number of days after the move, never before the card’s start date, or clear it.
Comment
Post a comment in Markdown, written as the rule.
Move it on
Send the card on to another column. Closing a card is left to people.
Hand to a routine
Start a Claude Code or Codex session that works the card as the routine’s agent.
Send to a webhook
Post the card and the move, signed, to one of the project’s webhooks.
Example rules
As a board’s settings list them: a name, then what sets the rule off and what it does, in one sentence.
Who has the last word
- Top to bottom
- Rules run in the order of the list, so a later rule has the last word. Drag them into the order you want.
- The mover’s choice stands
- When the person moving a card sets its assignee, reporter, observer or deadline in the same move, no rule overrides it.
- No chains
- A move made by a rule sets off no further rules, so rules can’t loop.
- Skipped, never half run
- A rule that names a column, person, repository, routine or webhook the board no longer has is marked Skipped, with the reason, and skipped whole.
- On and off
- Turn a rule off without deleting it, and on again when you need it.
Every change is on the record
A change a rule makes appears in the card’s history as Automation «name», and the person who moved the card stays the one who set it off.
Manage rules from a chat
Project admins can create, change, reorder and delete rules from an AI assistant with create-automation, update-automation, delete-automation and reorder-automations, and show-board lists every rule as a sentence.
Good to know
- Up to 20 conditions and 20 actions in a rule. There is no limit on the number of rules, and no run quota.
- Automations are on every plan. Handing a card to a routine needs the routine’s owner on Pro or Max.
- Project admins manage rules; everyone who can open the board can read them.
Automations
Questions about automations
Can a rule run on a schedule, or when a card is created?
No. Rules run only when a card moves between columns.
Can conditions be combined with OR?
No. Every condition in a rule has to hold. For two alternatives, write two rules.
Can a rule close a card?
No. Move it on sends a card to an ordinary column, never to Closed.
Does one rule’s move set off other rules?
No. Moves made by a rule set off no further rules, so rules can’t loop.
Do automations cost extra?
No. They’re on every plan, with no limit on runs.
Give your next project a clear starting point.
Create a board, add your first task, and bring your team together.
No credit card required · Free forever plan