# Trello Slack Integration: Setup and Limits (2026)

By Zara Al-Hassan · 2026-10-14 · Source: https://www.activepieces.com/blog/trello-slack-integration-setup-and-limits-2026

---
<aside class="tldr"><p class="tldr-label">Summary</p><p>Native Trello Slack integration cannot route cards by label, list or custom field, forcing teams to choose between accepting all-or-nothing notifications or building a separate workflow.</p><ul><li>Native Power-Up lacks routing by label, field mapping, and syncing Slack replies to card.</li><li>Free plan limits automation to 250 runs monthly, Standard plan to 1,000 runs monthly.</li><li>Slack Free plan caps apps at 10, limiting room for Trello alongside other integrations.</li></ul></aside>

The Trello Slack integration is the official connection that shares cards into Slack and sends basic notifications. It stops at custom routing, field-level mapping and two-way updates, and that's where a workflow tool takes over. Vendor facts here were checked on 2026-10-14.

## Trello Slack integration fundamentals

### What the Trello Slack integration can do

You'll know which side of that line your job sits on, and you'll have it running. If it's card sharing or a simple alert, that's the native setup, done in an afternoon.

If it's something like sending a card to a different channel depending on its label, you'll have a workflow that does it.

If a connector for one of your other tools is missing, [Activepieces](https://www.activepieces.com) lets you generate it with AI and add it privately to your own instance, without waiting on a vendor release, and roughly 60% of its 740 integrations were already built by the community, so you'll likely find a working connector for whatever tools you need.

The same applies if it means writing a [Slack](https://slack.com/blog/news/slack-has-10-million-daily-active-users) reply back onto the card.

### What the native integration does and does not do

Stop here if all you need is a card in front of people, because every extra tool is one more thing to maintain.

The two sets below show where its reach ends:

What it does:

- Shares a card into a Slack channel or conversation
- Posts alerts when cards change on a board
- Sends reminders for due dates

What it doesn't do:

- Route cards to different channels by rule, such as label or list
- Map individual card fields into a specific Slack message layout
- Push changes made in Slack back onto the card

If your job needs anything from the second set, the native setup won't stretch to cover it.

### Trello and Slack permissions required before setup

Sort this out first, because a missing permission is the most common reason a first attempt stalls.

On the [Trello](https://www.trello.com/pricing) side, you need to be able to add a Power-Up to the board, which usually means being a board admin or having a workspace admin do it.

On the Slack side, adding an app to a workspace can be restricted to admins or require approval, depending on how your workspace is set up.

If you're not an admin on both sides, ask for two things up front: Power-Up access on the board, and approval to install the app in Slack.

## Step-by-step setup of the Trello app in Slack

Once your admin has approved the install, setup is five stages.

Do this on the board whose activity you want in Slack, not on your workspace home page.

1. Open the board and select Power-Ups from the board menu.
2. Choose Add Power-Ups and search for Slack.
3. Click Add next to the Slack Power-Up.

You should now see a Slack icon among the board's Power-Up buttons. If you don't, you're probably on a board where you lack permission to add Power-Ups, so ask the board admin before going further.

### Stage 2: Authorise Trello inside Slack

Click the Slack Power-Up button on the board and choose Authorize Slack. Slack opens a permissions screen asking which workspace to connect. Pick the right workspace in the dropdown, check what access it requests, and click Allow.

If your workspace restricts app installs, this is where it stalls. When it works, you're returned to the board with the Slack button showing a connected state.

### Stage 3: Send board activity to a channel

Back in the Slack Power-Up settings on the board, pick the channel that should receive updates. Start with a quiet test channel, not the one your whole team reads. Then confirm it works:

1. Create a new card on the board.
2. Switch to the Slack channel you picked.
3. Check that the card appears as a notification.

If the card shows up, the integration works and you can repoint it to the real channel. If nothing arrives, the usual cause is a private channel the Trello app hasn't been invited to. Add it with `/invite @Trello` and create another card.

![Trello card outside a locked private Slack channel](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/3a9a6a7e-f57b-4602-b42e-b60b4e436ab7/trello-slack-integration-setup-and-limits-2026-i-b6412b4a.webp)

### Stage 4: Turn a Slack message into a card

From any message, open the More actions (three dots) menu and choose the Trello option to create a card. Pick the board and list, then confirm.

The message text becomes the card's content, with a link back to the original. This is the fastest win for most teams: a customer complaint in a support channel becomes a tracked card in seconds.

### Stage 5: Attach a Slack thread to an existing card

Use the same **More actions** menu on a message, but choose the option to attach it to an existing card, then search for the card by name.

The thread link lands in the card's attachments, so whoever opens the card later can see the discussion behind it.

What the native integration can't do is where the limits start.

## Trello Slack settings and limits

Before you need a workflow tool, you'll run into limits in three places: which board events can notify a channel, what your plans allow, and what Slack lets an app do per minute.

### Notification types and which events trigger them

When something happens on a board you've linked to a channel, the Trello Power-Up for Slack posts it: cards created or moved, comments, due dates, attachments. You pick the events per board-and-channel pair.

![Audit Logs](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/386757c3-834a-4fa2-b29d-81caff3e41c7/automate-ticket-handoffs-a-2026-guide-for-saas-t-26e23664.webp)

If sales cards and support cards share a board, everything lands in the same channel, and you can't route one list to a different place.

The catch is that the setting is per pair, not per list or label. That's the first sign you need a workflow tool.

### Power-Up limits by Trello plan

250 runs a month on Free and 1,000 on Standard: according to Trello, that is the ceiling on its built-in automation, and plan limits show up as ceilings on volume, which means you need to choose your tier based on your expected automation volume.

At 250 runs, one busy board with a few rules can burn the month's quota in days, and after that the rules stop firing without anyone noticing, leaving you without automation for the rest of your billing cycle.

![Full shelf of ten Slack app tiles with one waiting](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/a3c98074-876f-401a-afb0-bdc60cdbe23b/trello-slack-integration-setup-and-limits-2026-i-2686273e.webp)

10 apps is the cap on Slack's Free plan. Once you add Trello, a calendar, a help desk and a few others, you're deciding which app to remove before you can add the next one.

### Slack app permissions and private channels

Whether you can connect a channel at all depends on how your Slack workspace handles installs. Many workspaces require an admin to approve new apps, so the person who wants the integration often can't finish the setup alone.

![Person at gate, guard booth with empty chair](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/acf8dfd6-3b29-486a-b94f-d09bdfeca57b/trello-slack-integration-setup-and-limits-2026-i-9cd196c4.webp)

Skip one step on a private channel and notifications fail with no obvious error: the app has to be invited into the channel before it can post there.

Anything custom you build inherits Slack's API rate limits, which are grouped into tiers per method. The [Slack rate-limit documentation](https://docs.slack.dev/apis/web-api/rate-limits) sets them at:

- Tier 1: 1 request per minute
- Tier 2: 20 requests per minute
- Tier 3: 50 requests per minute
- Tier 4: 100 requests per minute

A method in Tier 1 handles a trickle, so a burst of 30 card moves can't all post at once. A Tier 4 method has about a hundred times that room.

Look up the tier of the exact method your flow calls before you promise anyone real-time updates.

![Slack API rate limits by method tier](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/f0342f0a-edd6-4b1a-9187-d014eb1ce490/trello-slack-integration-setup-and-limits-2026-s-9b2827b2.svg "Source: Slack")

## Trello Slack errors and fixes

Check the tier first, then the table below: almost every failure left is a permission, a stale connection or a routing mistake, and each has a quick fix.

| Symptom | Cause | Fix | Docs cover it? |
|---|---|---|---|
| No notifications | Board not linked to the channel, or the connection lapsed | Relink the board and send a test card | Partly |
| Private channel missing | The app was never invited to the channel | Invite the app from inside the channel, then reselect | Thin |
| Not authorised | Admin restrictions on app installs | Have a workspace admin approve the app | Partly |
| Departed user's connection | Link was made under an account that no longer exists | Reconnect under a current owner and relink | No |
| Wrong board | Connected to a similarly named board or workspace | Check board and workspace before saving | No |
| Duplicates | Two links, or native plus workflow tool, firing for one event | Keep one source per event | No |

The last three rows are where the docs say least, which means you're on your own if they fail. The details below cover the ones that need judgment.

When nothing arrives, the link between board and channel is usually gone, and Trello is not broken. Relink the board, move one card, and watch the channel. If nothing arrives, the connection itself has lapsed and needs re-authorising.

### Trello Slack private channels and admin approval

Until the app is a member, a private channel won't appear in the picker, so invite it from inside that channel first.

If you see "not authorised", the workspace is probably limiting who can install apps. You can't fix that from your side. Ask an admin to approve the app, and tell them exactly which one so the request doesn't sit.

![A modal dialog for installing a custom piece in Activepieces, with fields for package type, piece name, and version.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/a568b71d-b5b8-4e98-bcd9-834b9227ff0a/self-host-deepseek-r1-for-private-automation-202-7d9a246c.webp)

Someone built the link, left, and their account was removed, so alerts stop with no error anywhere.

The docs don't warn about it. Rebuild the connection under a current owner, and make it a habit to create shared connections from a role account where your policies allow it.

### Wrong board or duplicate cards

Confirm both board and workspace before you save, because wrong-board problems come from near-identical names across workspaces.

Duplicates almost always mean two things are listening to the same event: a second link, or the native integration running alongside a workflow tool. Pick one source per event and remove the other.

![Activepieces workflow builder showing a three-step automation connecting Calendly, Slack, and Gmail with an Event Canceled…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/57df6f6d-d916-41a0-af35-29f19ea1c3e6/trello-slack-integration-setup-and-limits-2026-s-2150fb50.webp)

If you've worked through all six and the behaviour you need still isn't there, you've hit a real limit.

## Automate what the native integration cannot with Activepieces

Choose Activepieces only once your limit is custom routing, field-level mapping or updates that flow both ways, the jobs the native Trello Slack integration can't handle.

Its 740 integrations include both a Trello integration and a Slack integration, so each of those jobs is a flow you build rather than code you write.

Beyond sharing cards and posting notifications, the native integration can't do three things:

- Sending a card to different Slack channels depending on its label, list or member
- Choosing which card fields appear in the message, rather than accepting the default
- Writing a Slack reaction or reply back onto the card

If your problem isn't on that list, stay native.

### Compare integration options by pricing model

Read the table for what each option lets you trigger on, how much control you get over fields, and what you pay to start. Take from it that the real difference is pricing model, because the three tools handle this pair's basics in similar ways.

| | Trigger options | Field mapping | Pricing model and entry plan |
|---|---|---|---|
| Native Power-Up | Fixed notification events | None; card details post as-is | Part of Trello, no separate plan |
| Zapier | Trello triggers including new card | Per-field mapping between steps | Per task; $19.99/mo for 750 tasks |
| n8n | Trello triggers including new card | Per-field mapping between nodes | Per execution; Cloud €20/mo for 2,500 executions |
| Activepieces | Trello triggers including new card | Per-field mapping between steps | Open source and self-hostable; free to start on cloud |

A third app is where [Activepieces](https://www.activepieces.com/pieces)' library matters. It grew from [200 pieces in June 2024](https://www.activepieces.com/pieces) to 280 by March 2025, 320 by July 2025 and 500 by November 2025.

**By 2026 the library stands at 768**. The odd tool you add after Trello and Slack is therefore more likely to have a ready-made connector. It's less likely to force you into custom HTTP calls.

With the comparison settled, the build takes three steps:

1. In the [Trello piece](https://www.activepieces.com/pieces/trello), choose the New Card trigger and select your board.
2. Add a branch that checks the card's label or list. Cards that match go on; the rest stop here, which is your custom routing.
3. In the [Slack piece](https://www.activepieces.com/pieces/slack), choose the Send Message action, pick the channel for that branch, and map the card name, due date and URL into the text.

You can [start the flow free on Activepieces cloud](https://cloud.activepieces.com/sign-up): the free plan is $0 with no card needed, and it includes 1,000 credits a month, unlimited flows and up to 5 users, letting you try it without any financial commitment.

Test with one real card before turning it on. Then add a second branch for the next label, so each channel gets only the cards it needs.

## Frequently asked questions

Once the label routing is live, the same few questions tend to come up, and none of them needs another branch.

### Is the Trello Slack integration free?

Yes, adding the Slack Power-Up to a board costs nothing on its own.

The catches are the plan limits around it: your Trello plan may cap how many Power-Ups a board can run, and your Slack plan may cap how many apps the workspace can install.

If you're on free plans for both, check those two limits before you promise anyone a rollout date.

### Can Slack messages sync back to Trello comments?

Not automatically. The native integration lets you turn a Slack message into a card or attach a message to one, but a reply in a thread doesn't become a comment on its own.

You need a workflow to sync replies. It has a trigger in Slack, such as a reaction or a post in a specific channel, and a step that adds a comment to the card.

Build in a guard so comments the workflow posts to Slack don't trigger it again. Otherwise the two tools will echo each other until someone notices the noise.

### Does the integration work with Slack Connect channels?

I haven't confirmed this for every setup, so test before you rely on it. A Slack Connect channel is shared between two organizations, and the app only exists in yours.

Admin approvals on both sides can affect what works, and so can what people from the other company are allowed to see.

Create a throwaway card on a test board, link it to the shared channel, and check what the other side sees. If you're routing client-facing updates, that ten-minute test beats finding out after a customer sees an internal card title.

### How do I remove the Trello Slack integration?

Remove it in two places, because each side keeps its own connection. In Trello, open the board's Power-Ups menu and disable the Slack Power-Up on every board that uses it. In Slack, remove the Trello app from your workspace's app management page.

Once either side is disconnected, notifications stop, and cards you already created stay where they are. Do the Slack side too, though, or you leave an authorized app sitting there that nobody is watching.

## Related reading

- [Ultimate Guide: Automate Trello Card Creation with Google Contacts Updates](https://www.activepieces.com/blog/create-trello-card-creation-for-updated-google-contacts)
- [HeyGen Alternatives vs Custom AI Video Workflows in 2026](https://www.activepieces.com/blog/heygen-alternatives-vs-custom-ai-video-workflows-in-2026)
- [Odoo Studio vs Custom Development for AI Workflows (2026)](https://www.activepieces.com/blog/odoo-studio-vs-custom-development-for-ai-workflows-2026)

## References

- [Activepieces](https://www.activepieces.com/pieces)
- [Slack](https://docs.slack.dev/apis/web-api/rate-limits)
