Phone

This article covers the configuration needed for Capacity's Conversation Intelligence (CI) platform to ingest your Zoom Workplace Phone call recordings, call logs, and associated metadata. It assumes you've already created your Zoom Server-to-Server OAuth app — if not, start with the Zoom Authentication article first.


How It Works

  • Automated ingestion of call recordings and call logs directly from Zoom Phone via API — no file transfer step required
  • Secure, credential-based access using OAuth 2.0 Server-to-Server client credentials — Capacity never has access to your Zoom login
  • Batch retrieval of call recordings and metadata once configured

Before You Begin

  • Complete the Zoom Authentication article to create your Server-to-Server OAuth app (or confirm one already exists if you're also enabling Meetings or Contact Center).
  • Confirm call recording is enabled for the extensions/users whose calls you want ingested.

Required Scopes

Add the following scopes to your Server-to-Server OAuth app's Scopes tab — you don't need to create a second app if one already exists for another Zoom product:

ScopeDescription
phone:read:call_recording:adminView a call recording
phone:read:call_log:adminView a call log
phone:read:list_call_recordings:adminView call recordings
user:read:user:adminView a user, used to map agent identities
group:read:group:adminView a group
group:read:list_groups:adminView groups, used if only specific groups should be ingested

What to Share with Capacity

ItemDescription
Account ID
Account ID from the Server-to-Server OAuth app
Client IDClient ID from the same app
Client SecretClient Secret from the same app
Include GroupsLet us know if only specific groups should have their meetings ingested by sending a list of group names
If no list is provided, we will assume ingestion applies account-wide

Was this article helpful?