Brief meeting prep from Google Calendar
Connect Google Calendar read-only and prepare an evening brief for the next business day's external meetings.
The Google Calendar meeting prep brief template runs each evening before
a business day, reads one calendar for the next business day, and prepares a
short prep note per external meeting: the attendees and their organizations,
the stated agenda, previous meetings with the same people, and the open
questions worth asking, with the event cited behind each note. It follows the
sales-enablement marketing skill: walk in prepared, and keep the notes
factual rather than speculative.
Enable and connect Google Calendar
Google Calendar shares the Google Cloud OAuth client and Developer Preview
status described in
Digest source material from Google Drive;
an operator must configure GOOGLE_MCP_OAUTH_CLIENT_ID and
GOOGLE_MCP_OAUTH_CLIENT_SECRET before enabling
MANAGED_MCP_GOOGLE_CALENDAR_ENABLED. Then connect the Google Calendar card
and authorize with your own Google account. Work on Repeat requests only
https://www.googleapis.com/auth/calendar.events.readonly and
https://www.googleapis.com/auth/calendar.calendarlist.readonly, so the
connection cannot create, edit, accept, decline, or delete events or change
sharing.
Set the variable
| Key | Example | Why it is a variable |
|---|---|---|
calendarName | Sales calendar | The calendar to read varies per person, and it is also the routine's read boundary. |
Reference it in the instructions as {{calendarName}}.
Current beta boundary
Google Calendar is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. After review, the first manifest should stay with calendar-list and event reads; event creation, edits, and responses are mutations and must remain blocked or approval-gated. Attendee lists are personal data, so keep the brief inside the team that needs it.
Recovery
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.
The seven-day refresh-token expiry for a Google Cloud project still in Testing
applies here too.