Set up board automations

Every team has steps that are always the same: card is finished → tell someone → leave a comment. That is exactly what an automation takes off your hands. Rules are available from Private Plus upwards; the Free plan includes 0 runs per month.

What you need

• Private Plus or higher. Included runs: Plus 200, Business Standard 1,000, Business Pro 25,000 per month — see pricing.
• A board with a few cards to test against.
• Rights to manage the board.

1. Check your plan

On Free you can create a rule but it will never run — the allowance is zero. From Private Plus rules actually fire.

2. Understand the three parts of a rule

Every rule reads as one sentence: when something happens, and if something else is true, then do this.

• Trigger — the event: card created, card moved, assignee added, epic added, priority changed, due date arrived or approaching, time logged, started, stopped. For engineering teams also: branch created, commit pushed, pull request opened or merged, CI passed, CI failed, release published. Plus a scheduled trigger for anything that happens on a clock rather than on an event.
• Conditions — optional, and they narrow: only high-priority cards, only in a particular column.
• Actions — what happens: add or remove an epic, move to a column, set priority, assign someone, notify, add a comment, call a webhook, set a custom field, start or stop a timer, create a new card — including on another board in the same workspace.

3. Build your first rule

An example almost every team can use:

• When a card is moved into the "Done" column,
• then add a comment ("Finished — please give this a quick review") and notify the assignee.

Two actions in one rule is entirely normal; they run in order.

4. Narrow it with conditions

Without a condition the rule runs for every card. Usually you want less: only high-priority cards, only those carrying a particular epic, only ones with a due date set. Conditions are the difference between a useful rule and one the team switches off after three days because it is too noisy.

5. Test the rule and read the run history

Trigger it once for real — move a test card. The run history then shows whether it fired and what it did. A run has three outcomes: succeeded, failed, or skipped (a condition did not match). Skipped runs do not count against your allowance.

6. Disable, copy or hand over a rule

Rules can be disabled temporarily rather than deleted — handy while you narrow something down. And because a rule belongs to the board rather than to whoever built it, you can hand it to someone else. Nothing quietly stops working the next time the team changes.

Troubleshooting

• The rule never runs. Check the allowance first (Free = 0 runs), then the conditions — usually one is too narrow.
• It runs too often. The trigger is too broad. "Card moved" covers every column; narrow it to the destination.
• Nothing arrives in Slack. Check the webhook URL. Slack and Discord both expect an incoming webhook URL you have to create there first.
• Allowance used up. Successful and failed runs count. Tidy up noisy rules or change plan.

Next steps

• Create custom fields on cards — fields a rule can set.
• Git on the board — triggers from commits, pull requests and CI.
• Pricing — included runs per plan.