PROJECT MANAGEMENT
Real-time cross-team blocker alert to the blocking owner
When a Linear issue is marked blocked by an issue owned by another team, it instantly DMs the owner of the blocking issue with the downstream cost and a link.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear blocked-by relation addedLinear
- ActionLoad blocked and blocking issue detailsLinear
- LogicConfirm blocker is owned by another team
- OutputDM blocking owner with impact and linkSlack
What it does
Listens for Linear issues that get flagged as blocked. The moment a blocking relationship points at an issue owned by a different team, it notifies that blocking owner directly so the dependency does not sit silently until the next planning cycle.
When to use it
Use it when blockers routinely stall for days because the person who could unblock them never knew their work was on someone else's critical path. This closes the loop in seconds instead of at the next standup.
How it works
- 1A Linear webhook fires when an issue's blocked-by relation is added or updated.
- 2The workflow loads both the blocked issue and the blocking issue, including their team and assignee.
- 3A logic check confirms the two issues belong to different teams — same-team blockers are ignored to avoid noise.
- 4It assembles context: what is blocked, who it affects, and the blocked issue's deadline.
- 5It sends a direct Slack message to the blocking issue's owner with a one-click link back to Linear and the downstream impact spelled out.
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.