Trello Power-Ups Worth Adding (and When to Stop)

Trello Power-Ups are add-ons that give a board features it does not have out of the box, or connect it to another service such as Slack, Google Drive, GitHub or Jira. You add them from the Power-Ups menu in the board header, every plan can add as many as it likes, and some are built by Trello while most come from partners. Automation, the feature once called Butler, is built in and is not a Power-Up. The useful question is not which Power-Ups exist but which ones your team will still open in a month. Start with one or two that remove a real chore, and stop when a new one would only add another button.

What a Power-Up is, and who makes them

Trello’s Power-Ups guide↗ (opens in a new tab) splits them in two: “Made by Trello Power-Ups are just that—integrations designed by the Trello team,” and all others come from third-party partners, companies or Trello users. Anyone can build one with Trello’s public API. That matters for two reasons. A partner Power-Up is maintained on the partner’s schedule, not Trello’s, and some need a subscription of their own with the partner even when your Trello plan does not charge for it.

The Made by Trello set is small: Calendar, Card Aging, Card Repeater, Dashcards, Voting, Box, Evernote, GitHub, Google Drive, Mailchimp, Package Tracker and Salesforce. The Giphy Power-Up appears on the same help page as no longer available.

Power-Up categories in Trello’s directory

The Trello integrations directory↗ (opens in a new tab) sorts Power-Ups into eleven categories, plus an All integrations view. As of October 1, 2026, they are:

• Analytics & reporting, Automation, Board utilities and Communication & collaboration: the general-purpose tools most teams look at first.
• Developer tools and File management: links to code hosts, issue trackers and document storage.
• HR & operations, IT & project management, Marketing & social media, Product & design, and Sales & support: tools built for one kind of team.

The directory features Slack, Jira Cloud and Miro at the top. Featured is not the same as recommended for you; read the category your problem sits in, not the front page.

How to add a Power-Up to a board

Trello’s help page on enabling and managing a Power-Up↗ (opens in a new tab) gives the steps:

1. Open the board and select Power-Ups in the board header.
2. Select Add Power-Ups and search for the one you want.
3. Select Add, then follow its own setup, which may include signing in to the other service.
4. Choose whether its button shows in the board header with the slider next to it in the same menu.
5. To remove it later, open Power-Ups, select its Settings button and choose Disable. Tick “Keep all Power-Up data” first if you might switch it back on.

Power-Ups are added per board, not per Workspace. A team with ten boards that wants Google Drive on all of them adds it ten times (Slack is an exception that works per Workspace), and a board copied from a template can bring Power-Ups along that someone then has to configure.

Power-Up limits by plan

There is no count to manage. The same help page says “There’s no limit on the number of Power-Ups a board can have, regardless of your plan,” and Trello’s plan guide lists unlimited Power-Ups on Free, Standard, Premium and Enterprise alike. What changes by plan is control and the features around them:

• Free and Standard: unlimited Power-Ups on every board. The plan guide lists Power-Up restrictions only on Enterprise.
• Premium: the same, plus the views that make some Power-Ups unnecessary, such as Calendar, Timeline, Table, Dashboard and Map.
• Enterprise: Power-Up restrictions. Enterprise admins approve which Power-Ups people may use, often against the company’s security requirements.

Trello Automation, formerly Butler

Before you add a Power-Up to move cards or set dates, check whether Automation already does it. Butler began as a bot that read commands written on cards; Trello built it into the product, and its help pages now call it Automation. The old Butler Bot is no longer officially supported, and Trello asks anyone still using it to move to the built-in version.

Automation has five types: rules that fire when something happens, card buttons, board buttons, scheduled commands and due date commands. It is available in every Workspace. Trello’s automation quotas page↗ (opens in a new tab) sets the limits by plan: Free and Standard each get a monthly allowance of automation runs, larger on Standard; Premium and Enterprise get unlimited runs, with a cap on the operations those runs perform. The quota is pooled across every board in the Workspace and resets on the first of each month, so one busy rule on one board can use up a small team’s allowance for all of them.

Rule:        when a card is added to "Requests", add the label "Triage"
Rule:        when a card is moved to "Done", mark the due date complete and remove all members
Card button: "Blocked" -> add label "Blocked", post a comment asking who can help
Board button: "Weekly cleanup" -> archive all the cards in "Done"
Scheduled:   every Monday at 9:00 am, sort "Up next" by due date
Due date:    1 day before a card is due, move it to the top of its list

A starter set by team

Most boards need no more than two or three Power-Ups. These pairings use the Made by Trello set and the directory’s featured partners:

• Software team: GitHub or Jira Cloud on the card back, so a pull request or a linked work item shows beside the card. Slack if the team already lives there.
• Marketing team: Calendar on Free and Standard boards to see dates on a calendar, and Mailchimp if campaigns run there. Teams on Premium can use the built-in Calendar view instead.
• Product team: Voting for a request board, so people vote instead of filing duplicates, and Card Aging to show which requests nobody has touched.
• Operations or a household board: Card Repeater for chores that come back, though recurring due dates and scheduled automation may already be enough.
• Anyone filing documents: Google Drive or Box, so attachments open from the card with a live preview.

When to stop adding Power-Ups

A Power-Up often brings another sign-in, another set of permissions on another service and another thing a new teammate has to learn. Run this test before adding one, and again every quarter on what is already there:

1. Did anyone open it in the last 30 days?               no  -> disable it
2. Does Automation or a built-in view already do this?   yes -> use that instead
3. Does it need its own subscription or admin approval?  yes -> name an owner first
4. What data can it read on the other service?           unclear -> skip it
5. Would a new teammate know why it is here?             no  -> write it on the board's "How we use this board" card

Stop when the board header has more buttons than the board has lists, when nobody can say who set a Power-Up up, or when the answer to a question is “check the Power-Up” and nobody does. A board people trust is one they understand at a glance.

AI assistants: the integration that is not a Power-Up

Connecting an AI assistant to Trello does not go through the Power-Ups menu. Trello runs an official MCP server, signed in with OAuth, scoped to the Workspace you choose and limited to what you can already do in Trello. The setup guides cover each client: Trello MCP with Claude Code, Trello MCP with ChatGPT, Trello MCP in Cursor and VS Code, and Trello MCP or CLI for choosing a route.

fenbs takes the opposite view of add-ons: it has no Power-Ups and no automation rules. Its one door for software is MCP, at https://fenbs.ai/api/mcp, and an assistant connected there joins the board as a member under a role, so a job a Power-Up might do, such as triaging new bugs each morning, becomes a request to the assistant, recorded in History with its name. It also has no due dates, no calendar and no settable assignee, so it suits a team that wants fewer moving parts, not one that needs them. fenbs vs Trello compares the two.