SocialMati
GoogleUses the Google Calendar OAuth connectionPricing verified 2026-10-06

Google Meet

Video-meeting links on booked demos and sales calls.

Meet links are created automatically on events booked through the Google Calendar connection (Calendar API conference data). There is no separate Meet credential or Meet API connection.

AProvider definition

Provider
Google Meet
What it does
Video-meeting links on booked demos and sales calls.
Why we need it
Video-meeting links on booked demos and sales calls.
Used in
CRM booking · AI Calling appointments

BAccount requirements

Account type
Google account whose calendar is connected
Prerequisites
  • Google Calendar connection

CConnection method

Authentication
Uses the Google Calendar OAuth connection
Credentials
Uses the Google OAuth client (Google Cloud Console) credentials — no separate key.
Where to enter it
  • Each salesperson: App → CRM → CRM settings → Calendar & bookingEvery salesperson connects their own calendar.

Setup steps

  1. 1Connect Google Calendar (see Google Calendar). Every booked meeting gets a Meet link automatically.

DPermissions & API scopes

Scope / permissionWhy it's neededRequested by
openidSign the user in with OpenID Connect.Calendar booking
emailShow which account 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 with a Google account; meeting length/participant limits depend on the Google plan.
Card or billing account required?
No.
Paid plan / costs
Google Workspace plans for longer meetings and recordings.
Quota and usage limits
Same as Google Calendar.
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_meet/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. 1Book a slot on the booking page — the confirmation and calendar event contain a Meet link.

ITroubleshooting

ProblemWhat to do
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
Disconnect Google Calendar.
Disconnect in the application
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
Only the meeting link attached to booked events.

Other Google providers

Start Free