PROJECT MANAGEMENT
Escalate Loom-reported blockers that stay open too long
On a schedule, find ClickUp tasks tagged as standup blockers that have been open past a threshold and escalate them to the team lead in Slack with the original Loom clip.
How it runs
The automated pipeline, trigger to output.
- TriggerRecurring stale-blocker check
- ActionQuery open blocker-tagged tasksClickUp
- LogicFilter to tasks past age threshold
- ActionEscalate to lead in Slack with Loom linkSlack
- OutputComment on task to mark escalatedClickUp
What it does
It makes sure spoken blockers actually get unstuck. The workflow scans ClickUp for tasks tagged `blocker` from standups, finds the ones still open beyond your threshold (say 48 hours), and escalates each to the team lead in Slack with a link back to the original Loom video for context.
When to use it
Use it after you're already capturing standup blockers as tasks and want a safety net so aging impediments surface to a decision-maker instead of quietly rotting on the board. Best for teams where blockers are common and ownership is fuzzy.
How it works
- 1A recurring schedule (e.g. twice daily) fires the check.
- 2The workflow queries ClickUp for open tasks carrying the standup `blocker` tag.
- 3A logic step filters to tasks whose age exceeds the configured threshold.
- 4For each stale blocker, an escalation message is sent to the team lead in Slack, including the task link and the source Loom recording.
- 5The escalated tasks get a ClickUp comment noting they were flagged, preventing repeat pings on the next run.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect LoomVideo transcripts, libraries.
- 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
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.