Meeting minutes in Google Docs

By Ai Flowi · Published 10 October 2026.

Meeting minutes in Google Docs should record supported decisions, action items and unresolved questions from supplied meeting text. Read the notes or transcript, extract the evidence for each commitment, have a participant review the draft, then save the accepted minutes. Keep missing responsible people and deadlines explicit instead of filling them in with model guesses.

example configuration, not a recorded test. This text-to-minutes proposal is documented in the catalogue; not production-tested by Ai Flowi.

1. Supply meeting text and the review context

Prepare permitted meeting notes or a reviewed transcript, the supplied meeting title, participant list and source identifier. Include the meeting date only when it is known. If a transcript contains uncertain names or speech, preserve those uncertainties before asking for minutes. A recording is outside this starting input; use the separate audio-to-Docs guide for that task.

Define what counts as a decision and an action item for this meeting. A suggestion, unresolved discussion and accepted commitment are different records. Ask the reviewer to confirm the distinction, especially where the source contains agreement without a named responsible person.

You need AI Flowi Workflow, model access through your own provider account/API key where required, and permission to process the meeting text. Model usage is paid separately. Use your own Google account with authorised Docs access; a Sheets action queue also needs its own permitted spreadsheet and appropriate connection access.

2. Read the supplied source in the correct format

Follow the Get Text reference for supplied Docs notes or the Read File guide for a supplied transcript file.

Separate the agenda from the meeting record. An agenda line naming a presenter is not evidence that the presenter accepted a follow-up action. If notes mix prepared questions with actual discussion, label those portions before extraction. Keep the participant list as context, while requiring attribution evidence from the meeting passage itself.

Keep the supplied source identifier beside the extracted text. A plain-text read may not preserve all formatting or the original locator scheme. Where evidence references matter, prepare paragraph labels or use supplied transcript timestamps and verify them. Do not create speaker attribution solely from the order in which names appear.

3. Extract decisions and actions as review records

Give Structured Output input_value the inspected meeting passages and supplied context. Preserve the language showing whether each proposal was accepted, deferred or challenged. A later “yes” needs its discussion context; it may confirm that a point was heard without accepting the proposed action.

In system_prompt, distinguish decisions, proposed actions and unresolved points, requiring a supporting passage for each commitment. Build output_schema around the records below. Keep relative timing in its original wording and add the reference event when supplied; a deadline remains unresolved when either that event or the meeting date is unknown.

Use the Structured Output implementation reference for the extraction schema, then inspect whether each record preserves the meeting’s actual degree of commitment.

4. Draft minutes around the accepted records

Use the Prompt Template guide and Language Model connection reference to draft the narrative from accepted meeting records.

Set template to group the minutes into meeting context, confirmed decisions, accepted actions and unresolved discussion. In system_message, require tentative language to remain tentative and objections to remain attached to the relevant decision. Keep each action identifier in the narrative so later wording edits can be compared with its accepted extraction record.

Have the reviewer compare the drafted wording with the record table. Watch for prose that changes “consider” into “will,” omits an objection or makes a tentative date definite. Accepted action records should remain identifiable after narrative edits. A well-written summary is not sufficient if it changes the commitment.

5. Save reviewed minutes and an optional action queue

The Create Document reference covers the minutes destination, with title identifying the supplied meeting and initial_text containing the participant-reviewed record.

The tested form-to-Docs recipe passed 42/42 using its documented CR+LF conversion, a result limited to validated literal-text creation rather than the extraction or fidelity of these minutes.

For the optional queue, follow the Append Rows operation contract, selecting value_input_option "RAW" for literal action wording.

Prepare values with the minutes identifier, action identifier, accepted task, confirmed person, timing phrase and source reference. Keep unconfirmed assignments out of the accepted-action queue and in the minutes’ unresolved section. Inspect the saved rows against the accepted minutes; saving an action records a commitment, not that the participant has completed the task. The separate Sheets tutorial provides its own duplicate-write evidence.

6. How do I check fidelity and stop at unresolved commitments in meeting minutes?

Test a suggestion without agreement, an action without an assigned person, a relative deadline and a transcript with uncertain speaker names. The minutes should retain those distinctions. Read back the document and optional sheet to ensure each action still refers to the accepted meeting record.

For an illustrative attribution check, suppose one participant proposes reviewing a draft and another says “I can look after the release.” The first passage remains a suggestion until agreement is evident. The second may indicate a commitment, but the reviewer must establish whether “after the release” means the task’s start condition or a deadline. Keep the literal phrase rather than calculating a calendar date. If the speaker label is uncertain, do not assign the commitment to a named participant solely because they appear nearby in the transcript.

Check corrections made after the meeting separately. A participant can clarify who accepted an action, but the clarification should be identified as a later review note rather than silently rewritten into the original discussion. If participants disagree about the decision, retain the disputed item as unresolved until the review process settles it. Minutes that expose that disagreement are more faithful than a summary that invents consensus.

Do not use this design for unattended task assignment, automatic reminders or an authoritative record when participants have not reviewed it. No meeting-platform intake or audio transcription is configured here. For versioned minutes, use source auditing; for a resulting procedure, see reviewed document drafting.

Plans: Go from USD8/month billed yearly (USD10 monthly), Plus from USD16 (USD20 monthly), Pro 100 from USD80 (USD100 monthly), Pro 200 from USD160 (USD200 monthly) and Pro 500 from USD400 (USD500 monthly), with 5,000 to 250,000 Flowi Tokens/month and top-ups; 1 token per node run; third-party API and model usage is not included.

The use-case hub describes existing starters. This deliverable adds evidence-linked minutes and an action review record from supplied text.