PERSONAL PRODUCTIVITY

Meeting Decision Log: Zoom Transcript to Notion Database

Captures decisions and action items from a recorded Zoom meeting and writes them as structured rows in a Notion database, building a searchable decision log over time.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom recording completedZoomZoom
  • ActionFetch transcript and attendeesZoomZoom
  • ActionClassify decisions vs action itemsOpenAI
  • LogicFormat entries into Notion fields
  • ActionWrite rows to Notion databaseNotionNotion
  • OutputReturn database link and countNotionNotion

What it does

Maintains a living decision log. After each recorded Zoom meeting it separates the transcript into two categories: decisions made and action items, then appends each as a row in a Notion database with date, attendees, owner, and status fields.

When to use it

When your team needs an auditable record of what was decided and why, not just a task list. Useful for leadership syncs, product reviews, and any meeting where the rationale behind a decision matters later.

How it works

  1. 1A Zoom recording-completed webhook triggers the flow.
  2. 2The transcript is retrieved from Zoom along with the meeting title and participant list.
  3. 3An OpenAI call classifies content into decisions versus action items and pulls owner and due-date metadata for each.
  4. 4A logic step formats each entry into Notion property fields and tags decisions versus tasks.
  5. 5Each decision and action item is written as a new page in the Notion database with linked properties.
  6. 6A confirmation row count and database link is returned as the output.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.