1 min read
Sync provider calendars to Google Calendar so bookings show up alongside their other commitments and double-booking risk drops.
OAuth setup (one-time, site-wide) #
- Create a Google Cloud project at console.cloud.google.com.
- Enable the Google Calendar API.
- Configure an OAuth consent screen (External, with the domains you’ll authorize).
- Create OAuth credentials (Web application). Set the authorized redirect URI to your site’s
?bookaro_gcal_oauth_callback=1endpoint. - Paste the Client ID + Secret into Settings → Calendar → Google Calendar.
Per-provider connection #
Each provider clicks Connect Google Calendar in their dashboard, picks the calendar to sync to, and authorizes.
Sync direction #
One-way: MyBookaro → Google Calendar. Booking creates/updates/cancellations push to the provider’s chosen calendar. External calendar edits do not flow back.
Tokens and storage #
OAuth tokens are stored in user meta (bookaro_gcal_access_token, bookaro_gcal_refresh_token, bookaro_gcal_token_expiry, bookaro_gcal_calendar_id). Access tokens auto-refresh.
Diagnostics #
Settings → Calendar shows last sync attempt, last success, last error code/message, and scope hash. If scopes change in a future Pro release, providers see a “reconnect required” prompt.
Disconnect #
From the provider dashboard’s Calendar Sync panel. POST to /bookaro/v1/google-calendar/disconnect revokes tokens and clears the link.
