Google Meet transcript to LinkedIn post, from what was said.

• Reads

  • Your own Meet calls from the last seven days that have a transcript, up to five. A call without transcription on has nothing to read and is skipped.
  • For each one: the transcript's lines with their speakers, and the call's title from your calendar (or its day and time when there was no calendar event). The first 6,000 characters of each transcript.
  • Through one permission, meetings.space.readonly, using Google's Meet API. Google verified the scope in August 2026, together with the calendar scope.
  • The participant list, only to put a name on each line so your words can be told from everyone else's.

• Does not read

  • Your Google Drive. Nothing in the connection touches Drive, which is where Meet keeps recordings.
  • The recording, video or audio. The Meet API hands over transcript text, and that is all Sonar asks for.
  • Anything older than seven days, or a call you were not in.
  • It never creates, joins or changes a meeting. The scope is read-only, on your own conference records.

• Keeps

  • The moments it mined: a title, an angle, one line of detail, and the call they came from, shown as "Meet: <title>".
  • A receipt of the read on the Meet transcripts row in Connected sources: how many transcripts, which calls, and how many moments came out.
  • The Meet scope on your Google connection's record, which is the switch itself. No second token: Meet rides the calendar's.

• Never keeps

  • The transcript text. The week's transcripts are assembled into one transient block, mined in a single pass, and discarded.
  • The participants. Their names ride the transcript into the read as speaker labels and leave with it.
  • Any moment past the retention you set, if you set one: 30 days, 90 days or a year.

1. 01

   In your Meet transcripts

   Hiring debrief

   Thursday · title from your calendar · transcription was on

   Our recruiter: all three finalists asked the same question. Who actually owns the roadmap.

   You: then the answer should be in the job description, and it is not.

   Only calls where transcription was on have a transcript to read. Each line arrives with its speaker, which is how Sonar can tell your words from everyone else's.

2. 02

   The moment Sonar keeps

   Lesson · Meet: Hiring debrief

   Every finalist asked who owns the roadmap

   Angle: the question candidates keep asking is the gap in the job description, and it costs the best ones.

   One pass over the week's transcripts, then the text is discarded. What stays is a title, an angle, one line of detail and the meeting it came from, with the people in it written as roles.

3. 03

   The draft, waiting

   LinkedIn draft · in your voice

   Three finalists, one question, and no answer in the job description.
   
   Who owns the roadmap? We had not written it down because we had not decided. The candidates found the gap before we did.

   The freshest moments are dealt into your weekly deck as drafts; keep one and it lands on your board. Every moment is also one tap from a draft on Home.

Invented for this page. Look at what is not in it: the recruiter's name, or any candidate's. The meeting title stays in Sonar as the moment's provenance, for your eyes only; the moment and the post say "our recruiter". That is the people rule, and it holds for every source, not only this one.

1. 01

   Connect Google Calendar first

   Meet transcripts ride the Google Calendar connection. In Settings, Connected sources, flip the Google Calendar switch and choose Allow on Google's consent screen: one read-only scope, calendar.events.readonly.

2. 02

   Turn transcription on in your calls

   Meet writes a transcript only for calls where transcription was switched on, by you or by your Workspace settings. A call without one is skipped; the row's receipt lists the calls that were read.

3. 03

   Flip the Meet transcripts switch

   Under the Google Calendar row, flip Meet transcripts on. Google asks for one more read-only permission, meetings.space.readonly, added to the grant you already gave. Choose Allow.

4. 04

   Let the first read run

   You land back in Sonar and the first Meet read starts on its own, alongside the calendar's. Moments appear on Home shortly after, each labelled with the call it came from, and the row's receipt lists the transcripts read.

5. 05

   Keep a draft

   The freshest moments are dealt into your weekly deck as drafts in your voice, and every moment on Home is one tap from a draft. Keep one and it lands on your board; schedule it or copy it.

6. 06

   Run it yourself any time

   About once a week is the cadence, and Meet syncs together with the calendar. The Sync all button at the top of Connected sources runs every connected source now.

Turning Meet transcripts off is the same switch. Sonar removes the Meet scope from its record and stops reading at once; the permission itself stays on your Google account until you disconnect Google entirely, which revokes the token, or remove Sonar on your Google account's permissions page. The choice is durable: reconnecting the calendar later never turns Meet back on by itself. Moments already mined stay yours to keep or delete in Settings, Intelligence, Moments. Recorded calls on Zoom have their own page. The step-by-step guide is Using Sonar with Google Meet.