Connection
- Authentication: OAuth 2.0 — you authorize Atako via Zoom’s consent screen; no key to copy.
Nothing to paste: click Connect and approve Atako in your Zoom account. Prerequisite on the Atako side — an administrator opens the Zoom App Marketplace (https://marketplace.zoom.us) → Develop → Build App → General App, and chooses “User-managed” as the management type. In Basic Information copy the Client ID and Client Secret into INTEGRATION_OAUTH_ZOOM_CLIENT_ID / _CLIENT_SECRET, and under OAuth Information set the OAuth Redirect URL (and the OAuth Allow List) to ${API_URL}/integrations/oauth/callback. In Scopes → Add Scopes, add: user:read:user, meeting:read:list_meetings, meeting:read:meeting, meeting:read:invitation, meeting:read:list_registrants, meeting:read:past_meeting, meeting:read:list_past_participants, cloud_recording:read:list_user_recordings, cloud_recording:read:list_recording_files, meeting:write:meeting, meeting:update:meeting, meeting:write:registrant, meeting:update:status. Until the app is published on the Marketplace (Zoom review), only the developer’s own Zoom account can authorize it. Registrants, past-meeting participants and cloud recordings need a paid Zoom plan on the host.See Zoom’s documentation.
Read actions (9)
Write actions (4)
Permissions
Every action above must be explicitly granted to an agent before it can be used. See Permissions for the grant model and Security for how credentials are protected.Last reviewed against the provider API: September 2026.