Outbound, every appointment is created, patched or deleted in their Google calendar and tagged so we recognise our own events coming back. Inbound, everything else on their calendar is pulled in as a busy block carrying no automations — no confirmations, no SOP ticks, no journey updates. If they move or delete one of our events in Google, the platform appointment follows.
Also called: connect Google Calendar · sync my calendar · my personal events block bookings · Google Meet link
- 1Scopes cover event read/write plus the list of their calendars, so personal blocks come from all of them, not just the primary one.
- 2Google sends no invites — the platform owns the emails.
- 3Sync is incremental by sync token, falling back to a windowed pull from 30 days back to 120 ahead when the token goes stale.
- 4Tokens are stored encrypted; disconnecting revokes them, removes the pulled personal events and leaves our own bookings in place.
- 5The connection card shows the linked address, minutes since last sync, and any error verbatim with a hint when the API is simply not enabled.
Migration 244 and the sync library are. The one-way-automations rule is explicit: pulled events carry 'no automations (no confirmations, no SOP tick, no Journeys light)' — a personal dentist appointment must block time without triggering a sales sequence. The push happens before the confirmation emails so 'the Google Meet link it creates is in the confirmation emails', and it never blocks the booking.
- Double-booking against personal commitments
- Two calendars to maintain
- Missing video links
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →