Google Calendar
Google Calendar to LinkedIn posts, in your voice.
Turn your Google Calendar into LinkedIn posts: connect it once, read-only. About once a week Sonar reads the last seven days of meetings on your primary calendar, asks you what came of the ones worth a story, and drafts LinkedIn and X posts in your voice from the answers. Nothing publishes without your approval.
What Sonar reads
One scope, one call, seven days.
The permission is calendar.events.readonly and nothing else. Here is exactly what passes through it, what stays, and what never does.
Reads
- Events on your primary calendar from the last seven days, up to 60.
- Only meetings: two or more people who did not decline. Solo blocks and all-day entries are skipped.
- For each one: the day, the title, the attendees' names, and the first 200 characters of the description.
- Through one permission, calendar.events.readonly, verified by Google.
Does not read
- Any other calendar on your account, or the list of your calendars.
- Anything older than seven days.
- Attachments, or your email.
- It never creates, changes or deletes an event. Meet transcripts are a separate switch with a separate scope.
Keeps
- The moments it mined: a title, an angle, one line of detail, and the meeting title they came from.
- Two or three debrief questions, until you answer or dismiss them.
- A receipt of the read on the row in Connected sources: how many meetings, and the titles of up to five.
- A refresh token, so next week's read runs without asking you again.
Never keeps
- The event text. The week is assembled into one transient block, mined in a single pass, and discarded.
- The attendee list. It rides the week's text into the read so a 1:1 can be told from a team review, and leaves with it. A moment names a role, never a person.
- Any moment past the retention you set, if you set one: 30 days, 90 days or a year.
From a calendar to a post
A meeting title is where a story happened.
The calendar knows that a meeting took place, not what came of it. So Sonar asks. An invented week, run the way yours would be.
01
On your calendar
Pricing review
Tuesday, 10:00 to 10:45 · 4 attendees
Read as one line: the day, the title, who was there, the first 200 characters of the description.
Only meetings with people count. A focus block, a reminder or an all-day entry never enters the read.
02
Sonar asks
Sonar asks · Home
What got decided in Tuesday's pricing review?
You, one line: we stopped discounting to close. Held list price, lost one deal, kept the margin on the other four.
Each read leaves two or three questions on Home, each naming the real event and day. A line back is enough.
03
The moment, then the draft
Decision · Calendar: Pricing review
We stopped discounting to close
Angle: what holding list price cost us in a week, and what it bought.
The draft opens: We lost a deal last week on purpose. Four others closed at list price, and I am still thinking about the one that walked.
Your answer becomes a moment with an outcome in it. The freshest moments are dealt into your weekly deck as drafts in your voice; keep one and it lands on your board.
Invented for this page. Look at what is not in it: the client's name, or anyone else's. The meeting title stays in Sonar as provenance for your eyes only; the moment and the post say "a client". That is the people rule, and it holds for every source, not only this one.
Set it up
One switch, one permission.
- 01
Open Connected sources
Sign in at app.meetsonar.co and open Settings, Connected sources. New to Sonar? The Sources step at the end of onboarding is the same list.
- 02
Flip the Google Calendar switch
Google's consent screen asks for one permission, read-only access to your calendar events (calendar.events.readonly). Choose Allow.
- 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; the row's receipt shows how many meetings were read.
- 04
Answer when Sonar asks
Each week the 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.
- 05
Add Meet transcripts if you want the full story
The Meet transcripts row on the same Google connection adds one more read-only scope for the transcripts of your own calls, which the calendar alone cannot know.
- 06
Run it yourself any time
About once a week is the cadence. The Sync all button at the top of Connected sources runs every connected source now.
Turning it off is the same switch. Sonar revokes its token with Google and deletes it, along with the row's receipt. Moments already mined stay yours to keep or delete in Settings, Intelligence, Moments. Meet transcripts are a separate switch on the same connection, and Zoom recordings have their own guide.
FAQ
Questions about the calendar.
Your week already wrote your posts.
The calendar is the lightest ask and the fastest start. Every other source is one page away on Integrations, and the full account of what is read and kept is the privacy policy. Anything else, ask support.