Slack
The official Slack Power-Up sends a card to a channel or a direct message, sets Slack reminders from a card, and links a channel to a board. Cards can also be captured from Slack. It doesn't keep a Slack thread and a card's comments in step.
Someone pastes a Slack thread into a card, then pastes the card link back into Slack so people know it exists. Trello integrations are meant to end that. Power-Ups are now unlimited on every plan, Free included, so the question is no longer how many you can switch on. It's whether the Power-Up only shows the other tool's data on the card, or actually moves work between them.
If people need to see the other tool's data while they work the card, a Power-Up fits. If a record should be created or changed somewhere else when the card moves, that's a Zap, a Trello automation rule, or code.
The official Slack Power-Up sends a card to a channel or a direct message, sets Slack reminders from a card, and links a channel to a board. Cards can also be captured from Slack. It doesn't keep a Slack thread and a card's comments in step.
Attach branches, commits, issues and pull requests to the card they belong to, so code activity shows on the board without anyone opening the repo.
Attach Drive files and folders to cards, so the brief, the contract or the spreadsheet sits on the work it belongs to.
Shows current cases, contacts, leads and opportunities attached to a card. It works with Salesforce Enterprise, Unlimited, Developer and Performance, and Professional with API access switched on.
There's no Trello-made HubSpot Power-Up, but third-party ones in the directory link cards to contacts and deals. Read each listing for what it syncs and in which direction.
Trello has built-in ways to link cards and Jira work items. The Trello Jira integration page covers what that link does and where it stops.
How you'll know: The CRM record shows on the card, but moving the card to Won changes nothing in the CRM.
Fix: Many Power-Ups are windows onto the other tool. If a card move should create or update a record, you need a Zap, an automation rule with an HTTP request, or an integration on the Trello API.
How you'll know: The Zap or the Power-Up's account link stops working after someone's account is removed.
Fix: Reconnect it under a shared service account that belongs to the business, not to one employee.
How you'll know: The Power-Up installs, then asks for a subscription before it does anything useful.
Fix: Price the partner's plan before you design around it. Sometimes a direct build costs less than per-seat fees for a feature you use on one board.
How you'll know: Rules that call out to another tool stop firing before the month is over.
Fix: Free Workspaces get 250 command runs a month and Standard 1,000. The Trello automation page covers the quota; busy integrations belong on the API instead.
The directory covers the platforms Trello or its partners chose to build for. Your in-house tools, a niche industry system, or the ERP your ops team runs on usually aren't in it, and where a Power-Up does exist it often stops at showing data.
n-frames builds those connections on Trello's REST API and webhooks: a Slack flow where an action in Slack creates or updates the right card and a card change posts the one detail someone in Slack needs, a two-way CRM sync where moving a card updates the deal and the deal's changes land back on the card, and links to tools that have no Power-Up at all. If the data needs to leave Trello in bulk, Trello export covers that side, and Zapier has its own page for when a Zap is the right size.
It does, with the official Slack Power-Up. You can send a card to a Slack channel or direct message, set reminders in Slack from a card, and link a channel to a board, and cards can be created from Slack without switching apps.
Salesforce has a Power-Up that shows cases, contacts, leads and opportunities on a card, on the Salesforce editions with API access. HubSpot is covered by third-party Power-Ups and by Zapier. For a true two-way sync between cards and deals, that's custom integration work on both APIs.
A plugin you switch on for a board that adds something to it, usually tied to an outside service: a button, a badge showing live data, an attachment type, or an action that reaches into the other tool.
Yes. The GitHub Power-Up attaches branches, commits, issues and pull requests to the related cards, so a dev team sees code activity on the board.
Not anymore. Trello's pricing page lists unlimited Power-Ups per board on Free, Standard, Premium and Enterprise. What does vary by plan is automation runs, and some partner Power-Ups charge separately.