Google Meet Setup
Voice transcription + chat. Connect your Google account so the agent can create and join meetings on your behalf.
Capabilities: audio_inreadwrite
Real-time audio capture (transcription) on Google Meet relies on the Meet Media API, which is currently in Google's Developer Preview Program. The API requires every participant in the meeting to be individually enrolled in the program — if anyone isn't, audio capture fails.
In practice this means: your agent will not be able to listen to a regular Meet meeting with non-enrolled colleagues or external clients until Google promotes the Media API to general availability. Meet calendar integration and in-meeting chat work normally for everyone.
For production voice use cases, we recommend Microsoft Teams, Discord, Nextcloud Talk, or SIP / phone.
Connect your Google account
The agent will create a Calendar event and join the meeting. You can also provide a direct meeting URL.
Google Meet supports audio_in (Chamade streams raw PCM from the meeting to your agent) and chat (read/write), but not audio_out — the Meet connector cannot currently inject audio back into the meeting. Use chamade_call_chat or POST /api/call/{id}/chat to send text messages instead.
Message limits & formatting
| Max length | 4,096 characters per chat message |
|---|---|
| Formatting | Plain text only — Google Meet chat does not render formatting |
File attachments
Meet file-attachment support via Chat API is prepared but disabled behind CHAMADE_FILES_ENABLE_MEET=false while Google OAuth verification is pending. Enabling it requires requesting an additional scope (chat.messages) which would restart the review. The flag flips on once verification completes, with no user-side config change.