What we do
Tools
Industries
Department
How we workLet's talk →
Home/Trello/Trello Automation
Trello

Trello Automation: Rules, Buttons, Schedules and the Monthly Limit

A card lands in Done and you still drag it to the archive list, tag the owner and tick the checklist. Trello automation, still often called Butler, does that for you, on every plan. It runs inside the board, it can call other systems over HTTP, and it stops for the month when the Workspace's quota runs out.

Build your first Trello automation

  1. 1

    Open Automation on the board

    Board header Automation

    This opens the automation builder for the board. Trello also offers Suggestions based on things you do by hand over and over, which is a quick first rule.

  2. 2

    Pick the command type

    Choose Rules, Card button, Board button, Scheduled or Due date. The table below says which one fits which job.

  3. 3

    Set the trigger, then add actions

    For a rule, the trigger is something like "when a card is moved into list Done". Then add actions: move the card, add a label, join a member, post a comment, send an email. Each run can do up to 20 actions and operations in total.

  4. 4

    Save, then watch the log

    Save the command and move a test card. The automation log shows each run and any error, which is the first place to look when a rule seems to do nothing.

Which Trello automation type for which job

You want Use Good to know
Something to happen every time a card changes Rule: a trigger (card moved, label added, checklist done, card created) and actions. Runs on every match, so a busy board spends quota fast.
A one-click routine on a single card Card button on the back of the card. Up to 20 card buttons can be on at once.
A one-click routine across the whole board Board button in the board header, such as "archive everything in Done". Also capped at 20 at once.
A weekly or monthly routine Scheduled command: create the Monday stand-up card, or sort a list every Friday. Runs on the clock whether or not anything changed.
Something keyed to deadlines Due date command, such as "two days before due, add the red label and mention the owner". Only sees cards that have a due date set.

Why a Trello rule stops firing

Quotas are shared by every board in the Workspace and reset on the 1st of each month at midnight GMT.

The Workspace has used up its runs

How you'll know: Rules worked all month, then nothing from about the same day each month.

Fix: Free allows 250 automation runs a month and Standard 1,000. Premium and Enterprise have unlimited runs but cap operations at 150,000 plus 10,000 per user, up to 250,000 per Workspace. The usage log shows which rules spend the most, so you can narrow their triggers.

A rule that triggers itself

How you'll know: One card change sets off a long chain of runs in the log.

Fix: A rule whose action matches its own trigger, or two rules that answer each other, burns runs in a loop. Narrow the trigger with a list or label condition.

The email quota ran out first

How you'll know: Moves and labels still happen, but the notification emails stopped.

Fix: Emails have their own monthly allowance: 250 on Free, 1,000 on Standard. Each send-email action can reach up to 50 recipients.

The rule needs an answer from another system

How you'll know: You've added an HTTP request action, but the accounting system or CRM wants a sign-in the rule can't do.

Fix: Trello's HTTP action sends GET, POST or PUT with JSON headers and payload, and later actions can use the reply as {httpresponse}. Something still has to sit at that URL, sign in to the other system and answer. That's the piece n-frames builds and runs.

Trello automation calling out, or a service on Trello's API

Inside Trello automation

A rule with an HTTP request action

  • Fine when the other system takes a simple key in a header and answers in JSON.
  • Uses one run per trigger, plus operations for each action.
  • Only fires on things that happen in Trello. An invoice paid elsewhere can't start it.
Outside Trello

A small service on Trello's API and webhooks

  • Holds the sign-in for QuickBooks, Xero or your CRM and refreshes it.
  • Can start from an event in the other system and move the card, the opposite of a rule.
  • Doesn't draw on the Workspace's automation quota.

Most boards need both: rules for the moves inside Trello, and a service for the steps that depend on another system. The Trello API page covers the code side.

Questions people ask

What is Trello Butler?

Butler is the original name for Trello's built-in automation. It's now just called Automation, and it covers rules, card buttons, board buttons, scheduled commands and due date commands, built from the Automation menu on any board.

Is Trello Butler free?

Yes. Automation comes with every Trello plan, including Free. What changes by plan is how many runs and operations the Workspace gets each month.

How many Butler automations can I run per month?

Free gets 250 automation runs a month and Standard 1,000. Premium and Enterprise have unlimited runs, with operations capped at 150,000 plus 10,000 per user, up to 250,000 per Workspace. The quota is shared across every board in the Workspace.

Can Butler connect to tools outside Trello?

Partly. Actions can send email, post to Slack, act in Jira and send HTTP requests to any URL, then use the response in later steps. Triggers only watch what happens in Trello, and a system that needs a proper sign-in needs something in between, which n-frames builds.

Why isn't my Trello automation working?

Check the automation log first. The usual causes are a used-up monthly quota, a trigger that doesn't quite match (the wrong list name, for example), or an action that hit the 20-action limit for a single run.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.