Skip to main content

Zoom

Most architectural decisions are not made in writing. They are made in a meeting, and the only artefact is a recording nobody re-watches. Zoom is the connector that closes that gap.

Off by default

Zoom is fully built and shipped as a container image, but connectors.zoom.enabled is false in the chart's default values. On Align Cloud, ask us to enable it. Self-hosting, set the flag - see Configuration.

What it does​

  • Post-meeting transcript analysis - when a cloud recording finishes and its transcript is ready, Align analyses it for decisions
  • Discover - scan past recorded meetings for decisions already made
  • Evidence linking - each decision keeps a link back to the meeting and the moment in the transcript

How Zoom differs from every other connector​

There is no @align and no /align in Zoom. Capture is transcript-driven: you record the meeting, Align reads the transcript, and by default it saves each decision it finds as a remark. A remark is shown to agents marked as unconfirmed, and it does not fail a check until a person ratifies it. An org admin can switch the workspace to propose mode instead (PUT /tenant/meeting-capture-settings). Then each decision waits as a suggestion, and nothing enters the graph until a person approves it.

That makes Zoom the one connector where the trigger is "you already recorded this meeting" rather than "somebody typed a command". It is also why it is the highest-yield source for teams whose real decisions happen on calls.

Zoom Team Chat is not supported for real-time capture. Zoom does not emit message events to apps for Team Chat, so there is no chat capture and no chat reactions - only meetings.

You can still ask the Align bot a question in Team Chat, by slash command or @mention. It answers from your decision graph and keeps the last few turns of that chat for follow-up questions. It does not capture decisions from chat. That history lives in the connector pod, so a restart clears it.

Setup​

  1. Settings → Integrations → Connect next to Zoom
  2. Authorise the Align app on your Zoom account
  3. Confirm cloud recording and audio transcript are enabled in your Zoom account settings

Cloud recording with transcription must be on. Align cannot transcribe audio itself, and a local recording never reaches Zoom's API.

OAuth scopes​

ScopeWhy
cloud_recording:read:list_user_recordings:adminFind recordings to analyse
cloud_recording:read:list_recording_files:adminLocate the transcript file for a recording
cloud_recording:read:meeting_transcript:adminRead the transcript text

All three are read scopes. All three carry Zoom's :admin suffix, which means account level: the grant permits reading cloud recordings and transcripts for any user in the account, and an account admin has to authorise it.

Align's code is narrower than the grant. It lists recordings only for the authorising user (/users/me/recordings), reads that user's own profile (/users/me), and fetches a single meeting's recording (/meetings/{meetingId}/recordings) only when Zoom's recording-completed webhook announces that meeting. The grant is still broader than the use. If your review needs it narrowed to match, tell us and we will pursue Zoom's user-level scope variants.

Align does not start, join, record or post to meetings.

Retention​

Transcripts fetched during a Discover scan are held in the import batch while the job runs and purged with the job. The decision that comes out of a transcript keeps a link and a short quoted rationale, not the full transcript. See Data Retention for the exact fields and windows.

Evidence captured​

  • Meeting link and topic
  • Meeting date and duration
  • Participants
  • The transcript excerpt the decision was drawn from

Next steps​