PROJECT MANAGEMENT
Escalate unresolved Loom standup blockers to a manager when they persist
Watches blockers raised in Loom standups and, when the same blocker recurs across multiple days without the linked Linear issue closing, escalates it to the team lead via Slack…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule runs after standups
- ActionExtract active blockers + speakers from LoomLoom
- ActionMatch blockers to Linear issues; check age/statusLinear
- LogicDecide if blocker persisted past threshold / is urgent
- ActionEscalate persisting blockers to lead in SlackSlack
- OutputRaise PagerDuty incident for urgent stuck blockersPagerDuty
What it does
This workflow keeps a memory of blockers spoken in Loom standups and matches them to their Linear issues. When a blocker is repeated across several standups and its issue is still open past an agreed threshold, it escalates: the team lead is messaged in Slack, and anything flagged urgent triggers a PagerDuty alert so it doesn't rot.
When to use it
When repeated blockers need a guaranteed escalation path rather than relying on someone noticing the pattern. Best for teams where a stalled dependency can quietly sink a sprint.
How it works
- 1A daily schedule runs after standups are in.
- 2Loom transcripts are read and active blockers are extracted with their speakers.
- 3Each blocker is matched to its Linear issue and age/status is checked.
- 4Logic decides whether a blocker has persisted past the threshold and whether it's urgent.
- 5Persisting blockers are escalated to the team lead in Slack.
- 6Urgent, long-stuck blockers also raise a PagerDuty incident.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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.