PROJECT MANAGEMENT
Blocked Issue Escalation Log to Notion with Slack Alert
When a Linear issue is labeled blocked, it logs the blocker to a Notion tracking database and DMs the issue's lead with the blocking details so it never goes silent.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear 'blocked' label addedLinear
- LogicCheck for existing open blocker row
- ActionLog blocker to Notion databaseNotion
- OutputDM issue lead in Slack with detailsSlack
What it does
Turns the 'blocked' label into an accountable escalation. The moment an issue is marked blocked in Linear, the flow records a row in a Notion blocker-tracking database — capturing the issue, owner, and how long it's been stuck — and pings the responsible lead in Slack so blockers surface in standup instead of rotting in a backlog.
When to use it
Use it when blocked work tends to disappear between standups, or when you want a durable audit trail of what stalled each sprint and who owned the unblock. Ideal for teams running sprint retros off real blocker data.
How it works
- 1A Linear webhook fires when the 'blocked' label is added to an issue.
- 2A logic step checks whether the issue already has an open blocker row to avoid duplicate logging.
- 3If it's new, the flow writes a row to the Notion blocker database with issue title, assignee, sprint, and timestamp.
- 4The final step sends a Slack direct message to the issue lead summarizing the blocker and linking the Notion entry for follow-up.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect NotionPages, databases, comments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.