Bot Authentication

Meetings are often limited to signed in accounts for security purposes. Our bots are by default guest accounts and are therefor blocked by these security measures. Below we'll explain how to set up authentication with your own accounts for each supported platform.

Google Meet & Microsoft Teams

Google Meet & Microsoft teams authentication works by simply logging into an account. Via the platform you can add "Authenticated Accounts", each account will have an account id. When requesting a new bot, you can simply provide this id via authentication.account_id.

By default, the bot will first try to join the meeting as a guest, if authentication is required then the bot will use the provided credentials to sign in. You can also force authentication by setting the authentication.always_authenticate option.

Important considerations for authenticated accounts:

• The bot name will be the account name if authenticated, for this reason by default we'll try to join as a guest. If the bot is authenticated then provided bot name will be ignored.
• Google Meet & Microsoft Teams merges participants on the same accounts into 1 participant. This means if 2 bots with the same authentication joins the same meeting, it'll look like a single participant in the meeting.
• Make sure MFA (Multi-Factor Authentication) is disabled on these accounts. The bot should be able to log in with purely email - password.

Zoom

Zoom authentication is based on the Zoom ZAK Tokens feature. This is a short-lived token that gives the bot access to join the meeting in the name of a certain user. This token can be generated via the Zoom API. Once you have generated this token, you can provide the token via the authentication.zoom_zak_token field.