PROJECT MANAGEMENT
Monday board stall detector with PagerDuty escalation
It watches a Monday sprint board for items that have sat in In Progress past their expected cycle time and, when stalled work piles up beyond a threshold, escalates to the owning…
How it runs
The automated pipeline, trigger to output.
- TriggerMonday board item-update eventmonday.com
- ActionRead board items, statuses, and in-progress timestampsmonday.com
- LogicFlag items aging past expected cycle time
- LogicThreshold: stalled count vs. safe limit
- OutputEscalate stalled pile-up to PagerDutyPagerDuty
What it does
It scans a Monday.com sprint board, finds items stuck in In Progress longer than their expected cycle time, and counts how much stalled work has accumulated. When the stalled count crosses a threshold that puts the sprint goal at risk, it pages the sprint lead.
When to use it
Use it when work-in-progress quietly stalls and nobody notices until standup. This catches aging items automatically and only escalates when the pile-up is large enough to threaten the commitment, so you avoid alert fatigue.
How it works
- 1An item-update event on the Monday sprint board triggers the run.
- 2It reads all board items, their current status column, and the timestamp each entered In Progress.
- 3It flags items whose in-progress age exceeds the configured expected cycle time.
- 4A threshold step checks whether the count of stalled items exceeds the safe limit.
- 5If under the limit, it records the snapshot and exits; if over, it builds an escalation payload listing the oldest stalled items.
- 6It triggers a PagerDuty incident routed to the sprint lead's escalation policy.
Set it up
What you configure once, before turning it on.
- 1Connect monday.comVisual work management for teams.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.