PROJECT MANAGEMENT
Monday Critical Path Slip Alert to MS Teams
Recomputes the project critical path from a Monday board on a schedule and posts a Teams alert only when a slip pushes the project's final delivery date.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled critical-path recompute
- ActionFetch items, durations, and dependenciesmonday.com
- LogicCompute critical path and compare finish date
- LogicStop if project finish unchanged
- ActionSummarize the driving causeOpenAI
- OutputPost slip alert to Teams channelMicrosoft Teams
What it does
This workflow recalculates the longest dependency chain (the critical path) across a Monday board and detects whether recent date changes have moved the overall project finish date. When and only when the end date moves, it posts a clear alert to a Microsoft Teams channel showing the old date, new date, and which task drove the change.
When to use it
Use it on schedule-sensitive programs where the team only wants to be pinged about slips that actually matter, the ones that move the launch, not every minor task wobble.
How it works
- 1A schedule triggers a recalculation a few times per day.
- 2The flow fetches all items, durations, and dependency links from the Monday board.
- 3A logic step computes the critical path and compares the new projected finish against the last stored finish.
- 4If the finish date is unchanged, the run ends silently.
- 5If it moved, OpenAI summarizes the driving cause in one line.
- 6The alert is posted to the program's Teams channel.
Set it up
What you configure once, before turning it on.
- 1Connect monday.comVisual work management for teams.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.