Trello Due-Date Reminder and Escalation
A scheduled flow scans a Trello board for cards due today or overdue, notifies the card members in Teams, emails the board owner a digest, and adds an escalation comment on cards overdue past a threshold. Keeps Trello work on track without manual chasing.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
Overview
This flow enforces deadlines across a Trello board. On a daily schedule (08:00 Eastern) it reads every card, filters to those due today or overdue, posts a nudge to a Microsoft Teams channel for each, adds an escalation comment back on a card once it passes an overdue threshold, and emails the board owner a consolidated HTML digest.
Why it matters: Trello's built-in reminders are per-user and easy to miss. Consolidated, escalating, owner-visible deadline management keeps work moving without manual chasing.
Ships Off (demo).
Use Case
A delivery team running its work on Trello wants automatic daily deadline chasing: a Teams nudge per due/overdue card, an escalation comment on cards overdue past a configurable number of days, and a single owner digest email summarizing everything - all driven from one board with zero hardcoded values.
Flow Architecture
Daily 08:00 Recurrence
RecurrenceDaily deadline sweep at 08:00 Eastern.
Initialize Config & Cutoff
Initialize variable (x7)Binds board, escalation days, owner email, Teams group/channel; computes the start-of-tomorrow cutoff and seeds the digest-rows accumulator.
List Cards
Trello - ListCardsReads all open cards on the board.
Filter Due / Overdue
Filter arrayKeeps cards with a non-null due date earlier than the start-of-tomorrow cutoff (due today or overdue).
For Each Card
Apply to eachComputes days overdue, posts a per-card nudge to Teams, adds an escalation comment when overdue past the threshold, and appends an HTML digest row.
Compose Digest
ComposeWraps the accumulated rows in a styled HTML table.
Email Owner Digest
Outlook - SendEmailV2Emails the consolidated digest to the board owner.
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_TrelloBoardId | String | REPLACE_WITH_TRELLO_BOARD_ID | The Trello board to monitor. |
| flowlibs_OverdueEscalationDays | String | 3 | Days overdue before an escalation comment is added. |
| flowlibs_OwnerEmail | String | me@contoso.com | Digest email recipient (board owner). |
| flowlibs_TeamsGroupId | String | <your-team-id> | Teams team (group) ID for nudges. |
| flowlibs_TeamsChannelId | String | <your-channel-id> | Teams channel ID for nudges. |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Trello | shared_trello | ListCards AddCommentToCard |
| Microsoft Teams | shared_teams | PostMessageToConversation |
| Office 365 Outlook | shared_office365 | SendEmailV2 |
Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.
Customization Guide
Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.
- Member DMs
- Instead of (or in addition to) a channel post, DM each card member their own due cards by resolving member ids to UPNs and using Teams PostMessageToRecipient.
- Per-board portfolio
- Wrap List Cards in an outer Apply to each over a list of board ids to produce one portfolio digest.
- Weekend skip
- Gate the body on dayOfWeek(utcNow()) so it only runs Mon-Fri.
- No-repeat escalation
- Add a Trello label (e.g. Escalated) inside the escalation branch and exclude it in the filter so a card escalates only once.
- Threshold & schedule
- Change flowlibs_OverdueEscalationDays or the Daily_0800 recurrence without touching flow logic.
Key Expressions
The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.
EXPR.01Start-of-tomorrow cutoff
Upper bound for due today or overdue.
EXPR.02Due today or overdue (filter)
Null-safe filter keeping due-today and overdue cards.
EXPR.03Days overdue
Whole days a card is past due.
EXPR.04Escalation gate
True once a card passes the escalation threshold.
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.