Setting up Google Meet recording
Google Meet recording with Mavio works through the meeting bot. There is no separate Google Meet “integration” to install — the bot joins Meet calls using the meeting link from your Google Calendar.Connect Google Calendar
Go to Settings > Integrations > Google Calendar and click Connect. Authorize Mavio to read your calendar events. This is how Mavio discovers your Google Meet meetings.
Enable auto-join
Navigate to Settings > Recording and toggle Auto-join meetings to on. Mavio will detect Google Meet links in your calendar events automatically.
Configure filters (optional)
Choose which meetings to record:
- All meetings with a Google Meet link
- Only external meetings
- Only meetings with 3+ attendees
- Meetings matching specific keywords in the title
How it works with Google Meet
When the Mavio bot joins a Google Meet call:- It appears in the participant list as Mavio Notetaker.
- Google Meet displays a notification to all participants that the meeting is being recorded.
- The bot captures the mixed audio stream.
- When the meeting ends or the last participant leaves, the bot disconnects.
Google Workspace requirements
| Account type | Bot can join? | Notes |
|---|---|---|
| Google Workspace (Business, Enterprise) | Yes | Bot joins seamlessly |
| Google Workspace (Education) | Yes | Admin may need to enable external participants |
| Personal Gmail | Conditional | Someone in the meeting must admit the bot manually |
Google Workspace admins can restrict external participants from joining meetings. If the Mavio bot cannot join, ask your admin to allow external guests or add
bot.mavioapp.com to the trusted domains list.Manual recording
To record a Google Meet call that is not on your calendar:- Click Record now in the Mavio dashboard.
- Paste the Google Meet link (format:
meet.google.com/xxx-xxxx-xxx). - Click Start recording. The bot joins within 15 seconds.
Google Meet-specific behavior
Admission
In some Google Workspace configurations, external participants must be admitted by someone inside the organization. If the Mavio bot requires admission, the host or any internal participant must click “Admit” when they see the request. The bot waits up to 5 minutes before timing out.Recording consent notification
Google Meet automatically notifies all participants that a recording is active. This is a platform-level behavior and ensures transparency. The notification appears as a banner at the top of the Meet window.Companion mode
If a participant joins via companion mode (second screen), the bot captures audio from the primary session only. Companion mode does not produce a separate audio stream.Comparing Mavio vs. native Google Meet recording
| Feature | Mavio | Google Meet native |
|---|---|---|
| Transcription | 95%+ accuracy, 40+ languages | English only on Business Standard+ |
| AI summary | Automatic with action items | Not available |
| Speaker identification | Automatic with voice profiles | Basic |
| Storage | Mavio cloud (searchable) | Google Drive |
| Sharing | Link, email, Slack, Notion | Google Drive sharing |
| Cross-platform search | Search across all meetings | Per-recording only |
| Cost | Included in Mavio plan | Requires Workspace Business Standard+ |
Troubleshooting
The bot cannot join the meeting
The bot cannot join the meeting
Check that the Google Meet link is valid and the meeting has started. For Google Workspace organizations, verify that external participants are allowed. See bot not joining for additional steps.
No recording appears after the meeting
No recording appears after the meeting
Ensure the bot was admitted to the meeting. Check the Meetings page in Mavio — if the recording shows as “Failed,” hover over it to see the reason. Common causes include the bot not being admitted or the meeting ending before the bot could join.
Speaker names are wrong
Speaker names are wrong
Connect Google Calendar so Mavio can match speakers to attendee names. You can also correct speaker labels manually — see speaker identification.
Advanced configuration
Google Workspace admin approval
Google Workspace admin approval
In many organizations, a Google Workspace administrator must approve third-party apps before users can authorize them. If you receive an “app blocked” error when connecting:
- Ask your Google Workspace admin to go to Admin Console > Security > API Controls > App Access Control.
- Search for the app in the third-party apps list.
- Set the app access to Trusted or Limited (limited is sufficient — the app only needs calendar read access).
- Alternatively, the admin can add
bot.mavioapp.comto the list of trusted domains.
Google Workspace Education and Enterprise editions have stricter default policies. Admin approval is almost always required in these environments.
Calendar-based auto-join rules
Calendar-based auto-join rules
Fine-tune which Google Meet meetings the bot automatically joins by configuring rules in Settings > Recording:
- All meetings with a Google Meet link — the bot joins every calendar event that contains a Meet link.
- External meetings only — only record meetings where at least one participant has an email domain different from yours.
- Minimum attendees — set a threshold (e.g., 3+) to skip 1:1 calls.
- Keyword match — only join meetings whose title contains specific words. Add keywords in Settings > Recording > Auto-join keywords.
- Calendar filter — if you have multiple Google Calendars, choose which calendars the bot monitors. Go to Settings > Integrations > Google Calendar > Calendars and toggle each calendar on or off.
Recording permissions for external participants
Recording permissions for external participants
Google Meet’s recording consent behavior varies based on participant type:
- Internal participants (same Google Workspace domain) — see the recording notification banner automatically.
- External participants (different domain or personal Gmail) — also see the recording banner. Google Meet notifies all participants regardless of their account type.
- Anonymous participants (joined without signing in) — see the recording notification but may not have a named identity in the transcript.
Meet add-on vs bot recording
Meet add-on vs bot recording
There are two approaches to recording Google Meet calls. Here is how they compare:
Use the bot when you want automatic, hands-off recording with full participant visibility. Use the browser extension when you prefer a silent recording method or when the bot cannot join due to organizational restrictions.
| Aspect | Bot recording | Browser extension |
|---|---|---|
| How it works | Cloud bot joins as a participant | Extension captures tab audio in your browser |
| Visible to others | Yes — appears in participant list | No — invisible to other participants |
| Setup required | Calendar connection | Chrome extension installed |
| Recording consent | Google Meet shows recording banner | No platform-level notification |
| Audio quality | Consistent (server-side capture) | Depends on your browser and connection |
| Works without you in the call | Yes (bot joins independently) | No (you must be in the tab) |