PROJECT MANAGEMENT
Compute the critical path of a Notion roadmap and publish it
Reads a Notion project database with task durations and dependencies, computes the longest blocking chain (critical path) to the launch date.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run for a milestone
- ActionRead tasks, durations, and dependencies from NotionNotion
- LogicForward/backward pass to find zero-float tasks
- LogicFlag near-critical low-float tasks
- OutputPublish critical path summary page in NotionNotion
What it does
Treats a Notion project database as a dependency network, computes the critical path — the sequence of dependent tasks that determines the earliest possible finish — and publishes it as a readable summary. Any slip on a critical-path task slips the whole milestone, so this makes the load-bearing chain explicit.
When to use it
Use it before a launch review or whenever a roadmap has enough cross-task dependencies that "what actually drives the date" is no longer obvious. Re-run after any re-plan to see how the critical path shifted.
How it works
- 1A manual run starts the workflow against a chosen milestone.
- 2Read all tasks, their estimated durations, and depends-on links from the Notion database.
- 3Run a forward/backward pass to compute earliest/latest start, identifying zero-float tasks as the critical path.
- 4Branch: flag any task whose float is dangerously low as near-critical.
- 5Write an ordered critical-path list, total duration, and the near-critical watchlist to a Notion summary page.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.