v2.1.0

Bots can now join Google Meet as a real Google Workspace user instead of an anonymous guest, and transcription runs on the provider of your choice — optionally with your own API key. Recordings whose upload fails are also recovered automatically before a bot completes.

✨New Features

• Authenticated Google Meet bots. A bot can sign in as a user in your Google Workspace and join as that person. POST /v2/meet-workspaces registers the workspace and returns the certificate to install in your Google Admin console; POST /v2/meet-logins registers the user identities under it; meet_config.credential_id or meet_config.email_group on POST /v2/bots dispatches a bot under one of them. No password, no 2FA prompt and no Google OAuth access is involved. See Authenticated bots for Meet.
• Choose your transcription provider. Gladia, Deepgram, AssemblyAI, Speechmatics, Soniox and ElevenLabs are supported, batch or real-time depending on the provider, each with its own region list. See Transcription.
• Bring your own key. Supply your own provider API key and transcription runs on your account instead of ours. Keys are stored encrypted.
• Re-transcription. A bot's transcript can be regenerated from the recorded audio, which is re-read from storage rather than from stale database state.
• A transcription_failed bot status, so a transcription problem is visible as itself instead of as a generic failure.

⚡Improvements

• Recording artifacts that fail to upload are now reconciled into storage before the bot completes, so bot.completed always carries usable URLs and transcription always runs on real audio. In that rare case the completion webhook arrives later than usual rather than arriving empty.
• Transcription failures report a clearer provider error, and the failure history is preserved rather than overwritten.

🐛Bug Fixes

• Zoom bots retry the join when Zoom's SDK returns its intermittent unknown-failure error, instead of abandoning the meeting.

↩ All releases