PROJECT MANAGEMENT
Page the on-call owner when a critical-path Monday blocker stays unresolved
Watches Monday.com for items on the critical path that are overdue and blocking others; if the blocker is still unaddressed after a grace window, it escalates by paging…
How it runs
The automated pipeline, trigger to output.
- TriggerCritical-path Monday item goes overduemonday.com
- LogicConfirm item is blocking downstream work
- LogicWait out grace window
- ActionRe-check Monday for resolutionmonday.com
- OutputPage on-call owner via PagerDutyPagerDuty
What it does
This workflow watches Monday.com items tagged as critical-path. When one becomes overdue while still blocking downstream items, it starts a grace timer. If the blocker is still neither reassigned nor rescheduled when the timer ends, it treats the stall as an incident and pages the owning team's on-call via PagerDuty.
When to use it
Use it for blockers that genuinely cannot wait for the next standup, like a launch-gating dependency. A Slack ping is easy to ignore; a page is not. This reserves the loud channel for the small number of blockers that are both overdue and on the critical path.
How it works
- 1A Monday.com item on the critical path flips to overdue.
- 2A filter confirms the item is actually blocking one or more downstream items.
- 3A timed logic step waits out a grace window for a human to act.
- 4It re-checks Monday.com to see whether the blocker was rescheduled or reassigned.
- 5If still unresolved, it opens a PagerDuty incident routed to the owning team's on-call.
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
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.
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.
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.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
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.