PROJECT MANAGEMENT
Weekly critical-path risk report across boards, written to Notion
Each week an agent traces dependency chains across Linear, ClickUp, and Asana, identifies the longest at-risk critical paths.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull dependencies from Linear, ClickUp, and AsanaClickUp
- LogicAgent traces and ranks cross-board critical paths
- ActionPublish the ranked risk report to NotionNotion
- OutputPost report link to leadership SlackSlack
What it does
Once a week, an agent gathers dependency relationships from Linear, ClickUp, and Asana, reconstructs the critical paths that span teams, and scores each path by how exposed it is to current blockers and slipping dates. It writes a ranked, narrated risk report into a Notion page so leadership reads one source instead of three boards.
When to use it
Use it when work is fragmented across multiple boards and no single view shows where the program's true bottlenecks are. The weekly report gives leadership a consolidated, prioritized risk picture.
How it works
- 1A weekly schedule starts the run.
- 2The flow pulls issues, tasks, and dependency links from Linear, ClickUp, and Asana.
- 3An agent stitches the cross-board graph, traces critical paths, and ranks them by blocker exposure and deadline proximity.
- 4It drafts a narrated report with the top at-risk chains, owners, and recommended escalations.
- 5The report is published or updated on a designated Notion page.
- 6A Slack link to the fresh report is posted to the leadership channel.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 3Connect AsanaTasks, projects, milestones — everywhere.
- 4Connect NotionPages, databases, comments.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.
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…
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.
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.
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.