What This Integration Does
This integration posts Trello card activity into Slack with per-board channel routing, per-list message formatting, and smart filtering so the team gets the signal that matters from each board. Card creation, list moves, due-date alerts, checklist completions, and member assignments all post into Slack with formatting that matches how the team works.
For teams who run kanban boards in Trello and coordinate in Slack, this is the connection that closes the gap.
The Workflow
When a card is created or moved between lists, the integration receives the webhook, finds the configured channel for the board, and posts a message describing the change. A card moving from “In Progress” to “Review” posts to the channel tagging the reviewer assigned to the card. A card moving to “Done” posts a confirmation with the elapsed time from creation to done. Due-date approaching alerts fire when a card with a due date is two working days away from due and hasn’t moved into the “In Progress” or “Done” lists.
A specific chain: a content marketing team uses a Trello board with “Idea,” “Brief,” “Drafting,” “Editing,” “Scheduled,” “Published” lists. A card moves from “Drafting” to “Editing.” The integration posts to the #content channel tagging the editor with the working title, the writer’s name, and a link to the card. Two days later, if the card has not moved to “Scheduled,” a follow-up alert posts. When the card finally moves to “Published,” the integration posts a closing message in the channel with the published URL pulled from a custom field on the card and tags the writer and editor with a “Shipped” note.
Checklist completions also surface. A board configured with launch checklist cards posts a progress update in the channel each time a checklist item is ticked, with the percentage complete and the next item due.
Before and After
Before, Trello’s built-in Slack power-up posts updates in a single firehose that nobody reads. Important moves get lost. Due-date misses go unannounced. The team checks Trello manually and the signal in Slack is ignored.
After, each board has its own channel. Card moves are formatted for context. Due-date alerts fire before things slip. The team trusts the Slack signal and keeps using Trello as the kanban source of truth.
Who Needs This
Small teams and agencies using Trello as the operational system — particularly content teams, marketing teams, and product teams who like Trello’s simplicity and run their work as kanban. The integration is worth building once boards have grown beyond a few cards a week and the firehose of native notifications becomes noise.
How We Build This
We build this against the Trello REST API and the Slack Web API. Trello webhooks fire on card, list, board, and checklist changes; the integration filters and routes each event according to per-board configuration. See Slack API Integration for the Slack capabilities involved.
Get Trello and Slack Connected
If your team works in Trello and coordinates in Slack and the default integration is producing noise instead of signal, we can build a custom routing layer that delivers the right card update to the right channel.