Documentation Workflows Workflow Beginner

AI Meeting Notes Workflow

Turn a meeting transcript into notes people actually use — a faithful summary, the action items pulled out and assigned, and a clean shareable format.

The problem

A raw transcript is technically a record and practically useless — nobody rereads forty minutes of dialogue to find the one decision that affects them. The value is in what gets extracted: what was decided, who owns what, and by when. Doing that by hand is the chore that quietly doesn't happen, so the decisions evaporate. This workflow makes it mechanical: summarize the discussion faithfully, pull the action items out as their own list with owners, and format the result so it's actually worth sending.

Recommended workflow

Each step uses an existing NewPrompt tool, pre-filled by a matching resource. Open the resource to read it, or jump straight into the tool with the inputs ready.

  1. Summarize the discussion faithfully

    Condense the transcript into what was actually discussed and decided, keeping attribution straight, so the summary reflects the meeting rather than the model's guess at it.

    Goal A faithful summary of decisions and discussion.

    Open this step in Structured Summary Prompt
  2. Pull out the action items

    Extract the commitments as a separate list — task, owner, and any due date — because an action buried in a paragraph is an action nobody does.

    Goal A clean action-item list with owners.

    Open this step in Extraction Prompt Generator
  3. Format notes worth sending

    Lay the summary and actions into a consistent notes template so the output is scannable and the same shape every meeting.

    Goal Shareable, consistently formatted meeting notes.

    Open this step in Markdown Output Builder

Expected outcome

A transcript becomes notes people read: a faithful summary, an action list with owners, and a clean format — so decisions and commitments survive the meeting instead of dissolving in the recording.

Best for

  • Turning recorded meetings into shareable notes
  • Making sure action items get captured and owned
  • Keeping meeting notes in a consistent format

Not for

  • A meeting you didn't record or transcribe
  • Analyzing feedback across many sources — use the AI Customer Feedback Analysis Workflow

FAQ

Do I need a transcript?

Yes. The workflow starts from text — a transcript, or a transcription of the recording. It structures and extracts from that; it can't sit in on the call for you.

Why separate the action items?

Because actions buried in prose get missed. Pulling them into their own list with owners and dates is the difference between notes that inform and notes that drive follow-through.

How is this different from a summary prompt?

A summary prompt does step one. This adds extracting and assigning the action items and formatting the whole thing into shareable notes — the parts that make meeting notes actually useful.

Tip: Each step's resource opens its tool pre-filled — start at step one and carry the output forward.

All playbooks