Write meeting minutes in Google Docs
When Kalima has written the AI summary of a meeting, Zapier copies your Google Docs minutes template and fills it in: overview, key points, decisions, action items and open questions, each in its own section, with a link to the recording.
The template keeps your layout, logo and headings. Kalima only supplies the content.
Minutes that look like your minutes
Plenty of teams keep a minutes template in Google Docs that stops being filled in around the third week. The headings are right and the meeting happened, but turning scattered notes into a clean document takes half an hour that nobody has between two meetings.
Kalima writes the content from the transcript, and Google Docs keeps the format you already agreed on. The board, the client or the project file receives the same kind of document after every meeting.
Why minutes stop being written
The template exists. Filling it is the job nobody volunteers for.
The minute-taker cannot take part
Whoever writes the minutes spends the meeting typing and has the least room to contribute to the discussion.
Every document looks different
One colleague writes bullet points, another full paragraphs, and comparing two months of meetings means getting used to two styles.
Minutes arrive days later
By the time the document is shared, people have already acted on their own memory of what was decided.
How to fill a Google Docs template from Kalima
The steps with Zapier. In n8n or Make, their Google Docs modules do the same with a Kalima API key.
Prepare the template in Google Docs
Write your minutes layout once and put a placeholder in double curly braces wherever content belongs, such as {{overview}}, {{decisions}}, {{actions}} and {{link}}: no spaces inside, plain text without bold or italics.
Trigger on New AI Summary
Connect Kalima from Settings, Integrations and Go to Zapier on the Zapier card, then choose the project whose meetings should get minutes. Switch on Only the First Summary of a Recording if a corrected summary should not create a second document.
Add Create Document From Template in Google Docs
Pick your template, name the new document, for example with the Recording Name, and choose the Drive folder it is saved in.
Map Kalima's fields to the placeholders
Zapier lists every placeholder from the template as a field. Put Overview, Key Points, Decisions, Action Items, Open Questions and the Recording Link into the matching ones. If a placeholder is missing, click Refresh fields.
Test with a real recording
Run the test with a recent meeting, open the new document in Google Docs and check the layout before you switch the Zap on.
How Kalima's fields fill your template
A suggested mapping for a classic minutes layout.
Recording Name as the document name
Each document is named after its meeting. Put the Created At date in front of it and the folder sorts itself by date.
Overview and Key Points under the summary heading
Two or three sentences on what the meeting was about, then the main points, each on its own line.
Decisions, Action Items and Open Questions in their own sections
Action items keep the person and deadline as they were named, for example Send the launch brief (Anna, Friday).
Recording Link at the end
People who were there can check a detail, people who were not can listen to the passage, as long as they have access to the recording in Kalima.
Ways teams use Kalima with Google Docs
Three setups, each with a different Google Docs action.
Before you record
Kalima runs on your own device, so nobody in the meeting sees it. That is exactly why you should announce it: tell everyone before you start and ask for their consent. If you use Kalima at work, agree on it with your data protection officer and, where there is one, your works council first.
Google Docs questions
Common questions about Kalima minutes in Google Docs.
Further reading
Related integrations
Get your next minutes written in Google Docs
Start for free, then connect Google Docs through Zapier on the Plus plan.