Using Sonar with Google Calendar.

Sonar turns your working week into content for LinkedIn and X. When you connect Google Calendar, Sonar reads the last seven days of events on your primary calendar, once when you connect and about once a week after that, and keeps only the meetings with people: two or more attendees who did not decline. Solo blocks, focus time and all-day entries never enter the read.

For each meeting it reads the day, the title, who was there and the first 200 characters of the description, up to 60 events. From that it mines up to three story-shaped moments (a decision, a win, a lesson) and writes two or three debrief questions that name the real event and day, because a calendar knows that a meeting happened and never what came of it. Your one-line answers become moments with an outcome in them.

The event text is never stored. The week is assembled into one transient block, mined in a single pass and discarded; what stays is the moments, the questions until you answer or dismiss them, and a receipt on the row in Settings saying how many meetings were read and the titles of up to five.

• A Sonar account (create one at app.meetsonar.co).
• A Google account with a primary calendar. A work account or a personal one both work.
• Nothing to install and nothing to configure at Google. The connection asks for one permission, read-only access to your calendar events (calendar.events.readonly), which Google verified in August 2026.

1. 01

   Open Connected sources

   Sign in at app.meetsonar.co and open Settings, Connected sources. On your first day the Connect your week row on Home opens the same list.

2. 02

   Flip the Google Calendar switch

   Google's consent screen asks for one permission, read-only access to your calendar events. Choose Allow.

3. 03

   Let the first read run

   You land back in Sonar and the first read starts on its own. Moments and the week's questions appear on Home shortly after, and the row's receipt shows how many meetings were read.

4. 04

   Answer when Sonar asks

   Each read leaves two or three questions on Home, under Sonar asks, each naming a real event and day. A line or two back becomes a moment with an outcome in it.

There is nothing to operate day to day. Sonar reads about once a week and after you connect; the Sync all button at the top of Connected sources runs every connected source now. The row shows when the last read happened, how many meetings it covered with the titles of up to five, and how many moments were kept.

Moments surface on Home and in the chat as material for drafts in your voice, and the freshest are dealt into your weekly deck already written. Each week the read also leaves two or three questions under Sonar asks on Home; answering them is what turns a meeting title into a story with an outcome.

Meet transcripts are a separate switch on the same Google connection, for what was actually said on the calls the calendar only knows happened. It adds one more read-only scope; the Google Meet guide covers it.

In Sonar: Settings, Connected sources, flip the Google Calendar switch off. Sonar revokes its token with Google and deletes it, along with the row's receipt. Nothing from your calendar can be read from that point on.

Moments already mined stay in your workspace because they are yours: delete any one, everything from the calendar, or all of them in Settings, Intelligence, Moments, or set a retention rule of 30 days, 90 days or a year and Sonar sweeps daily.

You can also remove Sonar from the Google side at any time, on your Google Account's permissions page. Turning Meet transcripts off is its own switch and leaves the calendar connected.

The refresh token that lets next week's read run without asking you again is stored server side only and never reaches the browser; the database is encrypted at rest and every request runs over TLS. Event text and the attendee list are processed in memory and discarded after the extraction pass. A moment names a role, a client or someone on my team, and the meeting title survives only as the moment's provenance label, which only you see.

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.

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