@devries-cameron20 / composio Mirror · read-only
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

next
md 32 lines 1.93 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "Zoom"
4 description: "Public support knowledge for Zoom."
5 category: "auth-config"
6 visibility: "public"
7 timestamp: "2026-06-24T00:00:00Z"
8 tags:
9 - "zoom"
10 ---
11 # Zoom
12
13
14 ## Zoom custom OAuth apps may only connect users in the app owner's Zoom organization unless configured/approved otherwise
15
16 If a customer is using their own Zoom OAuth app, verify whether the users they are connecting belong to the same Zoom organization or whether the app is published/approved for external users. An unpublished internal app may only connect users from its own Zoom organization.
17
18 ## Zoom should use the default Composio redirect URL unless the auth guide says otherwise
19
20 For Zoom OAuth setup, do not arbitrarily change the redirect URL. Use the default redirect URL/callback shown by Composio or the Zoom auth guide. If auth fails after redirect changes, recreate or update the auth config with the default redirect URL.
21
22 ## `ZOOM_GET_A_MEETING_SUMMARY` needs the correct past-meeting UUID and auto summary enabled
23
24 For Zoom meeting summaries, verify that the meeting was created with `settings__auto_start_meeting_summary=true`. Then fetch the correct past-meeting UUID from Zoom's `/v2/past_meetings/{meetingId}/instances` endpoint and use that UUID with `ZOOM_GET_A_MEETING_SUMMARY`; the numeric meeting ID alone may not be sufficient.
25
26 ## Zoom delete/summary tools may require extra scopes in a custom OAuth app
27
28 If a Zoom tool fails with a scope or permission issue, check whether the required scope is configured on the customer's Zoom OAuth app. `ZOOM_DELETE_A_MEETING` needs `meeting:write` or `meeting:write:admin`, while fetching past meeting instances or summary UUIDs needs `meeting:read:list_past_instances`.
29
30 ## Zoom OAuth consent branding comes from the customer's OAuth app
31
32 For Zoom OAuth branding, use the customer's own Zoom OAuth app. The OAuth consent screen logo/name is picked up from the OAuth app settings rather than from Composio alone.