Meetings

This article covers the configuration needed for Capacity's Conversation Intelligence (CI) platform to ingest your Zoom Workplace Meetings cloud recordings 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 meeting cloud recordings and metadata directly from Zoom via API
  • Secure, credential-based access using OAuth 2.0 Server-to-Server client credentials — Capacity never has access to your Zoom login
  • Batch retrieval of meeting 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 other Zoom products).
  • Confirm cloud recording is enabled for the users/groups whose meetings you want ingested — meetings must be set to record to the cloud, not local storage, for CI to retrieve anything.

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
meeting:read:list_meetings:admin
View a user's meetings
meeting:read:participant:admin
View a meeting's participant
meeting:read:chat_message:admin
View a meeting's chat message
meeting:read:meeting:admin
View a meeting
device:read:list_groups:admin
List groups

What to Share with Capacity

ItemDescription
Account IDAccount 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?