Zoom

Server-to-Server OAuth app for the Zoom API.

Field	Description	Required
Account ID	From your Server-to-Server OAuth app's App Credentials page in the Zoom App Marketplace.	Yes
Client ID	Generated when you create the Server-to-Server OAuth app.	Yes
Client Secret	Generated alongside the Client ID. Regenerating it in Zoom invalidates the old value.	Yes

Step 1: Sign in to the Zoom App Marketplace and choose Develop → Build App → Server-to-Server OAuth. You need the account owner/admin role (or a role with the Server-to-Server OAuth permission).
Step 2: Under Scopes, add the meeting scopes — meeting:read:meeting:admin, meeting:write:meeting:admin, meeting:update:meeting:admin, and meeting:delete:meeting:admin (older accounts show the classic meeting:read:admin / meeting:write:admin pair instead) — then Activate the app.
Step 3: On the app's App Credentials page, copy the Account ID, Client ID, and Client Secret.
Step 4: In Falcon Builder, go to Dashboard → Credentials → Add Credential, pick Zoom, and paste all three values.
Step 5: Click Test Connection. We mint an access token via the account_credentials grant to confirm all three values.

No redirect/consent flow is involved — access tokens are minted automatically per execution and never stored.
The app is account-level: it can act for any user in your Zoom account, which is why the Zoom node's Create and Get Many operations ask for a Host Email.
Zoom retired JWT apps in 2023 — Server-to-Server OAuth is their replacement for exactly this kind of backend integration.
Regenerating the Client Secret in Zoom invalidates the old value — update the credential if you regenerate.

Create, update, get, list, and delete Zoom meetings — including join links for scheduled calls.