PROJECT MANAGEMENT
Log slipped Monday blockers to a Notion cross-team risk register
When a blocking item on a Monday board sits past its timeline end with a non-Done status, this workflow appends a structured risk entry to a Notion register and tags the affected…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scheduled sweep of Monday boardsmonday.com
- LogicKeep blockers past timeline end and not Done
- ActionRead linked dependent boards and compute days latemonday.com
- ActionUpsert risk row in Notion register by item idNotion
- OutputUpdated Notion cross-team risk registerNotion
What it does
This workflow monitors blocking items on Monday boards. When a blocker's timeline end date has passed and its status is still anything other than Done, it writes a structured risk-register row in Notion capturing the slipped item, its owner, how many days late it is, and which dependent boards are exposed.
When to use it
Use it when leadership needs a single, durable view of which slipped blockers threaten which programs, rather than scattered Monday notifications. The Notion register becomes the source of truth reviewed in weekly risk standups.
How it works
- 1A scheduled trigger sweeps Monday boards each morning for items in the blocker group.
- 2A filter keeps items whose timeline end is in the past and status is not Done.
- 3A logic step computes days-overdue and reads the item's linked dependent boards from a connect-boards column.
- 4A Notion action upserts a row in the risk register keyed by item id, so re-runs update rather than duplicate.
- 5The register page is the output, time-stamped with severity derived from days late.
Set it up
What you configure once, before turning it on.
- 1Connect monday.comVisual work management for teams.
- 2Connect NotionPages, databases, comments.
- 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.