PROJECT MANAGEMENT
Alert downstream teams when a Linear blocker issue slips its due date
Watches Linear blocker issues for due-date changes and, when one slips, finds every issue that depends on it and posts a cascade alert to the affected teams' Slack channels…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue updated webhookLinear
- LogicKeep only later due-date slips on blocker issues
- ActionFetch downstream blocked-by dependency chainLinear
- LogicGroup at-risk issues by owning team
- OutputPost cascade alert to each team's Slack channelSlack
What it does
When a blocking Linear issue's due date moves later, this workflow traces the chain of issues that depend on it and warns each downstream team in Slack before their own deadlines quietly become impossible.
When to use it
Use it when teams share a dependency graph in Linear and a single slipped blocker silently pushes three other teams off schedule. Instead of someone noticing in standup days later, the affected owners hear about it the moment the date moves.
How it works
- 1A Linear webhook fires whenever an issue is updated.
- 2A filter keeps only events where the due date moved later AND the issue blocks at least one other issue.
- 3The workflow fetches the full set of issues marked as "blocked by" this one, recursively, to build the cascade.
- 4For each downstream issue it computes the new at-risk date assuming the slip propagates.
- 5It groups the affected issues by their owning Linear team.
- 6It posts one Slack message per affected team channel listing each at-risk issue, its owner, the old date, and the projected new date.
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.