PROJECT MANAGEMENT
Dependency SLA-breach alert when blockers exceed resolution target
Checks open cross-team blockers in Linear against a per-team resolution SLA, and the moment one breaches its target it fires a high-priority Slack alert to the program lead…
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent SLA-sweep schedule fires
- ActionFetch open blocked Linear issuesLinear
- LogicCompute time-in-state vs team SLA target
- LogicKeep only SLA-breached blockers
- OutputSend high-priority breach alert to SlackSlack
What it does
This workflow holds each cross-team blocker to a resolution SLA — for example, 4 business days to clear a dependency. It repeatedly checks open blocked Linear issues, compares time-in-state against the target for the owning team, and alerts the instant an item breaches. The alert names the responsible owner, the waiting team, and how far past SLA the blocker now is.
When to use it
Use it when your organization has committed to dependency-resolution targets and program leads need to catch breaches as they happen rather than discovering them retroactively.
How it works
- 1A frequent schedule kicks off the SLA sweep.
- 2The workflow fetches open dependency-labeled Linear issues in a Blocked state.
- 3For each, it calculates business-hours time-in-state and looks up the owning team's SLA target.
- 4A branch isolates only the issues that have breached their target.
- 5For every breach, it posts a high-priority Slack alert to the program lead with owner, elapsed time, and overage so action can be taken immediately.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.