PROJECT MANAGEMENT
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.
How it runs
The automated pipeline, trigger to output.
- TriggerMorning schedule fires
- ActionQuery Linear for overdue dependency issuesLinear
- LogicBranch by lateness: nudge vs escalate
- ActionDM the owner in Slack with overdue issueSlack
- OutputPost escalation and daily summary to status channelSlack
What it does
Scans Linear daily for issues labeled `cross-team-dependency` that are overdue and still open. For each, it pings the assignee in Slack DM with the issue and how many days late it is. If an issue is more than a set threshold past due, it also posts to the requesting team's channel so the blocked side has visibility.
When to use it
When tracked dependencies exist but slip silently and the blocked team finds out too late. Use this to close the loop: every promise that goes red gets a nudge, and chronic slips get surfaced upward.
How it works
- 1A morning schedule triggers the run.
- 2The flow queries Linear for open dependency-labeled issues with a due date in the past.
- 3A branch sorts each issue by lateness: a gentle nudge under the threshold, an escalation over it.
- 4For nudges, a Slack DM goes to the assignee with the issue link and days overdue.
- 5For escalations, a message also posts to the requesting team's channel tagging their lead.
- 6A summary of all overdue items posts to a project-status channel.
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.
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.
Daily Retro Sweep to Themed Notion Action Board
On a schedule, finds yesterday's Zoom retro recordings, transcribes them, and appends themed, owner-tagged action items as rows in a Notion board database.
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.