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
- 1Connect Google Calendar (see Google Calendar). Every booked meeting gets a Meet link automatically.
DPermissions & API scopes
| Scope / permission | Why it's needed | Requested by |
|---|---|---|
| openid | Sign the user in with OpenID Connect. | Calendar booking |
| Show which account is connected. | Calendar booking | |
| https://www.googleapis.com/auth/calendar.events | Create, update and cancel the meetings the app books (with Meet links). | Calendar booking |
| https://www.googleapis.com/auth/calendar.freebusy | Check 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.
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.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Screenshot to add3. Project / app creationCreating the app or project used for this integration.
- Screenshot to add4. API enablementThe API or product enabled for the project.
- Screenshot to add5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Screenshot to add7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe 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
- 1Book a slot on the booking page — the confirmation and calendar event contain a Meet link.
ITroubleshooting
| Problem | What to do |
|---|---|
| Invalid credentials | Check the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure. |
| Missing permissions | Reconnect 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 failure | Sign-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 mismatch | Copy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| App review required | Permissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions. |
| Billing required | Add 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.

