PROJECT MANAGEMENT
Trello Blocked-WIP Detector with Slack Escalation
Scans Trello daily for cards that are blocked or have sat untouched past a threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule fires
- ActionFetch active cards with labels + last-activity timeTrello
- LogicFilter to blocked or stale-past-threshold cards
- LogicBranch by stall age: nudge owner vs escalate
- OutputSend owner nudges and lead escalation to SlackSlack
What it does
It finds in-progress Trello cards that have stopped moving — flagged with a blocked label or idle longer than your threshold — and turns them into targeted Slack nudges. Recently stuck cards ping the assignee directly; long-stalled cards escalate to a leadership channel so blockers don't quietly rot in WIP.
When to use it
Use it when cards routinely get stuck mid-flow and the team only notices at standup. Ideal for keeping work-in-progress honest and surfacing blockers the same day they form instead of days later.
How it works
- 1A daily schedule triggers the scan.
- 2Trello returns active cards with their labels, assignees, and time since last activity.
- 3A filter keeps only cards that are blocked-labeled or idle beyond the threshold.
- 4A branch sorts each stuck card into 'nudge owner' or 'escalate to lead' based on how many days it has stalled.
- 5Owner nudges and the escalation digest are posted to the appropriate Slack destinations, each linking straight back to the card.
Set it up
What you configure once, before turning it on.
- 1Connect TrelloKanban boards for everything.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.