PROJECT MANAGEMENT
Sync cross-project blockers into a Notion risk register
Nightly, collects open cross-project blockers from Asana and Linear and upserts them as rows in a Notion risk-register database, keeping status, owner, and age current.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly sync schedule
- ActionPull open blockers from AsanaAsana
- ActionPull open blockers from LinearLinear
- LogicFilter to cross-project blockers and compute age
- OutputUpsert rows into Notion risk registerNotion
What it does
Maintains a single Notion risk register that mirrors every live cross-project blocker from your tracking tools. Each blocker becomes a row with its owner, age, severity, and current status, and the row updates or closes itself as the underlying work changes.
When to use it
Use it when leadership wants one durable view of dependency risk that does not vanish when a Slack message scrolls away. The register becomes the system of record auditors and quarterly reviews can trust.
How it works
- 1A nightly schedule triggers the sync.
- 2The workflow pulls open blocked items from both Asana and Linear.
- 3A logic step filters to blockers spanning two different projects or teams and computes the age of each.
- 4It matches each blocker against existing Notion rows by a stable issue key to decide insert versus update.
- 5New blockers are created, existing ones have status and age refreshed, and resolved blockers are marked closed in the Notion risk-register database.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect NotionPages, databases, comments.
- 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.