SocialMati
GoogleOAuth 2.0 (Google)Pricing verified 2026-10-06

Google Calendar

Book demos and sales calls on salespeople's calendars, check free/busy for the public booking page, and create Meet links.

AProvider definition

Provider
Google Calendar
What it does
Book demos and sales calls on salespeople's calendars, check free/busy for the public booking page, and create Meet links.
Why we need it
Book demos and sales calls on salespeople's calendars, check free/busy for the public booking page, and create Meet links.
Used in
CRM booking page · AI Calling (appointment booking) · Workflows (book appointment)

BAccount requirements

Account type
Google account (Gmail or Google Workspace)
Prerequisites
  • Google OAuth client
  • Google Calendar API enabled

CConnection method

Authentication
OAuth 2.0 (Google)
Credentials
Uses the Google OAuth client (Google Cloud Console) credentials — no separate key.
Where to enter it
  • Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
  • Each salesperson: App → CRM → CRM settings → Calendar & bookingEvery salesperson connects their own calendar.

Setup steps

  1. 1Enable “Google Calendar API” in the Cloud project; add the calendar scopes below to the consent screen.
  2. 2Add the Google Calendar redirect URI (listed under Google Cloud Console) to the OAuth client.
  3. 3Each salesperson: CRM → CRM settings → Calendar & booking → Connect Google Calendar.

DPermissions & API scopes

Scope / permissionWhy it's neededRequested by
openidIdentify the account.Calendar booking
emailShow which calendar is connected.Calendar booking
https://www.googleapis.com/auth/calendar.eventsCreate, update and cancel the meetings the app books (with Meet links).Calendar booking
https://www.googleapis.com/auth/calendar.freebusyCheck availability without reading event details.Calendar booking

This list is generated from the scopes the application's code requests.

EFree vs paid

Free account / free API access
Yes.
Card or billing account required?
No.
Paid plan / costs
None.
Quota and usage limits
Per-project and per-user request quotas.
Checked against official/current sources on 2026-10-06. Provider pricing changes often — re-check before publishing.

FSetup screenshots

Capture each step with real values masked. Save images as public/docs/integrations/google_calendar/1.png … 10.png and they appear here automatically.

  1. Screenshot to add
    1. Account login / creation
    The provider's sign-in or sign-up page.
  2. Screenshot to add
    2. Developer console
    The developer console or dashboard home.
  3. Screenshot to add
    3. Project / app creation
    Creating the app or project used for this integration.
  4. Screenshot to add
    4. API enablement
    The API or product enabled for the project.
  5. Screenshot to add
    5. OAuth configuration
    Consent screen / OAuth settings with the redirect URIs.
  6. Screenshot to add
    6. API key / credentials creation
    Creating the key, secret or token (mask the value).
  7. Screenshot to add
    7. Permissions / scopes
    The scopes or permissions requested or approved.
  8. Screenshot to add
    8. Billing / quota settings
    Billing, credits or quota page.
  9. Screenshot to add
    9. Application connection
    The provider card in our application with fields filled (secrets masked).
  10. Screenshot to add
    10. Successful connection
    The green Test result or the connected account listed.

GApplication configuration

Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.

Nothing to enter for this product — it uses the Google OAuth client (Google Cloud Console) credentials. Connect it from the location in section C.

HTesting

  1. 1Connect a calendar, open the public booking page and book a slot — the event appears in Google Calendar with a Meet link.

ITroubleshooting

ProblemWhat to do
Slots show as unavailableCheck the working hours in CRM settings and that free/busy is readable.
insufficientPermissionsReconnect and accept both calendar permissions.
Invalid credentialsCheck the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure.
Missing permissionsReconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved).
OAuth failureSign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app.
Redirect URI mismatchCopy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings.
API not enabledEnable the API/product for the project or app in the provider console and wait a few minutes.
Quota exceededWait for the quota window to reset (see section E) or request a higher quota / add credits.
Account not eligibleCheck the account requirements in section B (e.g. business/professional account, verified property, registered organisation).
App review requiredPermissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions.
Billing requiredAdd a payment method or prepaid credits on the provider account (see section E).

JDisconnect & security

Revoke access at the provider
Google account → Third-party apps → remove; or disconnect in CRM settings.
Disconnect in the application
App → Integrations → Providers & API keys or App → CRM → CRM settings → Calendar & booking → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
Rotate credentials
Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
How credentials are stored
Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
What data the application can access
Free/busy times and the events the app creates. Other event details are not read.

Other Google providers

Start Free