PROJECT MANAGEMENT
Escalate stale blockers holding downstream work to PagerDuty
On a schedule, finds blockers across boards that have stayed unresolved past a threshold while downstream tasks pile up behind them.
How it runs
The automated pipeline, trigger to output.
- TriggerRecurring scan schedule
- ActionCollect open blockers and dependents from Linear and ClickUpLinear
- LogicKeep blockers past age and downstream-impact thresholds
- ActionRaise PagerDuty incident for the owning teamPagerDuty
- OutputPost escalation to team Slack channelSlack
What it does
This workflow periodically scans Linear and ClickUp for blockers that have been open longer than an allowed threshold, weights each by how many downstream tasks are stuck behind it, and raises a PagerDuty incident for any blocker that crosses both the age and impact thresholds. A Slack message gives the owning team a chance to act before it pages on-call.
When to use it
Use it when blockers quietly rot for days and nobody owns clearing them until a deadline is already blown. This forces accountability by escalating only the stale, high-impact blockers, not every flag.
How it works
- 1A recurring schedule triggers the scan.
- 2The flow collects open blockers and their downstream dependents from Linear and ClickUp.
- 3A logic step computes each blocker's age and downstream-impact count, keeping only those past both thresholds.
- 4Qualifying blockers raise a PagerDuty incident routed to the owning team.
- 5A Slack message posts the same escalation to the team channel with a link to clear the blocker.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
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…
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.
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.
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.