Start Trello automation with one clear handover: a known event, a small set of actions and somebody responsible for the result. Automating a confusing board usually makes its confusion harder to investigate. Agree what each list means before letting cards trigger work.
This guide assumes you already use Trello. Our Trello versus Asana comparison covers the broader platform decision.
Table of Contents
Choose what should start the automation
Atlassian’s automation overview separates event-driven rules, buttons pressed by a person, scheduled actions and actions tied to a card’s deadline. Use a rule when a board event should consistently cause the same response. Choose a card button when somebody needs to make a decision first.
For example, an editor deciding that work is ready for review is a human judgement. After that decision, adding the review label and the responsible colleague can be routine. Avoid treating a new label as evidence that someone actually inspected the work.
Build a small review-handover rule
Illustrative workflow: a consultancy uses Drafting, Review and Approved lists for proposals. An author moves a prepared draft into Review. The rule adds a Needs review label and the agreed reviewer.
Prepare a practice board and a clearly named sample card first. Then follow Atlassian’s custom automation instructions:
- Open the board’s Automation menu and choose a rule.
- Select the trigger for a card being moved into the Review list.
- Add the action that applies your Needs review label.
- Add the action that assigns the intended board member.
- Read the complete rule, then save it. Saving activates it.
Rules respond to colleagues’ actions too. Advanced trigger conditions narrow eligible cards; every added condition must match. Start with a rule colleagues understand.
Before moving a real proposal, agree who covers the reviewer during leave. The automation cannot establish that the chosen person has capacity. Keep the required response in the card description, such as approving the commercial terms or requesting specific changes.
Add useful context without copying the wrong information
Trello’s variable reference lists {cardname} for the current title and {cardlink} for its link. Card variables require a card in the automation’s context. If you add a comment action, an illustrative message is “Review requested for {cardname}: {cardlink}”. Inspect the rendered comment before expanding it.
A link can point the reviewer towards the current work, but it does not explain which attachment or version needs approval. Keep that instruction beside the draft. Do not automatically copy a proposal’s full contents into another channel merely because a variable makes it possible.
If cards are missing the same preparation information repeatedly, fix their starting structure. Our Trello card templates guide explains reusable briefs and checklists. A template and a rule can support the same process without performing the same job.
Budget for runs and operations separately
The current automation limits give Free Workspaces 250 runs and 2,500 operations monthly; Standard provides 1,000 runs and 20,000 operations. Quotas are pooled across the Workspace’s boards. Premium and Enterprise have unlimited runs but still limit operations. Individual runs currently have a 20-action/operation ceiling.
A trigger consumes a run; each action consumes at least one operation. Illustrative budget: 100 handovers with two ordinary one-operation actions would consume 100 runs and 200 operations. Adding a comment or moving the same card through review again increases usage. This is planning arithmetic, not measured performance.
Check the Workspace activity view before upgrading. Include automations already used on other boards and leave room for revisions. Quotas reset at midnight GMT on the first day of the month; do not assume an exhausted allowance renews at your local midnight.
Use the log to check the actual result
Open the relevant automation’s log from its entry in the builder. Atlassian’s log documentation says it records runs, actions, errors, warnings and changes to triggers or actions. The broader activity log shows work run on your behalf across accessible boards.
Use the following illustrative acceptance checks before handing over the rule. These are proposed checks, not test results.
| Sample action | Expected business result | Inspect |
|---|---|---|
| Move a prepared proposal into Review | The agreed reviewer and label are present. | Card membership, label and automation log |
| Move an unrelated card elsewhere | No review handover occurs. | Actual card state and log |
| Return a revised proposal to Review | The reviewer can identify the new version. | Repeated actions, comments and remaining quota |
If the first action succeeds but a later one fails, inspect the card before repeating the event. Record what needs repairing and reconcile the result with the intended handover. A log entry alone is insufficient if it sent work to the wrong colleague.
Check timing and who can maintain the rule
For a later reminder or scheduled tidy-up, check the automation timezone. Trello initially detects it from your computer. Updating it reschedules Calendar automations. Travelling does not necessarily mean your team’s reminders should move to your temporary local time.
Atlassian’s administrator guidance gives Premium Workspace and Enterprise admins the ability to view and disable other users’ enabled automations. Shared buttons have administrative controls; private buttons cannot be changed by admins. Do not assume every colleague has equivalent recovery access.
Name an owner and a backup, and document the intended trigger, actions and affected lists. Ask the backup to locate the rule and explain how they would investigate an unexpected result. Review this note whenever the team changes its board stages or reviewer responsibilities.
Sources reviewed 29 September 2026 against official Atlassian documentation. The consultancy workflow, calculation and acceptance checks are illustrative recommendations.
