PROJECT MANAGEMENT
Escalate critical-path blockers stuck past SLA to PagerDuty
When a high-priority Asana or Linear item stays blocked past its SLA, this opens a PagerDuty incident and tags the accountable lead so critical-path stalls get an owner.
How it runs
The automated pipeline, trigger to output.
- TriggerShort-interval workday schedule
- ActionPull high-priority blocked items (Asana + Linear)Asana
- LogicKeep items past SLA, not yet escalated
- ActionOpen PagerDuty incident with contextPagerDuty
- OutputMark source item EscalatedLinear
What it does
Turns a long-running blocker on a critical-path item into a real escalation. If a high-priority task in Asana or a high-priority Linear issue remains blocked beyond its SLA window, the flow opens a PagerDuty incident routed to the right escalation policy and notes the blocker context.
When to use it
Use it for launch-critical or revenue-impacting work where a stuck dependency can't wait for the next standup. Best for teams that already use PagerDuty for operational urgency and want delivery blockers treated with the same seriousness as outages.
How it works
- 1A scheduled trigger runs on a short interval through the workday.
- 2The flow pulls blocked, high-priority items from Asana and Linear.
- 3A logic step keeps only items whose time-in-blocked exceeds the configured SLA and that aren't already escalated.
- 4For each, it opens a PagerDuty incident with the item link, owner, and how long it has been blocked.
- 5It marks the source item as Escalated so the same blocker doesn't page twice.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.