PROJECT MANAGEMENT
Notify downstream owners when a ClickUp task is marked blocked
When a ClickUp task is set to Blocked, finds every task that waits on it and direct-messages each downstream owner on Slack with what is now at risk.
How it runs
The automated pipeline, trigger to output.
- TriggerClickUp task status changedClickUp
- LogicOnly proceed when new status is Blocked
- ActionFetch tasks that depend on the blocked taskClickUp
- ActionResolve each downstream task's assigneeClickUp
- OutputDM each downstream owner on SlackSlack
What it does
The instant a task flips to a Blocked status in ClickUp, this workflow looks up that task's dependency graph, identifies the tasks blocked by it, and sends a targeted Slack direct message to each downstream owner explaining exactly which of their tasks is now exposed and why.
When to use it
Use it when blockers get logged in ClickUp but the people downstream only discover the stall days later. This closes the gap by pushing the bad news to the precise owners the moment it happens, not in a once-a-day report.
How it works
- 1A ClickUp status-change event triggers when any task enters a Blocked state.
- 2A filter confirms the new status is genuinely Blocked and ignores other transitions.
- 3The flow reads the blocked task's dependency relationships to collect the tasks waiting on it.
- 4For each downstream task it resolves the assignee.
- 5A direct Slack message goes to each owner naming the blocked upstream task, the blocker reason, and the downstream task at risk.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 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
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.