How to connect Trello to Slack when nobody owns the card

Trello is deliberately loose. A card can have several members or none, a list means whatever the board decided it means, and nothing requires a due date or an owner. That looseness is why people like it and why boards stall in a particular way: a card sits in a list for three weeks and no single person feels responsible for it.

A Slack integration can help with that, and only if it works with the looseness rather than pretending the board has structure it does not. The signal in Trello is movement between lists, not assignment, and building around that is what makes the difference.

What we'll cover

• Members are not assignees
• Lists are the signal
• Building it with CodeWords
• Three messages a board actually needs
• Finding the cards nobody owns
• Creating cards from a conversation
• Conventions that make a board automatable
• Time in list, which is the honest metric
• Making it survive
• Limits worth knowing about
• What to set up first
• Frequently asked questions

Members are not assignees

Worth stating clearly, because it shapes every message you can send.

Several people can be on a card, or nobody, and Trello attaches no particular meaning to either.

Being a member often means "interested" rather than "doing it", and different boards use it differently.

There is no built-in notion of who is responsible, which means a message saying "this card needs attention" frequently has no obvious recipient.

Watching is separate from membership, and neither implies ownership.

The consequence: messages addressed to individuals are unreliable on a Trello board unless the team has agreed a convention. Most useful messages therefore go to the board's channel, and the interesting ones are about the board's state rather than about one person's queue.

Lists are the signal

What Trello does encode well is position, and movement between lists is the meaningful event.

A card moving forwards is progress, and moving backwards is usually a problem worth noticing.

A card entering a "blocked" or "waiting" list is the clearest signal a board produces, and it is the one worth sending immediately.

Time in list is the health metric. A card in review for two weeks is a fact that needs nobody's interpretation.

Entering the final list is a completion, and it is the event other teams care about.

Card creation is usually not interesting, since it happens constantly during planning and means nothing until the card moves.

Build the messages around list transitions, and the board becomes legible without requiring anybody to change how they work.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which board, which list transitions matter, and where the message goes.
3. Authorize the connection to Trello with an API key and token, and to your Slack workspace.
4. Describe the exceptions: a card archived, a list renamed, a card with no members.
5. Test against a copy of the board and a test channel before anything reaches the team.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Three messages a board actually needs

A card entered the blocked list. Immediately, to the board's channel, with what it is waiting on if the card says. This is the one where hours matter.

A daily or weekly board digest. What moved, what is stuck, what is overdue, and what has no owner. One message that makes the board's state readable without opening it.

A card reached done, to whichever other team was waiting — support, sales, or whoever raised it. Completion is the event people outside the board care about and nobody tells them.

That is it. Card creation, comments, label changes, checklist items, and description edits are board activity, and forwarding them produces a feed that obscures the three above.

Finding the cards nobody owns

The characteristic Trello problem, and the most valuable thing to report.

Cards with no members, listed weekly. On most boards this is a surprising number and each one is work nobody has picked up.

Cards with several members and no movement, which is the other version of the same thing — shared responsibility behaving like none.

Cards past their due date with no recent activity. Due dates in Trello are frequently aspirational, and the ones that passed silently are the honest measure of a board's health.

Cards in a list longer than that list's typical time, which identifies where work actually gets stuck rather than where somebody thinks it does.

Report it to the board's channel, once a week, phrased as a short list rather than a table. It becomes a two-minute conversation, which is exactly the right amount of ceremony for a Trello board.

Creating cards from a conversation

Genuinely useful, since Trello's low friction is the point of using it.

A message marked in an agreed way becomes a card in a defined list — an inbox or backlog, never directly into active work.

Carry the thread link on the card, so the context survives.

Put it in an intake list, so somebody triages rather than it appearing in the middle of the board.

Confirm in the thread with a link, so the person can see it exists.

Check for a similar card first, since the same request gets discussed repeatedly and chat-created cards are the main source of board duplication.

Conventions that make a board automatable

Small agreements, no technical work, and they determine whether any of the above is reliable.

Name lists consistently across boards if you have several, since automation matching on list names breaks when one board calls it "In Review" and another "Review".

Agree what membership means. If it means responsible, messages can be addressed to people; if it means interested, they cannot.

Use one list for blocked, rather than a label, a comment, and a card title prefix depending on who is doing it.

Set due dates on things with deadlines and leave them off things without, so the overdue report means something.

Archive rather than delete, which keeps history and avoids an automation finding a card gone.

Time in list, which is the honest metric

Most Trello reporting counts cards. Counting time tells you considerably more, and the data is already there.

Measure how long each card spends in each list, from the board's action history.

Report the distribution per list. The list where the median time is longest is where your process actually queues, which is rarely where people assume.

Watch the tail, not the median. Most cards move through review quickly; the ones that sit for three weeks are the problem and an average hides them completely.

Compare across boards if you run several, since a list taking twice as long on one board is a question worth asking.

Do not turn it into a target. A team measured on time in list will move cards to make the number look better, which is the easiest thing to game on a board with no enforcement.

Use it to start a conversation, monthly, about where work is waiting. That is the whole value — the number is evidence, not a verdict.

Making it survive

Make it idempotent, keyed on the card and the action, since webhook deliveries repeat.

Resolve list identifiers rather than matching names at run time where you can, because lists get renamed and identifiers do not.

Handle the archived card as a normal case rather than a failure.

Do not send on every card update. Filter to the transitions you decided on, or the volume returns immediately.

Report the outcome. Messages sent, transitions matched, and anything skipped.

Limits worth knowing about

Webhooks fire on a lot of actions, so filtering on your side is essential rather than optional.

Rate limits apply per key and per token.

List renaming breaks name matching, which is the most common cause of an automation silently stopping.

Power-Up data is not always reachable through the standard API, so custom fields added by a Power-Up may not be available.

Card descriptions and comments are freeform, so anything parsing them is a convention rather than a contract.

What to set up first

The weekly board digest: what moved, what is stuck, what is overdue, and what has no members, posted to the board's channel. It writes nothing, it takes little building, and the ownerless-card list is usually the first time a team sees how much work nobody has actually picked up.

Two habits make the difference. Lead with the count of cards with no owner, since that number starts the useful conversation. And keep it to a handful of lines, because a Trello team chose Trello to avoid reports and a long one will be ignored on principle.

Frequently asked questions

Why can I not send notifications to the person responsible?

Because Trello has no notion of responsibility. Members mean whatever your board decided, and several boards use it to mean "interested". Either agree a convention that membership means ownership, or send board-level messages instead.

What Trello events are worth sending?

A card entering the blocked list, a weekly digest, and completion notified to whoever was waiting. Card creation, comments, labels, and checklist changes are board activity and forwarding them buries the three that matter.

How do I find work nobody has picked up?

List cards with no members, cards with several members and no movement, and cards past their due date with no activity. On most boards this produces more than the team expects, and it is the single most useful report.

Can I create cards from Slack?

Yes, into an intake list rather than into active work, with a link back to the thread and a duplicate check first. Chat-created cards are the main source of board duplication precisely because nobody looks first.

Why did my automation stop working?

Somebody renamed a list. Match on list identifiers rather than names where you can, and report when a list you depend on has disappeared rather than producing a silently empty result.

Should every board have a Slack channel?

Only boards somebody is actively working. A channel per board multiplies until nobody is in the right ones, and a digest from an inactive board is noise that devalues the digests from active ones.

What makes a board automatable?

Consistent list names, an agreed meaning for membership, one way of marking blocked, and due dates only on things with real deadlines. All are team agreements rather than technical work, and nothing substitutes for them.

What is the most useful thing to measure on a Trello board?

Time in list, from the action history, reported as a distribution per list. It shows where work actually queues rather than where people assume, and the tail matters more than the median because the stuck cards are the problem.

Should time in list become a target?

No. Trello enforces nothing, so a team measured on it will simply move cards sooner. Use it as evidence for a monthly conversation about where work waits, not as a number anybody is accountable for.

Is Trello's own Slack Power-Up enough?

For posting card activity to a channel, yes, and that is largely the thing worth turning off. Digests, ownerless-card reporting, time-in-list analysis, and completion notified to another team all need building.

Related reading

• Trello and CodeWords
• Connecting ClickUp to Slack
• CodeWords integrations and templates