Use Trello Automation's card-moved trigger as a QA state machine

Problem: A bug card lands in your team's Ready for QA list, but no label appears, no one is assigned, and the QA engineer only finds it during a random board scan. The list is supposed to mean 'ready for testing,' but that state lives only in the position of the card, not in any field the team can filter or report on.

Takeaway: For board-local transitions like this, Trello Automation can act as a small state machine. A list represents a state, and a rule that fires when a card enters that list can add a label or member to make the transition visible and auditable. Use custom code only when a rule must coordinate systems outside Trello.

A list is a state; a rule is the transition

In Trello, a board contains lists, and lists often represent workflow stages such as To Do, In Progress, and Ready for QA. Trello Automation is the board's native rule engine. A rule has a trigger—such as a card being moved into a specific list—and one or more actions, such as adding a label, adding a member, or posting a comment.

Terms: trigger is the event that starts the rule. Action is what the rule does. Board administrator is typically required to create or edit Automation rules on a board.

Worked example: QA handoff on a software board

Suppose your board has a Ready for QA list and a qa-ready label. You want every card moved into that list to receive the label so it shows up in label filters and card views.

1. Open the board and open Automation from the board menu.
2. Create a rule with the trigger 'card is moved into list Ready for QA.'
3. Add the action 'add the qa-ready label to the card.'
4. Save the rule and test it on a disposable card.

If your plan and interface support assigning a fixed member, you can add an action to assign the board's QA member. If that action is not available in your current Trello interface or plan, use a label or checklist item instead and verify before relying on it.

Expected result: after you drag a card into Ready for QA, the qa-ready label appears on the card. Moving the same card to another list such as Done should not add or remove the label unless you created a separate rule for that transition.

Diagnostic decision: rule or custom integration?

Situation	Recommended approach
Card enters a Trello list and needs a Trello label, member, or comment	Native Trello Automation rule
Card move must create an issue in another system, update a database, or wait for an external approval	Custom integration or bot using Trello's webhook or API
Transition requires complex conditions across multiple boards or accounts	Custom integration; native rules are board-scoped and intentionally simple

Where Automation stops

Native rules are easy to audit because they live on the board and run in the Trello interface, but they are intentionally simple. Rules can be hard to discover for new team members, and multiple overlapping rules can fire for the same card move, producing duplicate labels or comments. Automation is not a transactional workflow engine, an approval system, or durable event processing. It also does not replace access control: anyone with permission to move cards can trigger the rule, so board membership and permissions still matter.

Rollout checklist

• Create a scratch board with a Ready for QA list, a qa-ready label, and one test card.
• Add the card-moved rule and move the test card into the list.
• Check that the label appears exactly once.
• Move the card to another list and confirm no unintended action occurs.
• Assign an owner to the rule, document its trigger and action, and review it with the team.
• Rollback: if the rule causes unwanted changes, open Automation, disable or delete the rule, and remove any labels it added.

Verify the current Automation action list and plan limits in Trello's interface or account documentation before documenting exact labels or screenshots, because wording, available actions, and entitlements can change.

Start with one transition. Expand only after the team can explain every automated side effect on the board.