PROJECT MANAGEMENT
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.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionList yesterday's Zoom retro recordingsZoom
- LogicSkip already-processed recordings
- ActionTranscribe and extract themed owned itemsOpenAI
- ActionAppend rows to Notion action boardNotion
- OutputReturn per-call ingestion digest
What it does
This workflow runs on a daily schedule, checks Zoom for any retrospective recordings from the previous day, and processes each one into a Notion action board. It transcribes the call, organizes the discussion into retro themes, extracts owned action items, and writes each item as a new row in a Notion database with theme, owner, and source-call columns filled in.
When to use it
Use it when retros happen across multiple teams or time zones and you want a single Notion board built automatically each morning, rather than wiring a trigger per meeting. It is the batch alternative to event-driven capture.
How it works
- 1A daily schedule fires in the morning.
- 2The workflow lists Zoom retro recordings from the prior day.
- 3A logic step skips any already-processed recording.
- 4For each new recording, the transcript is fetched and OpenAI extracts themed, owned action items.
- 5Each action item is appended as a Notion database row with theme, owner, and call-date fields.
- 6A digest of how many items landed per call is returned.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 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.
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.
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.
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.