Google Calendar Integration — Per-User OAuth & Meeting Sync | LlamaPress Cookbook
LlamaPress
Sign in Upload
Cookbook
Integrations Stable

Google Calendar Integration — Per-User OAuth & Meeting Sync

Let each signed-in user connect their own Google Calendar with OAuth (offline access + refresh tokens), sync their upcoming events into a local table with a zero-gem Net::HTTP background job, extract the Meet/Zoom/Teams join link, and render an "Upcoming meetings" widget — including token refresh, revoked-token recovery, and keeping moved meetings up to date.

Proven on rails-crm.llamapress.ai model · sql · controller · view
JSON Raw .md

Related

Cookbook Google Search Console — OAuth Client, Callback URI & Pulling Query Data Sibling recipe — the same Google Cloud OAuth web-client setup and zero-gem Net::HTTP pattern, but app-level (one refresh token in .env) instead of per-user. Cookbook Recall.ai Meeting Transcription Natural next step — once you know a user's meeting URLs, a bot can join and transcribe them. Link Google Calendar API — Events.list reference Official docs for the events.list endpoint used by the sync job — parameters, paging, sync tokens. Link Google Identity — OAuth 2.0 for Web Server Applications Google's own walkthrough of the authorization-code flow, offline access, and refresh tokens.