Google Meet

Google Meet stores the meeting record most customer-facing teams forget to use. Transcripts, recordings, participant lists, conference metadata — all sitting in Meet, all queryable through the Meet REST API. The integration treats those records as a live source so summaries, follow-ups, and CRM updates can land automatically instead of waiting for someone to copy notes into the right place.

What you can do

• Pull a transcript into a chat — "summarize the discovery call with Acme yesterday" returns a structured summary built from the actual transcript, not from someone's notes.
• Trigger follow-ups from a meeting — a function reads the transcript, extracts action items, and posts them to the right Linear project or Asana board.
• Customer-record enrichment — when a Meet call with a tracked customer wraps, the recap and action items write to the contact record in HubSpot or Salesforce.
• Cross-meeting search — find every conversation that mentioned a specific competitor, product, or commitment across customer-facing calls.
• Recording access — for the rare cases when the transcript isn't enough, pull the recording itself for deeper review.
• Participant context — who was on the call, when they joined, who hosted — useful for attribution and follow-up routing.

How to connect

Google Workspace service account with domain-wide delegation (DWD), same model as Gmail. Your Workspace admin grants the service account the Meet API scopes, and the integration impersonates user accounts to access their meeting records.

Setup (admin, one-time):

1. Enable the Meet REST API and Workspace Events API in your GCP project.
2. Create a service account, generate a JSON key, paste into the integration.
3. Enable DWD on the service account and note the Client ID.
4. In Workspace Admin → Security → API controls → Domain-wide Delegation, add the Client ID with scopes:
   • meetings.space.readonly — meeting and transcript access
   • drive.readonly — required because Meet recordings live in the user's Drive (Meet API returns Drive file IDs, not bytes)
5. Impersonation target must have a valid Workspace license and have hosted at least one Meet for recordings to surface.

Connect Google Meet in myai

Common use cases

• Auto-CRM-updates after customer calls — Meet wraps, function fires, recap and action items land on the contact record in HubSpot or Salesforce.
• Sales-call quality coaching — manager pulls all calls from the last week, surfaces objection patterns or talk-time imbalances.
• Cross-team handoffs — engineering reads the AE's last discovery call before the kickoff so context isn't re-litigated in the first meeting.

Reference

• Connection model: Google Workspace service account with DWD
• Scopes: meetings.space.readonly, drive.readonly
• Transcripts require Workspace edition that enables them (Business Standard+); recordings require the user to have hosted the call