PROJECT MANAGEMENT
Escalate via PagerDuty when a critical-path ClickUp blocker slips its deadline
When a ClickUp task on the project critical path misses its due date while incomplete, this workflow checks how many downstream dependencies it gates and, above a threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerClickUp critical-path task misses due dateClickUp
- ActionCount open downstream dependent tasksClickUp
- LogicBranch: downstream count over threshold
- ActionOpen PagerDuty incident with impact summaryPagerDuty
- OutputNotify team in MS Teams with incident linkMicrosoft Teams
What it does
This workflow monitors critical-path tasks in ClickUp. When one misses its due date and is still open, it counts the downstream tasks it blocks. If that count crosses a configured threshold, it treats the slip as a program-level risk: it opens a PagerDuty incident and posts an alert to MS Teams so the right people respond immediately.
When to use it
Use it on high-stakes projects where a critical-path slip should page someone, not just generate a notification. The threshold keeps low-impact slips from creating noise while ensuring genuinely cascading ones escalate.
How it works
- 1A ClickUp trigger fires when a task tagged critical-path passes its due date unfinished.
- 2A ClickUp action counts the open downstream tasks that depend on it.
- 3A branch compares the downstream count against the escalation threshold.
- 4If above threshold, a PagerDuty action opens an incident with the slipped task and impact summary.
- 5An MS Teams message is the output, notifying the channel with the incident link.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.