PROJECT MANAGEMENT
Flag ClickUp tasks blocked on a stalled engineering PR
Detects when a GitHub pull request that an upstream task depends on has gone stale past an SLA.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled PR staleness check
- ActionRead linked PR activity + review stateGitHub
- LogicCompare PR age to SLA + deadline
- ActionMark downstream ClickUp task at-riskClickUp
- OutputAlert dependent team in SlackSlack
What it does
This workflow bridges engineering and delivery. When a GitHub PR that a ClickUp task is waiting on sits without review or merge beyond an SLA, it computes how stale the PR is, marks the dependent ClickUp task as at-risk, and tells the waiting team in Slack exactly which PR is holding them up.
When to use it
Use it when delivery tasks quietly depend on code that is stuck in review. It surfaces the real cause of a blocker (a stalled PR) to the non-engineering team who would otherwise just see "in progress."
How it works
- 1A scheduled check runs against linked GitHub PRs.
- 2It reads each PR's last activity and review state.
- 3Due-date math compares PR staleness against the SLA and the downstream task's deadline.
- 4PRs within SLA are skipped; breaches continue.
- 5The downstream ClickUp task is set at-risk and the dependent team is alerted in Slack with the PR link and its age in days.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 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
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.