Integrations
CallScribe for Google Meet
Google Meet recordings stored in Drive — Arabic transcription via Workspace Admin SDK.
Last updated: April 2026
Google Workspace customers using Meet for video calls have access to Google's built-in transcript. For Arabic — especially Arabic dialect — that built-in transcript is unreliable. CallScribe pulls Meet recordings from Drive (where Workspace stores them by default), runs Arabic dialect-aware ASR, and produces transcripts with the analytics layer your operational team needs. The integration is Workspace-Admin-installed and OAuth-scoped to Drive read.
How the Google Meet integration works
CallScribe registers as a Google Workspace Marketplace app with OAuth scopes drive.readonly (read recording files), admin.reports.audit.readonly (subscribe to meet activity for completion events), and admin.directory.user.readonly (map Workspace users to CallScribe users). A Workspace Super Admin authorises domain-wide installation. From that point, CallScribe polls the Reports API for completed Meet recordings, fetches the MP4 from Drive, extracts audio, transcribes, and posts the transcript to the user's CallScribe project.
For organisations not yet ready for domain-wide install, an individual user can install CallScribe on their own account with user-level OAuth — limited to that user's own meeting recordings.
Workspace Marketplace install vs. SFTP fallback
The Marketplace install is the recommended path: domain-wide deployment, single-admin authorisation, automatic recording capture. For organisations whose security policy disallows third-party Workspace apps, CallScribe also supports an SFTP fallback — your Workspace exports recordings to an SFTP endpoint nightly, CallScribe polls and ingests. The Marketplace integration's real-time event stream is not available in SFTP mode; transcripts arrive on a daily lag.
Recording retention in Google Workspace
Google Workspace does not enforce a meeting-recording retention; recordings live in the organiser's Drive until manually deleted. Many organisations set Vault retention rules — for instance, retain Meet recordings 90 days then auto-delete. CallScribe pulls a copy at recording-creation time and persists transcripts (not original audio, by default) per its own retention rule. If you need to keep the original audio for compliance beyond your Workspace retention, configure CallScribe to keep original audio explicitly.
Filtering: which Meet calls actually transcribe
Internal stand-ups in English are usually noise for an Arabic-content analytics system. CallScribe filters by user (only customer-success or support reps), by meeting-title pattern, or by external-participant detection. Domain-tagging on Workspace lets us identify external participants reliably — meetings with no external participants are typically internal and skipped.
Arabic accuracy on Meet audio
Google Meet captures wideband audio (Opus codec, typically 16kHz). WER on clean two-party Meet calls in Khaleeji or Levantine is typically 9-13%; Egyptian audio sits at 10-14%. Multi-party Meet calls perform similarly to multi-party Zoom — overlap is the main accuracy hit. For sales-discovery calls and customer-success reviews — where external customers speak in dialect — CallScribe materially outperforms Meet's native transcript on Arabic.
Use-case fit
Google Workspace adopters skew toward tech-forward GCC firms — startups, fintechs, regional digital media. The Meet integration is most useful for sales-call analytics (pipeline coaching from real customer conversations), customer-success reviews (sentiment trajectory across the customer relationship), and external-stakeholder meetings where Arabic-language content needs structured search.
At a glance
- ✓Workspace Marketplace app with admin install
- ✓OAuth-scoped Drive read + Reports API event stream
- ✓SFTP fallback for security-strict tenants
- ✓External-participant filtering via domain-tagging
- ✓Materially better Arabic accuracy than Meet's built-in transcript
FAQs
Do I need a paid Google Workspace plan?▾
Yes — Google Meet recording is a paid-Workspace feature (Business Standard or above; Enterprise tiers; Education Plus). Free Google accounts and Workspace Business Starter cannot record meetings, so there is nothing for CallScribe to ingest.
Will Workspace admin consent be required?▾
Yes for domain-wide install (recommended for organisations) — a Super Admin authorises the OAuth scopes once. Per-user install does not require admin consent; the user authorises CallScribe for their own meetings.
How does CallScribe handle Meet captions vs. its own transcript?▾
Google Meet's in-meeting captions and recording transcript are produced by Google's ASR. CallScribe ignores them and produces its own transcript from the audio. We do not currently merge or compare against Google's captions.
Can CallScribe transcribe Meet calls without recording them?▾
No — CallScribe is post-hoc. We ingest existing recordings and transcribe them. We do not join meetings as a bot, we do not capture in-progress audio, and we do not currently offer a real-time transcript service for Meet.
How is the integration audited from Google Workspace side?▾
OAuth grants are visible to Workspace admins in the Marketplace settings and in the Admin Console's third-party app management. The Reports API and Drive API access by CallScribe is logged in Google's admin audit log; admin can revoke at any time.
What's the typical setup time for a 100-user Workspace organisation?▾
Under an hour. The admin OAuth grant is 5 minutes. Filtering rules and user mapping take 15-30 minutes. The first transcripts appear within an hour as recordings complete. Onboarding sales-call evidence and validating accuracy on your specific audio takes longer — typically a week.
5 min/mo free · No credit card · 8-12% WER on Khaleeji