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
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
example · the steps are this template's real steps
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.
The 4 Meeting Notes steps in order, each with the instruction your AI receives there as Meeting Notes stores it.
Shareable notes with a summary, decisions, owners and open questions, confirmed by you and kept as task notes in every version.
Capture the raw record of the meeting before structuring anything.
Record:
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.
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:
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
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:
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.
The meeting notes are structured and distributed. Confirm the final notes are saved as a task note, then close out the task.
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
Meeting Notes holds at Extract until an explicit approval is given, recorded with the account that gave it.
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
no rejection path · approve to continue
gates the engine checks without you
Meeting Notes runs in a ConvOps workspace and attaches to the task type, so new work of that type starts on it. Meeting Notes saves each step's output as a task note in ConvOps, and the next Meeting Notes step reads it back. Meeting Notes needs no repository, so a chat client such as ChatGPT or Claude can run it. Connect a client , then install Meeting Notes from the catalog .
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.
new chat
workflow_step_update · Meeting Notesmore example prompts
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.
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.
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.
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.
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.