PROJECT MANAGEMENT
Carry-Forward Blocker Alert to Incoming On-Call
When a Linear issue is marked blocked near the end of a shift, immediately drafts a focused escalation note and sends it to the incoming region's on-call via Slack and Outlook…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue status changes to blockedLinear
- LogicCheck the change landed in the outgoing shift's final hours
- ActionPull blocking comment, assignee, and linked context from LinearLinear
- ActionDraft a focused escalation noteOpenAI
- ActionNotify incoming on-call in SlackSlack
- OutputSend parallel escalation email via OutlookOutlook
What it does
Catches blockers the moment they're raised late in a shift and makes sure they cross the handoff cleanly. Instead of a blocker getting buried in a daily summary, this fires per-issue: it captures the blocking context and routes a short, actionable escalation to whoever is starting their day next.
When to use it
Use it when a single stuck issue can stall a whole region's progress for hours. Best for squads where the cost of an unattended overnight blocker is high and you want the next on-call to act before standup.
How it works
- 1A Linear event trigger fires when an issue's status changes to blocked.
- 2A logic step checks whether the change happened within the outgoing region's final shift hours; if not, it stops.
- 3Pulls the issue's blocking comment, assignee, and linked work for context.
- 4Drafts a concise escalation: what's blocked, why, and the suggested next move.
- 5Posts it to the incoming on-call in Slack and sends a parallel Outlook email for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect OutlookMail, calendar, contacts.
- 4Connect OpenAIModels, embeddings, files.
- 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.