PROJECT MANAGEMENT
Daily critical-path slip digest with auto-rescheduled successors
Runs every morning, scans an Asana portfolio for tasks that finished or moved later than their dependency required, auto-shifts the immediate successors.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionPull portfolio tasks and dependenciesAsana
- LogicFlag predecessor/successor date overlaps
- ActionShift affected successors to restore gapsAsana
- OutputEmail critical-path slip digestGmail
What it does
On a daily schedule this workflow audits an Asana portfolio for dependency violations where a predecessor's actual or new due date now overlaps its successor's start. It shifts the affected successors to remove the overlap and compiles a digest of every slip detected that day.
When to use it
Use it for program-level oversight when you want a once-a-day reconciliation instead of reacting to every individual edit, and you need the program lead to see the cumulative critical-path impact in one email.
How it works
- 1A scheduled trigger runs each weekday morning.
- 2The workflow pulls all portfolio tasks with their dependencies and dates.
- 3A logic step flags every predecessor-successor pair where the predecessor now ends after the successor starts.
- 4For each flagged pair it shifts the successor's start and due dates to restore the gap in Asana.
- 5A formatted critical-path slip digest is emailed to the program lead via Gmail.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect GmailRead, draft, send, label.
- 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.