PROJECT MANAGEMENT
Weekly dependency-risk rollup from ClickUp into a Snowflake dashboard
Each week, snapshots ClickUp milestone health and dependency chains, computes a blocked-task risk score per project.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull milestones, statuses, and dependencies from ClickUpClickUp
- LogicScore downstream blocked tasks per at-risk milestone
- ActionAppend the weekly risk rows to SnowflakeSnowflake
- OutputPost the highest-risk project of the week to SlackSlack
What it does
Produces a weekly, queryable record of dependency-chain risk. It snapshots every tracked ClickUp milestone, follows dependency links to count downstream tasks blocked by at-risk milestones, computes a risk score per project, and appends the result to a Snowflake table that feeds your reporting dashboard.
When to use it
Use it when leadership wants trend lines, not one-off alerts: is schedule risk improving or compounding week over week, and which projects carry the deepest dependency exposure. It builds the historical dataset other templates only react to.
How it works
- 1A weekly schedule kicks off the snapshot.
- 2The flow pulls milestones, statuses, and dependency relationships from the configured ClickUp spaces.
- 3For each milestone flagged at-risk, it counts and weights the downstream tasks blocked, producing a per-project risk score.
- 4It assembles a tidy row set with the run timestamp, project, milestone, blocked count, and score.
- 5The rows are appended to a Snowflake table powering the leadership dashboard, with a Slack confirmation noting the week's highest-risk project.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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.