Skip to main content
All integrations articles

Google Calendar — required for booking

Why the receptionist needs calendar access, what we read + write, and how to disconnect.

Updated 2026-04-29

The AI receptionist can't book real appointments without seeing your real schedule — otherwise she'd double-book or guess at availability. The Google Calendar integration gives her read access to your free/busy slots + write access to create events for new bookings.

What we access — and what we don't

  • Read: free/busy slots only. We don't read existing event titles, attendees, or content.
  • Write: NEW events only (the bookings the receptionist takes). We don't edit or delete existing events.
  • We never share calendar data with third parties — it's used only for the booking flow.

Setup

  1. 1
    Click Connect on /portal/integrations → Google Calendar

    Redirects to Google's OAuth consent screen.

  2. 2
    Pick the calendar account

    Personal Gmail OR Google Workspace works. Most contractors use a Workspace account so the bookings go to the same calendar the team uses.

  3. 3
    Approve the scopes

    Calendar.events read+write. That's the only scope we ask for.

  4. 4
    Done

    Receptionist starts booking onto the connected calendar immediately.

Disconnecting

Hit Disconnect on the integration card. We revoke the OAuth token at Google's end + delete our copy. Existing events on the calendar stay — disconnecting doesn't remove past bookings, only stops new ones.

Ready to try this in the actual product?

14-day free trial, no card charged for 14 days, cancel anytime.

More integrations articles