How to Automate Trello Butler Rules Without Hitting the Limit

Short answer: Trello’s Butler gives you 250 automation runs per month on Free, 1,000 on Standard and 10,000 on Premium. A well-built set of five rules stays under 150 runs a month on a 12-person team. A badly built set burns 800 in a week, because scheduled rules and “every time a card is added” triggers multiply across lists.

Here is how to build the first set, and how to spot the rules that are quietly eating your quota.

Why do Butler rules run out so fast?

Because Butler counts trigger execution, not card activity. A rule that says “when a card is moved into Done, set due date to today” fires once per card. A rule that says “every day at 9am, for each card in Doing, check the checklist” fires once per card, per day. Twelve cards in Doing means 360 runs a month from that one rule.

That distinction is the whole game. Trello does not warn you before you hit the ceiling. Automations just stop, silently, and cards start piling up in the wrong list. Teams usually find out three weeks later.

How do you check your Butler usage?

Open the workspace, go to Settings → Automations (or the Butler power-up in the board menu) and look at the usage meter. It shows runs used against your monthly allowance and resets on your billing date.

Do this before you add anything. If you are already at 70% of quota on day 5 of the cycle, you have a rule problem, not a plan problem.

Which five Butler rules are worth keeping?

These are the ones that survive contact with a real team.

Rule	Trigger	Action	Rough monthly runs
Stale card flag	Scheduled, weekly, cards in Doing older than 14 days	Add red label, comment “needs update”	20-60
Due-date guard	Card moved to This Week	Set due date to Friday	40-80
Done cleanup	Card moved into Done	Add “shipped” label, set due date to today	60-150
Checklist on intake	Card created in Backlog	Add 3-item checklist	30-90
Weekly rollup	Scheduled, Monday 9am	Create one card listing cards completed last week	4

The weekly rollup is the cheapest rule on the list because it fires once per week regardless of card count. The Done cleanup is the most expensive but also the most useful, since it gives you a date trail without anyone typing.

How do you cut runs without losing the behaviour?

Four moves, in order of payoff.

1. Convert per-card schedules into list-level checks. Instead of “for each card, check the checklist daily”, use “every Monday, add a checklist-complete label to nothing” — no, better: replace it with a single weekly card that asks the owner to review the list. One run instead of 300.
2. Narrow the trigger. “Card created in Backlog” is cheaper than “Card created in any list” when most cards arrive via templates.
3. Use card buttons instead of automatic rules for anything a human is standing next to. A button costs one run and only fires when pressed.
4. Delete the notification rules. Rules that comment on every move generate noise and runs. Nobody reads them.

On Premium, you also get the higher ceiling plus calendar and due-date commands that are otherwise paid. If you need more than 5,000 runs a month, the real fix is a different tool — Trello is not a workflow engine.

What breaks when automations stop?

Cards keep moving; the automation layer just does not follow. In practice you get three symptoms.

• Labels stop being applied, so filters look empty.
• Due dates drift, and the “overdue” view becomes fiction.
• The Done cleanup lags, so reporting shows work as open that shipped last week.

None of these raise an alert. Put a recurring human check on the automations page once a month — five minutes, on the first Monday — and you will catch it before the numbers matter.

Does Trello AI help with Butler rules?

Partly. The AI can draft the rule description in plain English, which is genuinely faster than reading Butler’s grammar reference. It will also suggest rules you did not ask for, and those suggestions are usually the expensive scheduled ones.

Use it to phrase a rule you already decided on. Do not use it to brainstorm automations. The same goes for rewriting card text with the AI button: good for clarity, irrelevant to quota.

Who should automate heavily, and who should not

Automate if the same three actions happen every week and nobody enjoys doing them. A 12-person team with a stable board gets real value from five rules.

Do not automate if your process is still changing monthly. Every redesign means retesting rules, and half-broken automations are worse than manual steps because people trust them. Also skip scheduled rules on Free if your team is over eight people — you will hit 250 runs by the third week.

Quick Summary

• Butler meters trigger runs: 250/month on Free, 1,000 on Standard ($5/user), 10,000 on Premium ($10/user).
• Daily per-card schedules are the quota killer — one 12-card list costs 360 runs a month.
• Five rules cover 80% of useful automation: stale flag, due-date guard, Done cleanup, intake checklist, weekly rollup.
• Automations fail silently. Check the usage meter on the first Monday of each month.
• Use card buttons for one-off actions; they cost one run and only fire when pressed.