Search all guides

Reference · Credentials

Connect Zoom to BusyBot

Used by 1 BusyBot node.

Type zoomOAuth2 5 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken
password Yes —
Refresh Token
refreshToken
password No —
Client ID
clientId
string Yes —
Client Secret
clientSecret
password Yes —
Token Expiry (Unix timestamp)
expiresAt
string No Unix timestamp (seconds) when the access token expires. Managed automatically after refresh.

Setting up Zoom OAuth2

  1. In Zoom OAuth2, create the credential this connection needs — the values listed in the table above. These are issued from your own Zoom OAuth2 account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Zoom OAuth2.
  3. Paste each value into the matching field and save.
  4. Add the Zoom node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use Zoom credentials?

One node: Zoom. Create the credential once and select it in that node.

What does a Zoom credential need?

5 fields: Access Token, Refresh Token, Client ID, Client Secret, Token Expiry (Unix timestamp). Required: Access Token, Client ID, Client Secret. The values come from your own Zoom account.

How are Zoom secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Does Zoom use OAuth?

Yes. This credential connects through OAuth (fields: Access Token, Refresh Token, Client ID, Client Secret, Token Expiry (Unix timestamp)): you approve access in Zoom, and the resulting tokens are stored encrypted like every other credential.

Nodes that use Zoom OAuth2

One credential works across every node below — create it once and reuse it.