Meeting Notes AI workflow template: Meeting notes people can act on.

The ConvOps Meeting Notes template makes your AI turn a meeting into shareable notes: save the raw record, extract the summary, decisions, owners and open questions, and format them for the team. It stops once, so you confirm the decisions and owners before anything is distributed. Every version is kept as a task note.

4 steps · 1 approval

Meeting Notes · example runyour AI client
  1. 01Capture
  2. 02Extractwaits for approval
  3. 03Distribute
  4. 04Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Meeting Notes template do?

For team leads and operators who leave meetings with rough notes or a transcript and need clean decisions and owners the same day.

Meeting Notes is stored in ConvOps as four steps, and your AI client receives them one at a time. A Meeting Notes run holds at Extract until an explicit approval is given.

  • Turn rough notes into a summary with decisions and action items
  • Write up a team standup into a shareable recap
  • Summarize a transcript into decisions, owners, and next steps
step by step

How does the Meeting Notes workflow run?

The 4 Meeting Notes steps in order, each with the instruction your AI receives there as Meeting Notes stores it.

Capture
Extractapproval
Distribute
Completeclosing note

Shareable notes with a summary, decisions, owners and open questions, confirmed by you and kept as task notes in every version.

  1. 01

    Capture

    the agent works

    Capture the raw record of the meeting before structuring anything.

    Record:

    • Meeting title, date, and who attended
    • The purpose or agenda
    • What was discussed: paste notes, a transcript, or your recollection

    If the record is incomplete, ask the operator for the missing pieces.

    Save the raw meeting record as a task note with task_notes_add. The next step (Extract) reads this note.

  2. 02

    Extract

    waits for your approval

    Read the task notes with task_notes_list: the note from the Capture step contains the raw record. Work from it.

    Extract clean structure. What good looks like:

    • A two- or three-line summary of the meeting
    • Key discussion points, condensed
    • Decisions made, stated plainly
    • Action items, each with an owner and a due date where known
    • Open questions still unresolved

    Capture only what was said: do not invent decisions or owners.

    Save the structured notes as a task note with task_notes_add. Then ask the operator to confirm the decisions and owners are right before distributing. This is a checkpoint: once notes go out they shape what people act on, so the AI cannot advance until you approve.

    no rejection path · the run moves on only when approved

  3. 03

    Distribute

    the agent works

    Read the task notes with task_notes_list: the note from the Extract step contains the confirmed notes. Work from it.

    Format the notes for sharing:

    • Clean, scannable layout: summary, decisions, action items, open questions
    • Action items grouped by owner so each person sees their part
    • The right destination (email, doc, channel) for this team

    Share the notes with the people who need them, or hand the formatted version to the operator to post.

    Save the final shared notes as a task note with task_notes_add so the record of what was distributed stays on file.

  4. 04

    Complete

    closes with a note

    The meeting notes are structured and distributed. Confirm the final notes are saved as a task note, then close out the task.

reach for it when

  • You leave a meeting with a transcript or rough notes and owe the team a clean version.
  • Decisions and owners must be right before anyone acts on them.
  • Every version should be kept, from the raw record to the shared notes.

something else fits when

  • The notes are for the other side of a client call: Meeting Follow-Up drafts that message.
  • Nothing was decided and nobody owns anything.
  • A decision still has to be made, which is Decision Memo's job.
example · hospital operationsenterprise

The weekly bed-management huddle

The coordinator pastes the transcript. The agent extracts three decisions and five owners, the coordinator corrects one owner at Extract, and the notes go to the ward leads.

Extract approval

where approval is required

Where do you approve in Meeting Notes?

Meeting Notes holds at Extract until an explicit approval is given, recorded with the account that gave it.

step 2

Extract

Once notes go out they shape what people act on. You confirm the decisions and the owners are right before the AI distributes anything.

what you review

  • A two- or three-line summary of the meeting
  • Key discussion points, condensed
  • Decisions made, stated plainly
  • Action items, each with an owner and a due date where known
  • Open questions still unresolved

no rejection path · approve to continue

gates the engine checks without you

  • Complete closes Meeting Notes only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Meeting Notes?

make it yours

How do you customize Meeting Notes?

Once installed, Meeting Notes is a workflow in your workspace. Ask your AI to change Meeting Notes in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

In Distribute, always post the notes to our #team channel format.
workflow_step_update · Meeting Notes
Done. Meeting Notes in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Distribute, always post the notes to our #team channel format."
  • "Add a step after Distribute that turns each action item into its own task."
  • "In Capture, also record which project the meeting belongs to."
the difference

Meeting Notes: without a workflow vs with it

  • Notes live in one person's notebook and the decisions are forgotten by the next meeting
  • The summary ships with an action item assigned to nobody and a decision left out
  • You write up half the notes, get interrupted, and lose the thread of what was decided
  • The Meeting Notes process lives in a prompt, and each run follows it a little differently
  • The AI drives raw notes into a structured, shareable recap that the whole team can find
  • The AI pauses at a checkpoint so you confirm the extracted decisions and owners before anything is shared
  • The AI saves the raw record and the structured notes as notes, so a later session resumes the write-up intact
  • Your AI receives the 4 stored steps one at a time, and the run holds at Extract until an explicit approval is given
questions

Meeting Notes template FAQ

What is the ConvOps Meeting Notes template?

The ConvOps Meeting Notes template makes your AI turn a meeting into shareable notes: save the raw record, extract the summary, decisions, owners and open questions, and format them for the team. It stops once, so you confirm the decisions and owners before anything is distributed. Every version is kept as a task note.

Will the AI invent decisions or owners?

The ConvOps Extract step tells your AI to capture only what was said and not to invent decisions or owners. It produces a short summary, key points, decisions, action items with owners and due dates where known, and open questions. The run then holds at Extract until an explicit approval is given that the decisions and owners are right, before anything is distributed.

Where are the notes stored?

In ConvOps task notes. Each step saves its output with task_notes_add: the raw record at Capture, the structured notes at Extract, the shared version at Distribute. The next step reads the previous note with task_notes_list, so a fresh session or a different AI client can pick up where the last one stopped, and the record of what was distributed stays on file.

How is it different from Meeting Follow-Up?

Both are ConvOps templates that start from a meeting record. Meeting Notes produces internal notes for the team, with action items grouped by owner, and its approval sits at Extract. Meeting Follow-Up drafts a message to the other side of a call, with a recap, actions and one next step, and holds the run at Send Review before the message goes out.

How are the notes shared?

The ConvOps Distribute step formats the confirmed notes for sharing: summary, decisions, action items and open questions, with action items grouped by owner so each person sees their part. Your AI shares them to the right destination for your team (email, doc or channel) with the tools it is connected to, or hands you the formatted version to post yourself.