PROJECT MANAGEMENT
Publish a live dependency-risk page when a Linear blocking issue goes overdue
When a Linear issue that blocks others passes its due date unresolved, this workflow collects all blocked issues and regenerates a Confluence status page summarizing the at-risk…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear blocking issue passes due date, not DoneLinear
- LogicConfirm it blocks at least one open issue
- ActionWalk blocked-by graph, group by teamLinear
- LogicBuild risk summary with severity rollup
- OutputPublish or update Confluence status pageConfluence
What it does
This workflow watches Linear issues that block other issues. When such a blocker passes its due date without reaching Done, it pulls every issue in its blocked-by chain and rewrites a Confluence page that shows the slipped blocker, the full at-risk tree, and which teams own the exposed work.
When to use it
Use it when stakeholders outside engineering need a readable, always-current snapshot of dependency risk without poking through Linear. The Confluence page is something a program manager can link in a status update.
How it works
- 1A Linear trigger fires when an issue with blocking relationships passes its due date and is not Done.
- 2A filter confirms the issue actually blocks at least one other open issue.
- 3A Linear action walks the blocked-by graph and groups dependent issues by owning team.
- 4A formatting step builds a risk summary with severity and team rollup.
- 5A Confluence action publishes or updates the dependency-risk status page as the output.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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
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.
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.
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.
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…
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.