Google Meet guide

Using Sonar with Google Meet.

Meet transcripts are a second switch on your Google Calendar connection. It adds one read-only scope, meetings.space.readonly, and about once a week Sonar reads the transcripts of your own Meet calls from the last seven days, up to five, through Google's Meet API, mines them for the moments worth saying, and discards the text. Nothing publishes without your approval.

01

What it does

The calendar knows that a call happened; the transcript knows what was said. When Meet transcripts are on, Sonar lists your conference records from the last seven days and, for up to five of them, reads the transcript entries with each speaker's name resolved, so a decision, a win or a lesson comes out with its outcome attached. The meeting's title comes from the calendar event that created it; an ad-hoc call keeps its day and time instead.

Everything is read through Google's Meet API. Sonar never asks for Drive access and never downloads a recording, and a call whose transcription was off is simply skipped.

Because a Meet transcript carries your own words under your own name, this source can also teach Sonar your spoken register: how you talk on a call, kept apart from how you write. That is a separate opt-in in Settings, Voice, off until you turn it on, and it shapes scripts and takes, never your written posts.

02

Requirements

  • A Sonar account with Google Calendar connected. The Meet transcripts switch reads Connect Google Calendar first until it is.
  • Meet calls with transcription turned on. Sonar reads the transcripts Meet produced; it cannot transcribe a call itself.
  • One more permission at Google: read-only access to your Meet conference records and transcripts (meetings.space.readonly), added to the same connection and verified by Google in August 2026.

03

Adding it

  1. 01

    Connect Google Calendar first

    In Settings, Connected sources, flip the Google Calendar switch and allow the calendar permission. The Meet transcripts row sits right under it.

  2. 02

    Flip the Meet transcripts switch

    Google's consent screen asks for the Meet read-only permission on top of the calendar one you already granted. Choose Allow.

  3. 03

    Let the first read run

    You land back in Sonar and the first read runs together with the calendar's. The Meet transcripts row shows its own receipt: how many transcripts were read and how many moments were kept, with the meeting titles.

  4. 04

    Decide whether it may teach your spoken voice

    Optional. In Settings, Voice, the sources switch names the exact sources it would read, Meet transcripts among them. Off by default; on, your own lines shape scripts and takes.

04

Using it

There is nothing to operate. Meet syncs together with Google Calendar, about once a week and after you connect, and Sync all at the top of Connected sources runs it now. Each read covers the last seven days and up to five calls; the row shows how many transcripts were read and how many moments were kept.

The moments land on Home and in the chat as material for drafts in your voice, and the freshest are dealt into your weekly deck. Their provenance names the call, for your eyes only. In a draft, the people on the call become roles, a client's COO or someone on my team; the names never travel.

05

Removing it

Settings, Connected sources, flip Meet transcripts off. Sonar removes the Meet permission from what it uses and stops reading transcripts at once; Google Calendar stays connected. The permission on Google's side remains until you disconnect Google entirely or remove Sonar on your Google Account's permissions page.

Flipping Google Calendar off removes both: Sonar revokes its token with Google and deletes it along with the receipts. Moments already mined stay yours to keep or delete in Settings, Intelligence, Moments, singly, by source or all at once, or under a retention rule of 30 days, 90 days or a year.

06

Data handling

Transcript text is processed in memory and discarded after the extraction pass; it is never stored. It is sent transiently to the AI provider that mines it and not retained for training under its API terms. What stays is the moments (a title, an angle, one line of detail, the call's title as provenance) and the row's receipt. Tokens are server side only and encrypted at rest.

Data from Google Workspace APIs is never used, transferred or sold to create, train or improve any model, and never shared with other users.

The full account is the privacy policy; the terms of service cover the account itself.

07

Support

Questions or trouble connecting? Email hello@meetdistilled.com. Hours and the first-reply time are on the support page.

One switch, and your week starts writing.

Every guide is one page away on Docs. Next to this one: the Google Calendar guide and the Zoom guide. What Google Meet reads, keeps and never keeps, in full, is the Google Meet integration page.