Setup

🛠️

Setup required

Zoom bots require some setup to get started.

Because Zoom has formal requirements for meeting bots, there is some setup required in order for bots to join and record Zoom calls.

If you're just looking to start testing Zoom bots, you can follow the setup guide for development.

When it's time to go to production, you'll need to prepare a Zoom SDK App Submission.

Recording Behavior

Zoom has formal requirements that bots must comply with in order to record meetings. In order to be compliant with Zoom, your bots can get recording consent one of two ways:

1. (Default) Explicit consent
2. OAuth permission

Explicit consent

By default, in order for a bot to record Zoom calls:

• The host must be present in the meeting
• The host must explicitly grant permission to record by accepting the consent dialog

Because these requirements can introduce user friction and unexpected recording errors, we recommend using OAuth permissions to grant recording permissions.

OAuth permission

As an alternative to manually accepting a consent dialog each meeting, a user can grant your application OAuth permissions to allow bots to record automatically.

This means that not only will your users not have to manually grant permission each meeting, but this also enables bots to record meetings regardless of if the host is present.

Because of this, we highly recommend using this mode of consent, and have a Zoom OAuth Integration to make this process easier to implement into your application.

Joining Behavior

Zoom bots join meetings according to the host's waiting room settings.

Web vs Native Zoom Bots

---

Recall.ai offers two types of Zoom bots: Native and Web.

Zoom Web

The Zoom Web bot is recommended for most customers. Important characteristics and limitations of this bot:

• Gets one combined audio stream from all users with active speaker events

Zoom Native

The Zoom Native bot uses a more native integration method to join Zoom meetings. Specifically, it uses the Zoom Linux SDK. We don't recommend this version unless you have any of the following requirements:

• You need separate audio streams per participant

Important characteristics and limitations of this bot:

• Gets separate audio streams per participant

To configure Zoom native bots, check out Native Bots.

Limitations

---

Zoom Breakout Rooms

Currently Recall.ai does not support breakout rooms.

OnZoom Events

Currently OnZoom events are not supported.

Zoom Gov

ZoomGov is not currently supported.

Language Interpretation

Recall bots do not currently support Zoom's Language Interpretation feature.

VDI Client

Zoom currently lacks support for the recording consent dialog in the VDI client. This means that, there is no way for a bot to prompt the host for recording consent.

The workaround here is to use the Zoom OAuth Integration, which grants the bot recording consent via OAuth instead of in the call itself.

Zoom Rooms

Currently Zoom Rooms do not support the local recording consent prompt. This means that, there is no way for a bot to prompt the host for recording consent.

Cursor capture in screenshares

Capturing cursors when screensharing in Zoom is not currently supported.

Zoom SDK App Approval

---

Zoom is a bit different than other meeting platforms in that in order to use Zoom bots in production, the bot must use a set of approved Zoom SDK credentials. To get a set of Zoom SDK credentials approved, you must submit an application according to Zoom's guidelines and get your app approved.

Check out Bot Requirements for more information on these requirements.

When you're ready to start your application, we have guidelines to help ease the process of app approval.