# Trello Automation: How to Automate Your Boards (2026) By Desmond Attah-Cole · 2026-10-16 · Source: https://www.activepieces.com/blog/trello-automation-how-to-automate-your-boards-2026 --- **It stops at the edge of Trello**. Trello automation is Butler, the built-in no-code feature that acts on cards, lists and boards without leaving Trello, and it handles in-board chores well: moving cards, setting dates, assigning people, tidying lists. ## Trello automation is Butler: rules, buttons and schedules Anything that has to reach into other apps, the sort of job people often hand to a separate tool such as [Activepieces](https://www.activepieces.com), sits outside that boundary. Once something happens on a board, Butler checks whether it applies, then does a Trello action. Nothing leaves the board, so the failure you debug is usually a rule firing on the wrong card, not a broken connection. Pick by who starts the action: - Rules fire on their own when something changes on the board. - Card buttons and board buttons wait for a person to click, so they suit steps that need a human decision. - Date commands run on a schedule or against due dates. Every Butler rule has the same three parts. The trigger is the event, the condition filters it, and the action is what Trello does. Here a card moved to Done triggers the rule, the condition asks whether it carries the Urgent label, and the action sets a due date and archives the card. Only Urgent cards get touched, so the rest of Done stays visible for review. ![Done list with one red-labeled card moving to an archive box](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/c24bdeaa-c6cb-4281-9427-a6f488f862d2/trello-automation-how-to-automate-your-boards-20-ada72c93.webp) That's the whole model, and the other Butler features are variations on it. Look at Butler's documented triggers and actions and you find only [Trello](https://trello.com/en/pricing)'s own objects: cards, lists, checklists, labels, members and dates. Nothing in them calls another app, runs an AI step or holds a card until someone approves. On a busy board you can hit the ceiling mid-month, because run limits also depend on your plan. When a flow has to cross into another tool, [Activepieces](https://www.activepieces.com) **connects to 741 integrations** counted from its open source monorepo, so the app on the other side of your card is usually already covered. Until then, Butler is the cheaper thing to debug. ## Trello automation limits and plan costs as published On Free, Butler costs nothing extra and allows **250 runs a month**, and buying more runs means upgrading seats. Figures below were checked against Trello's published pricing on 16 October 2026. ![What a Trello seat costs on each plan](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/e4a6034a-b8bb-471a-860a-9e1be62adfdc/trello-automation-how-to-automate-your-boards-20-7899d041.svg "Source: Trello") ### Trello automation quotas on Free and paid plans At [$0 per user a month], the Free plan lets a solo board or a small team test every rule without a purchase order, which means you can validate automation needs cost-free. According to Trello, Standard is $5 per user a month and lifts the quota to 1,000 runs, meaning you can automate four times as many tasks monthly. Premium is $10 per user a month and Enterprise is $17.5, and both have unlimited runs, per Trello. The chart shows the quota by plan: **the jump from Free to Standard is fourfold**, and Premium's bar is open-ended because no cap is published. ![Activepieces pricing page displaying four subscription tiers with features and costs.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/841ec84e-02e4-4761-aca2-e92f6d457f41/self-host-mistral-ai-enterprise-deployment-guide-c7d7dca9.webp) 250 runs is about eight a day, so boards with light automation fit, but heavier use will run into the cap. A rule that fires on every card moved to Done, on a board where ten cards close daily, would use the whole month's quota in 25 days, leaving the last few days without automation. Before you build anything noisy, count how many cards touch the trigger in a week and multiply. If that number is already near 250, budget for Standard's $5 seat rather than assuming Free will hold. Upgrading costs more as the team grows: a five-person team pays $25 a month on Standard, which is still small next to the cost of debugging a broken cross-app flow. ### What counts as a Trello automation run Per Trello's automation documentation, a run is one execution of a rule, card button, board button or due-date command. As I read it, the count is per execution, not per action inside it, so a rule that moves a card, assigns a member and adds a label should cost one run, not three. Check this against your own usage numbers before relying on it. Don't take my arithmetic on trust. Build the rule, trigger it five times on a test card, then open Butler's usage view and see how many runs were recorded. If five triggers show five runs, your forecast is sound. If the count is higher, something is firing twice, and that duplicate trigger is the thing to fix first. ## Case for Trello automation only ### Four arguments for Butler alone, and where each stops With duplicates fixed, Butler alone covers work that stays on one board; **it falls short when work leaves Trello**, waits on a sign-off, or needs an AI step. Believers make four arguments, and each holds only up to a specific point. "Included in the plan" is true for every rule that moves cards on your boards, but it stops the moment a rule has to reach an app Trello doesn't control. "No extra login" is true until a task touches another tool, and then you are handling someone else's credentials anyway. "Lives on the board" is true while one person owns the rules, but logic spread across many boards is hard to audit from any single one. "Data stays in one place" is true until the answer lives in a CRM or spreadsheet, where someone copies it across by hand. ### Trello automation terms and limits defined To see exactly where each limit falls, read the four paragraphs below, which define the terms. You describe something that happens on a board, and Butler, Trello's built-in automation, does the follow-up work on cards, lists and checklists without you touching them. When something happens, such as a card landing in a list, a rule fires. Card buttons and board buttons wait for a person to click. Date commands run on a schedule or against due dates. Each starts differently, but all of them act inside Trello. Take a card moved into "Ready for review." The trigger is that move. The condition is that the card has a due date. The action adds a checklist and assigns the reviewer. ![Trello card gaining a checklist and reviewer after moving lists](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/114c74ff-6e3f-426f-9fca-bfa38e3a5d82/trello-automation-how-to-automate-your-boards-20-b56e65bd.webp) Test it with a card that has no due date, because that missing field is what breaks flows people call set and forget. Nothing in Butler waits for a manager's approval outside the board, and nothing reads a card's text and drafts a reply, because its actions are Trello actions. A schedule that spans Trello and another tool needs something that can see both. ## Five Trello workflows that connect other apps Build five flows first. Butler can run only two of them alone, and only partly. Each one either starts in another app or ends in one, which is the point where a rule that sees only Trello stops being enough. Read the last column of the table first: it tells you which ones you can skip the outside tool for. The table shows each flow's trigger, its steps, the app it touches and whether Butler covers it. | Flow | Trello trigger | Steps | Connected app | Butler alone? | |---|---|---|---|---| | Slack alert | Card added to a list | Format title and link, post to channel | Slack | Partly | | Gmail email | Starred email arrives | Read subject and body, create card | Gmail | No | | Google Sheets row | New row added | Map columns to card fields, create card | Google Sheets | No | | AI triage | Card created | Send text to model, write label and priority back | AI model | No | | Approval before move | Card dragged to Done | Hold card, ask approver, move or return | Slack or email | Partly | ### Five Trello workflows with triggers and steps Each flow below runs trigger first, then steps. For the Slack alert, the trigger is a card landing in a named list. The steps: build a message from the card title and link, then post it to one channel. ![Trello card sending a message bubble to a Slack channel](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/c9941208-9f08-48c3-9579-cdac53481ed3/trello-automation-how-to-automate-your-boards-20-b32162de.webp) The connected app is Slack. Butler can fire on the card, but whether the message reaches a channel depends on Trello's own Slack connection, so test it before trusting it. For the Gmail flow, the trigger is a starred email in Gmail. The steps: read the subject and body, create a card in your inbox list, and paste the sender into the description. Butler can't see your mailbox, so this one needs an outside tool. Test it with a badly formatted email before calling it done. For the Sheets flow, the trigger is a new row in Google Sheets. The steps: map each column to a card field, create the card, and write the card link back to the row. ![A workflow automation builder showing a Lead Nurturing flow with six connected steps and trigger settings panel on the right.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/fa4624a2-4195-47b7-b35b-4370f9ccce6d/marketing-to-sales-handoff-2026-automation-guide-d020bc71.webp) Blank or oddly typed cells are where this breaks, so decide what happens to an empty cell first. For AI triage, the trigger is a new card. The steps: send the title and description to a language model, ask for one label and one priority from a fixed list, and write both back to the card. Butler has no step that reads text and judges it. Restrict the model to your list of labels, or it will invent its own. For the approval flow, the trigger is a card dragged into Done. The steps: return it to its list, message the approver, wait for a yes, then move it. A Butler button can move a card, but it can't hold the move until a named person signs off. The approval step is the reason to use an outside tool here. ## Building cross-app Trello workflows with Activepieces ### When workflows need approval steps Inside a single board, Butler stays right, while Activepieces supplies the approval step, plus Trello triggers and actions and connectors to the apps Butler can't reach. If the rule is "when a card enters Done, archive it," keep it in Butler. If a flow touches another app, the question is whether a connector for that app exists. Butler's actions only grow when Trello decides to add them, so a missing connector means waiting on someone else's roadmap. Activepieces counts 741 integrations in its open source monorepo, roughly 60% of them contributed by the community, and if the app your flow needs isn't among them, AI can generate the integration and you keep it private to your own instance. ### Setting up notification workflows step by step For the Slack alert, the trigger is a new card in the [Trello](https://www.activepieces.com/pieces/trello) integration. The step is a message to a channel in [Slack](https://www.activepieces.com/pieces/slack), with the card name and link in the text. The run view for a similar flow, a Stripe payment-failed trigger feeding a Slack channel message, shows what to check: the trigger fires, the Slack step completes, and the run reports success. ![A workflow automation canvas showing a Stripe payment failed trigger connected to a Slack message action, with…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/832a3d13-71ba-413a-9599-dc58eb902861/webhook-signature-verification-how-to-secure-int-dbd07535.webp) When a flow fails on a messy field, that step-by-step view is where you find out which step broke. Next come flows that bring work into Trello. For the Gmail flow, the trigger is a new starred email in [Gmail](https://www.activepieces.com/pieces/gmail). The step creates a Trello card in your inbox list, with the subject as the title and the sender in the description. Starring becomes your triage gesture, so nothing needs copying by hand. For the Sheets flow, the trigger is a new row in [Google Sheets](https://www.activepieces.com/pieces/google-sheets). The step creates a card from the row, mapping columns to title, description and list. Test this one with a deliberately blank cell before trusting it. An empty field is where "set and forget" usually breaks. For AI triage, the trigger is a new Trello card. The first step sends the card text to an AI step that returns a category or priority. The second step updates the card, adding a label or moving it to the matching list. Butler has no step that reads and judges free text, so this is the clearest case for an outside tool. ![Import dialog for an Invoice Collection System workflow template with steps preview and description.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/e3d9ecaa-246e-439e-a5b4-ede742dfebe0/best-ai-tools-for-insurance-agents-2026-privacy-baa3ed5d.webp) Keep the output to a fixed set of labels so a vague answer can't invent a new one. For the approval flow, the trigger is a card landing in a Review list. The flow pauses and asks a named person to approve, for example by message in Slack. Only an approval moves the card to Done. A rejection posts a comment on the card instead, so the reason stays with the work. ## Trello automation mistakes and the Monday plan Without a sound board, approvals don't hold, and **most Trello automation breaks for five avoidable reasons**: a messy board, rules that trigger each other, noisy triggers, no owner, and a log nobody reads. ### Mistakes that waste runs or break boards Automating a messy board is the first mistake: a rule that moves finished cards to "Done" is only as reliable as your lists and labels, and a stale label means the rule fires on cards nobody meant it to touch. Letting rules trigger each other is the second. One rule moves a card, which fires a second rule that moves it back, and the loop keeps going until you notice. Before you save a rule, ask what other rule its action could set off. Choosing noisy triggers is the third. "Whenever a card changes" fires on every edit, so you burn through your plan's run allowance on events nobody cares about. Pick the narrowest trigger that does the job, such as a card entering one specific list. Leaving rules with no owner comes next. When a rule misbehaves six months later, nobody knows who built it or why, so people disable it instead of fixing it. Put the owner's name in the rule's title. Never reading the log is the last. Butler records what ran and what failed. If you skip it, a broken rule looks like a team that ignores the process. Run the fixes in the order below, because each step makes the next one safer to build. 1. Audit one board. Pick the board people complain about, then delete dead lists, archive cards nobody has touched, and remove labels that no longer mean anything. A rule built on this board will now act on what you can actually see. 2. Build one Butler rule and check it in the log. Keep it small, such as moving a card to "Done" when its checklist is complete. Trigger it once on a test card, then open the log and confirm it ran once, on the right card, with the result you expected. 3. Build one cross-app workflow and name an owner. Choose a task Butler can't finish alone, such as posting a card's status to another app or routing a card through an approval. Write the owner's name into the workflow before you turn it on, and read its first few runs yourself. If step three feels heavy, that's a useful signal. You've found the point where Butler stops and an outside tool starts, and now you know which task is worth sending there. ## Frequently asked questions ### Is Trello automation free? Yes, Butler is free on Trello's free plan, but with a monthly cap on runs. Paid plans raise that cap, so the real cost question is how many times your rules fire, not whether you can switch them on. A rule that triggers on every card move across a busy board burns through runs faster than one scoped to a single list. Check your own board's usage before you decide you need to upgrade. To find it, open the Automation menu on the board and look at the run count there. ### Can Trello send messages to Slack without another tool? Only in limited ways. Trello's Slack Power-Up can link cards to a channel and post basic updates. But Butler isn't built to compose a message from several fields, send it to a channel chosen by a card's label, or wait for someone to reply. If your need is "tell the channel when a card lands in Done," the Power-Up is enough. If the message depends on a custom field, or someone must approve before it goes out, you've reached the boundary where an outside tool earns its place. Test the notification with a card that has a blank field, because that's where thin integrations show their gaps. ### Do automations stop when I hit my run limit? Yes. Once a workspace uses up its monthly runs, Butler stops running rules until the allowance resets or you move to a plan with more. The danger is that nothing visibly breaks. Cards just stop moving, due dates stop being set, and checklists stop appearing, and someone notices a week later. Look at the run count before any busy period, and keep your most important rule narrow so it doesn't compete with noisy ones for the same allowance. ### Can Trello automation use AI? Sending card text to a language model and using the reply isn't something Butler's rules and buttons can do. They move, assign, date, label and comment according to the conditions you set. Summarizing a card, drafting a response, or classifying a request by its wording needs a tool that can call a model and pass the result back. Build the rule that way only if the output feeds a real decision. If a person has to review the AI's answer before it changes anything, make that approval an explicit step rather than hoping someone catches mistakes after the fact. ## Related reading - [AI Workflow Automation Examples: 11 Ideas You Can Try Today](https://www.activepieces.com/blog/ai-workflow-automation-examples) - [Simplify Your Workday: 9 Best Workflow Automation Apps](https://www.activepieces.com/blog/workflow-automation-apps) - [Connecting Legacy Mainframe Systems via API Integration](https://www.activepieces.com/blog/connecting-legacy-mainframe-systems-via-api-integration) ## References - [Trello](https://trello.com/en/pricing)