PROJECT MANAGEMENT
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.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: scan recently edited Notion pages
- ActionFetch meeting-notes pages edited since last runNotion
- LogicLLM extracts cross-team action items with owner and due dateOpenAI
- LogicDe-duplicate against existing ClickUp tasks by source id
- OutputCreate ClickUp dependency tasks with owner and due dateClickUp
What it does
Periodically pulls Notion pages edited since the last run (meeting notes, planning docs), extracts action items phrased as cross-team handoffs, and opens a ClickUp task for each in a shared "Cross-Team Dependencies" list. Each task carries the owner, the requesting team as a custom field, the due date, and a backlink to the source Notion block.
When to use it
When decisions and handoffs get buried in meeting notes nobody revisits, and dependencies surface only when something is already late. Ideal for teams whose source of truth is Notion docs rather than chat.
How it works
- 1A schedule fires (e.g. hourly during work hours).
- 2The flow queries Notion for pages in the meeting-notes database edited since the last run.
- 3An LLM reads each page and extracts action items that are commitments between teams, with owner and due date.
- 4Already-tracked items are de-duplicated against existing ClickUp tasks by source block id.
- 5A ClickUp task is created per new commitment, with owner, due date, requesting-team custom field, and a Notion backlink.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 3Connect OpenAIModels, embeddings, 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.
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…
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.
Daily Retro Sweep to Themed Notion Action Board
On a schedule, finds yesterday's Zoom retro recordings, transcribes them, and appends themed, owner-tagged action items as rows in a Notion board database.
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.