PROJECT MANAGEMENT
ClickUp daily capacity drift monitor
Runs every morning during a ClickUp sprint, recomputes remaining points against the days left and the team's historical daily burn rate.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionRead active sprint remaining points and end dateClickUp
- ActionFetch trailing average daily burnClickUp
- LogicRequired burn > sustainable burn?
- OutputPost at-risk sprint alert to SlackSlack
What it does
This is a daily early-warning monitor for in-flight ClickUp sprints. Each morning it reads the current sprint's open points and the days remaining, then compares the required daily burn to the team's historical average daily burn. If finishing on time would demand a pace the team has never sustained, it flags the sprint as at-risk and posts the math to Slack.
When to use it
Use it when commitments look fine on day one but quietly slip mid-sprint. A start-of-sprint check only catches static overcommitment; this catches scope creep, sick days, and underestimated tickets as they accumulate.
How it works
- 1A daily schedule triggers each workday morning.
- 2The flow pulls the active ClickUp sprint's remaining points and end date.
- 3It computes required daily burn = remaining points / working days left.
- 4It pulls the team's trailing average daily burn from recent sprints.
- 5A logic step checks whether required burn exceeds sustainable burn.
- 6If at risk, Slack receives a concise status with the burn gap and projected finish date.
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
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.