Integrations
CallScribe for Zoom
Pull Zoom Cloud Recordings into CallScribe automatically — Arabic transcription on the calls Zoom's built-in transcript misses.
Last updated: April 2026
Zoom's built-in audio transcript is English-first. On Arabic calls, especially in dialect, it produces output ranging from rough to unusable. CallScribe replaces that pipeline for Arabic content: Zoom records, our integration pulls the recording via the Cloud Recording API as soon as it's ready, and a dialect-aware Arabic transcript appears in your CallScribe dashboard. It uses the same OAuth scopes any Zoom Marketplace app does.
How the integration works
You install CallScribe from your Zoom account (Marketplace app) and authorise the OAuth scopes recording:read:admin and recording:write:admin (write for tagging, read for fetching). When a Zoom meeting ends and cloud-recording processing completes, Zoom fires a recording.completed webhook to CallScribe. We GET the audio_only file via the recording API, push it through our Arabic ASR pipeline, and post the transcript back into a CallScribe project tied to the Zoom user.
No agent-side software runs. The Zoom user does not change their workflow. The transcript is available in CallScribe within minutes of meeting-end, with diarization, sentiment, and Arabic dialect attribution.
OAuth scopes and admin install
CallScribe's Zoom app requests recording:read:admin (to fetch any recording in the account, scoped to the connected workspace), webhook:write:admin (to register the recording.completed handler), and user:read:admin (to map Zoom users to CallScribe users). These are admin-managed scopes — your Zoom administrator authorises them once and individual users do not need to do anything.
For organisations with strict scope policies, a per-user install (user-level scopes) is also available; coverage is limited to that user's own recordings rather than the whole account.
Recording retention and CallScribe storage
Zoom's default cloud-recording retention is 30 days for paid plans (configurable). CallScribe pulls a copy as soon as the recording is available — so even if your Zoom retention is short, your transcript and the analytics derived from it persist on CallScribe at your project's configured retention setting. We do not, by default, copy the original audio to our storage; we transcribe it and discard our temp copy. If you need original-audio retention beyond Zoom's window, configure that explicitly.
Filtering: which calls actually go through CallScribe
Most organisations don't want every Zoom call transcribed — internal stand-ups in English, for example, are noise. CallScribe filters by Zoom user, by meeting-naming convention ("[Customer]" tag in title), or by external-participant presence (any meeting with at least one external participant). The webhook handler decides; non-matching meetings are ignored.
Arabic accuracy on Zoom audio
Zoom cloud-recording audio is 16kHz wideband — better than telephony-grade 8kHz. WER on clean two-party Zoom calls in Khaleeji or Levantine is typically 8-12%, with Egyptian sitting at 10-13%. Multi-party Zoom calls (5+ active speakers) see WER rise 3-5 percentage points due to overlap; diarization handles up to 8 speakers reliably.
Pricing under the hood
Zoom integration adds no extra fee — minutes consumed for transcription draw from your CallScribe plan minutes (Business 500/mo, Scale 3,000/mo). The Zoom-side cost is your Zoom plan, unchanged. For organisations that record every meeting, the volume math works out: a 50-person team averaging 30 hours of Zoom meetings each per month with 30% Arabic content fits comfortably within Scale.
At a glance
- ✓OAuth-scoped Marketplace app
- ✓Webhook-driven — no agent-side software
- ✓Filter by user, meeting name, or external-participant presence
- ✓Wideband audio yields 8-12% WER on Khaleeji
- ✓No extra fees beyond CallScribe plan minutes
FAQs
Do I need a Zoom paid plan?▾
Yes — cloud recording requires a Zoom Pro or higher plan. Free Zoom plans only support local recording, which CallScribe cannot ingest automatically. If your organisation uses local recording, upload files to CallScribe directly rather than via the Zoom integration.
How do I install the CallScribe Zoom app?▾
CallScribe is currently in private beta on the Zoom Marketplace. Existing CallScribe customers receive an admin install link from sales@callscribe.ae. General-availability listing is on the roadmap — joining the beta is a 10-minute Zoom-admin OAuth flow.
Does CallScribe transcribe video or just audio from Zoom?▾
Audio only. Zoom's recording.completed event includes both audio_only and shared_screen_with_speaker_view files; we pull the audio_only M4A. Visual content (slides, screen-shares) is not analysed.
What about Zoom Phone calls?▾
Zoom Phone (the cloud-PBX product) recordings are accessible via a separate API endpoint and a separate OAuth scope (phone_recording:read:admin). CallScribe supports Zoom Phone in the same way as Zoom Meetings recordings; treat the integration as the same product with two recording sources.
Can we push Zoom recordings to CallScribe via SFTP instead?▾
Yes — if you prefer not to install the marketplace app, you can configure your Zoom workspace to dump recordings to SFTP, point CallScribe at that endpoint, and we ingest from there. The integration features (filtering by participant, etc.) are not available in the SFTP path; everything dropped is transcribed.
How does Zoom handle our Arabic content vs. CallScribe?▾
Zoom's in-product transcript service uses primarily English models with limited Arabic support. For Arabic content — especially dialect content — accuracy is materially lower than CallScribe's purpose-built Arabic ASR. Many CallScribe customers disable Zoom's built-in transcript for Arabic users to avoid confusion.
5 min/mo free · No credit card · 8-12% WER on Khaleeji