Zoom

​

Common issues

• Verify Client ID and Client Secret are correct — no extra spaces
• Check that the OAuth app is still active in the Zoom Marketplace
• Regenerate the secret if necessary and update PipesHub

• The Redirect URL in PipesHub must match the OAuth Redirect URL saved in Zoom exactly — protocol, host, path, and trailing slash
• Also ensure the same URL is on the OAuth Allow List in Zoom

• If admin scopes are not shown when authorizing, the app was likely created as User-managed instead of Admin-managed. Delete the app and create a new Admin-managed one.
• Confirm all six scopes are added in the Scopes section of the app builder before authorizing.

• Only a Zoom admin can authorize an Admin-managed app. Sign out and sign back in as an admin, then retry Authenticate on the Authorize tab.

• Confirm the authorizing admin can see the account’s users (e.g., via Zoom Admin → User Management)
• If users show up but no meetings, check that Report API access is enabled for your plan — Report APIs require Pro or higher
• Initial sync only covers the last 180 days; older meetings are intentionally excluded

• Only AI Companion transcripts are indexed. Meetings without AI Companion enabled will not have a transcript.
• Verify cloud_recording:read:meeting_transcript:admin is granted
• If transcripts fail with Zoom error 3322, the meeting simply has no transcript — this is expected, not an error

• The Report API GET /v2/report/meetings/{id}/participants is a Heavy-rate endpoint (~10–20 req/s). For accounts with thousands of meetings, the initial 180-day backfill can take an hour or more.
• The connector processes meetings with a concurrency cap to stay under rate limits — this is intentional.

​

Sync overview

1. Fetch active users — GET /v2/users?status=active lists users in the account.
2. Create user groups — one USER_GROUP per host; permissions anchored to the host email.
3. Per-user meeting history — for each user, GET /v2/report/users/{userId}/meetings returns meetings in 30-day chunks, driven by a per-user checkpoint (zoom_report_last_sync/{user_id}).
4. Per-meeting enrichment — for each meeting:
   • GET /v2/meetings/{meetingId} — meeting detail
   • GET /v2/meetings/{meetingId}/recordings — recording share URL only (silently skipped if the meeting has no recording)
   • GET /v2/report/meetings/{meetingId}/participants — attendee list
   • GET /v2/meetings/{meetingId}/transcript — AI Companion transcript (if enabled)
5. Build permissions — host → Owner; alt-hosts / participants / invitees → Read.
6. Persist records — meeting records and permissions are written per chunk.

​

Full sync vs incremental sync

• First sync runs from max(user.created_at, today - 180 days) forward.
• Subsequent syncs start from the per-user checkpoint minus one day (safety overlap) and advance to today, in 30-day chunks.
• Lookback cap: 180 days. Older meetings are never synced.
• Chunk size: 30 days per API call (Zoom Report API constraint).

​

Rate-limit awareness

• GET /v2/report/meetings/{id}/participants is Zoom’s rate-limit bottleneck (Heavy-rate tier, ~10–20 req/s).
• The connector processes meetings with a concurrency cap to stay safely under the limit.
• Throttled responses trigger exponential backoff; long-running syncs will continue across scheduled intervals.

​

Transcripts

• Transcripts are not pre-cached — they are fetched live when the record is opened in PipesHub.
• Zoom error 3322 means the meeting has no transcript (expected for meetings without AI Companion).
• Zoom errors 3001/3301 mean the meeting/transcript expired — silently skipped.

• List all users in the account → user:read:list_users:admin
• Read meeting history per user via the Report API → report:read:user:admin
• Fetch meeting participants → report:read:list_meeting_participants:admin
• Meeting details and recording share URLs across the account → meeting:read:meeting:admin, cloud_recording:read:list_recording_files:admin, cloud_recording:read:meeting_transcript:admin