Google Calendar

Staff can push a provider's appointments into that provider's own Google Calendar. Calbok does not read busy time from Google, and it does not ship a Google Cloud project. You create the OAuth client; every business on this install authorizes against it.

  1. In Google Cloud Console, create a project and an OAuth consent screen with user type External. Add the scope https://www.googleapis.com/auth/calendar.events only. Do not add the full Calendar scope.

  2. Create an OAuth client of type Web application.

  3. Register this exact redirect URI (copy it from Admin → Google Calendar; it is {APP_URL}/oauth/google/calendar/callback):

    https://your-domain.com/oauth/google/calendar/callback

  4. Paste the client id and client secret into Admin → Google Calendar. The secret field is write-only: leave it blank on a later save to keep the secret already stored. Optional .env seeds (GOOGLE_CALENDAR_CLIENT_ID / GOOGLE_CALENDAR_CLIENT_SECRET) apply only until you save the panel.

  5. Staff connect each provider from Calendar Settings. Appointments are written to that Google account's primary calendar. Disconnecting removes the stored tokens and leaves the events already on Google.

Until Google verifies the app, staff see an unverified-app screen and the client is capped at 100 users. That interstitial is expected for a buyer-owned sensitive scope. The install never ships a Calbok client id.