What connects

Zoom Recordings uses a user-managed Zoom OAuth app for historical cloud-recording access. Zoom Live is a separate signed RTMS lifecycle/WebSocket path; connecting the recordings path alone does not guarantee live RTMS.

An IntellaOne administrator configures the server-side Zoom app credentials, OAuth callback, webhook Secret Token, and cloud recording list, past participant, and meeting transcript scopes.
The customer Zoom administrator or connected user approves the OAuth request and grants the account's recording, participant, and transcript access.
RTMS also needs the Zoom host or administrator to enable or auto-start RTMS for eligible meetings, Zoom Developer Pack credits, and participant consent controls.
IntellaOne does not start or control Zoom meetings. Browser microphone capture remains an explicit fallback when RTMS is unavailable.

Information used

The recordings path imports historical cloud recordings in incremental windows. The first run looks back 90 days, then processes windows of no more than 30 days and resumes from a completed watermark.

Recording meeting metadata, timing, duration, host/attendee information when a participant report exists, and the provider share URL.
A recording transcript file where Zoom provides one; missing transcript files and missing participant reports are normal provider outcomes.
Participant and transcript backlogs are each bounded at 200 items per run and continue on later runs.
The live RTMS path emits final transcript segments and signed start/stop lifecycle state; it is not a historical recording importer.

Why it is useful

Historical recordings and available transcripts provide prior-conversation context for teams without a separate conversation-intelligence platform. RTMS can provide no-bot live transcript guidance when the Zoom account and meeting lifecycle are configured for it.

How the workflow behaves

Zoom Recordings runs as a scheduled historical sync; it is not real-time. Zoom Live begins only after the signed RTMS lifecycle route receives a start event and ends on the corresponding stop lifecycle.

Recording downloads and attendee reports are separate provider calls, so one may be available when the other is not.
RTMS emits transcript callbacks and lifecycle state rather than storing a raw live audio/video recording.
This integration has no outbound Zoom actions and does not start, stop, or control meetings.

Prerequisites and limits

Before connecting, an IntellaOne administrator must configure the server-side Zoom OAuth app, callback, webhook Secret Token, client credentials, and required scopes. The customer Zoom administrator or connected user must then authorize the OAuth request and grant recording, participant, and transcript access. Recordings additionally require a paid Zoom plan with cloud recordings; live RTMS separately requires signed webhook events, host/admin RTMS enablement, Developer Pack credits, and participant consent behavior.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Security and privacy boundaries

Newly saved connector credentials are encrypted before storage.

Connected tools sync server-side under the user's own credentials. Requested permissions and data flows are connector-specific.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

RTMS raw live audio and video are not stored by IntellaOne; only transcript callbacks and lifecycle state are used by the live path. Historical recordings remain provider cloud-recording data, and transcript or attendee availability is not guaranteed for every meeting.

Zoom Recordings and Zoom (Live) are separate catalog capabilities with separate setup requirements.
Participant consent and the Zoom account's recording/transcript permissions still govern what can be imported or streamed.