AI Note Taker for Google Meet: Google Now Denies Bots by Default
11 vendors, every fact read off the vendor’s own documentation on 2026-09-09.
This page establishes one thing before anything else: on Google Meet, a third-party notetaker bot is denied entry unless a human explicitly admits it. That is not a claim we found in a blog post. It is written on two competing vendors’ own support pages, and it changes which tools are usable for anyone who meets mostly with people outside their own Workspace.
Everything below is quoted from the vendor page it came from, with the URL and the date we read it. Where a vendor publishes nothing on a point, this page says so.
The finding: Google’s default is deny
“Google now flags third-party notetaker bots as ‘potential risk’ and defaults to denying them entry”
tldv.io/google-meet/ · read 2026-09-09
the host must find Fireflies under the “With potential risks” section and select “Admit entry”
guide.fireflies.ai/articles/7581948912-how-to-invite-fireflies-to-google-meet-meetings · read 2026-09-09
Two vendors with opposite commercial interests describing the same Google behaviour is the strongest form of confirmation available without Google publishing it itself. The consequence is concrete: every bot-path tool on this page - Otter’s Notetaker, Fireflies’ Fred, MeetGeek’s Notetaker, Notta Bot, Noota’s NooBot and tl;dv’s extension bot - now needs an affirmative human override on calls that previously needed none.
What buyers get wrong: the host’s domain governs, not yours
You can configure your own Workspace perfectly and still be blocked on every external call. Fireflies is the only vendor of the 11 that states this plainly:
“even if your Fireflies setup is perfect, Fred won’t be able to join if the host organization’s settings block guests or external bots”
guide.fireflies.ai/articles/7581948912-how-to-invite-fireflies-to-google-meet-meetings · read 2026-09-09
Otter states only that your “meeting and organization settings must allow guest participants for Notetaker to join”, which understates the point: the controlling Admin Console is frequently the other organisation’s, and you have no access to it.
“Ask the host to test their meeting link by opening it in Incognito mode without logging into a Google account. If they get blocked, so will Fred”
This works for any guest-joining bot, not only Fireflies, and it takes thirty seconds. guide.fireflies.ai/articles/7581948912-how-to-invite-fireflies-to-google-meet-meetings · read 2026-09-09
Every tool on Google Meet, ordered by how it captures
Bot paths first, then bot-free, then extension-only. This ordering is deliberate: the question this page answers is how each tool gets the audio, not which tool we rate highest. Our ranking lives on the /100 ranking.
| Tool | Capture path | What the admin or user must configure | Published limitation |
|---|---|---|---|
| Notta verified 2026-09-09 | Bot joins the meeting |
| A hard five-hour ceiling: recording stops when "the maximum recording duration of 5 hours is reached". Bot name customisation is not available on the free plan, and hiding the recording notification banner is also paid-only. |
| Otter.ai verified 2026-09-09 | Bot or browser extension |
| Otter states the Notetaker "will automatically leave a meeting after detecting 12 continuous minutes of silence". It can never join invisibly, so any Workspace that blocks non-domain guests blocks Otter outright. |
| MeetGeek verified 2026-09-09 | Bot or browser extension |
| If no host has joined yet, the admission request is invisible to everyone in the call and the bot sits unadmitted. It abandons the call if no human joins within 10 minutes, and the extension path is browser-tab-only, so desktop Meet clients get nothing. |
| Noota verified 2026-09-09 | Bot or browser extension |
| Noota publishes no Google Workspace admin-configuration article at all - nothing about Meet safety settings, external-participant policy or the "potential risks" admission prompt that now governs every bot on this platform. An IT admin has no vendor page to work from before the first meeting. Its two capture paths also sit at opposite ends of the consent spectrum with no guidance reconciling them: NooBot is always visible and posts a consent message, while the extension and desktop paths send no recording notification to participants at all, leaving the entire consent burden on the user. |
| Fathom verified 2026-09-09 | Bot or browser extension |
| Fathom cannot record a Meet call the user is not personally attending - there is no unattended capture. It is also unsupported on Linux, in its own words: "If you're using a device or operating system we don't support, such as Linux, we're still unable to record calls." And the location-field requirement is a silent failure: a Meet link auto-inserted into the invite body rather than the location field is simply never detected. |
| tl;dv verified 2026-09-09 | Bot or local desktop capture |
| tl;dv publishes no minimum OS version for the desktop app anywhere on its own site, so a buyer cannot check fleet compatibility from vendor sources before committing. |
| Fireflies.ai verified 2026-09-09 | Bot, or bot-free capture through the Google Meet SDK |
| On the bot-free SDK path there is a hard three-active-participant ceiling imposed by Google's own API, no captions and no chat capture, and "Google Meet SDK supports only one active integration per meeting session", so a second notetaker on the same call is locked out. |
| Granola verified 2026-09-09 | Bot-free, local device capture |
| No video and no retained audio: the transcript generates in real time and the audio is discarded when the session ends, so there is nothing to re-review or re-transcribe if the transcript is wrong. Granola also publishes two different macOS floors, catalogued in the contradictions section below. |
| Jamie verified 2026-09-09 | Bot-free, local device capture |
| Jamie publishes no Google Meet documentation at all: its docs index contains no Google Meet page, and Meet appears only in marketing posts, so no Meet-specific requirement is published. A macOS floor of 13.1 or higher is published on meetjamie.ai; no Windows minimum version is published, and whether system audio rather than only the microphone is captured is not published either. Its own docs also warn that "Very short recordings may not generate useful summaries." |
| Krisp verified 2026-09-09 | Bot-free, local device capture |
| The most consequential published failure mode in this set: selecting only Krisp Microphone and not Krisp Speaker silently produces a transcript containing only the user's own voice, with no error and no warning. And because Safari will not let the speaker device be changed, Krisp cannot capture other participants in Meet on Safari at all. |
| Tactiq verified 2026-09-09 | Browser extension, reads platform captions |
| "Tactiq cannot retroactively change the transcription language of a completed live transcript", and in Companion mode anything said before captions were switched on is permanently lost. Tactiq's two help pages also give opposite answers on whether captions are required at all, catalogued in the contradictions section below. |
Bot joins the meeting
“You'll need to invite the Notta Bot to your meeting using the meeting invitation link.”
“If the waiting room or lobby is enabled, Notta Bot will need the host's approval to join the meeting.”
“Simply press the button on the meeting screen and the bot will join without switching screens.”
- Chrome plus the Notta extension for the in-Meet button
- Workspace and transcription language selected in the extension BEFORE the bot is invited
- Host approval whenever the lobby is on
A hard five-hour ceiling: recording stops when "the maximum recording duration of 5 hours is reached". Bot name customisation is not available on the free plan, and hiding the recording notification banner is also paid-only.
Bot or browser extension
“Notetaker joins Zoom, Google Meet, and Microsoft Teams meetings as a guest participant and will be visible”
“Notetaker cannot join a meeting anonymously or without appearing to other participants.”
“Your meeting and organization settings must allow guest participants for Notetaker to join.”
“The Record on my device instead option on the pop-up is only available for Google Meet, not Zoom meetings at this time.”
- Meeting and organisation settings must permit guest participants
- Calendar connection for auto-join
- Chrome for the extension path
Otter states the Notetaker "will automatically leave a meeting after detecting 12 continuous minutes of silence". It can never join invisibly, so any Workspace that blocks non-domain guests blocks Otter outright.
Bot or browser extension
“The Notetaker joins Google Meet calls as a participant at the scheduled start time.”
“When someone else organized the meeting, only Hosts see the pop-ups to admit participants from the lobby.”
“The Notetaker waits up to 10 minutes for at least one non-bot participant to join before it starts recording.”
- Workspace Meet safety settings must allow guest join requests
- A host must be present to see and action the lobby prompt
- The recording widget "only appears on the meeting page when you're using the browser version of Google Meet"
If no host has joined yet, the admission request is invisible to everyone in the call and the bot sits unadmitted. It abandons the call if no human joins within 10 minutes, and the extension path is browser-tab-only, so desktop Meet clients get nothing.
Bot or browser extension
“Download the Noota extension to record your Meets meetings on your browser. Or connect your Meets calendar and let a bot join and record.”
“Once you connect your calendar with Noota, NooBot will automatically join all your meetings.”
“When using the Meeting Assistant, recording is always visible to meeting attendees.”
- Calendar connection to Noota is mandatory for the bot path, plus enabling bot join in advanced settings
- Manual fallback: add the assistant email directly to the invite
Noota publishes no Google Workspace admin-configuration article at all - nothing about Meet safety settings, external-participant policy or the "potential risks" admission prompt that now governs every bot on this platform. An IT admin has no vendor page to work from before the first meeting. Its two capture paths also sit at opposite ends of the consent spectrum with no guidance reconciling them: NooBot is always visible and posts a consent message, while the extension and desktop paths send no recording notification to participants at all, leaving the entire consent burden on the user.
Bot or browser extension
“Fathom looks for any meetings on your calendar with a Google Meet link in the location field and adds those to your Fathom desktop app drawer.”
“Once installed, Fathom can intercept the click of a Google Meet meeting link and join any unscheduled calls.”
“Fathom can only record a Zoom, Microsoft Teams, or Google Meet call if you are also present on the call.”
“If you're using a device or operating system we don't support, such as Linux, we're still unable to record calls.”
- Desktop app on macOS or Windows
- Chrome extension permitted to read and change site data on meet.google.com
- The meeting must be on the primary calendar and the Meet link must sit in the LOCATION field of the invite, not the description
Fathom cannot record a Meet call the user is not personally attending - there is no unattended capture. It is also unsupported on Linux, in its own words: "If you're using a device or operating system we don't support, such as Linux, we're still unable to record calls." And the location-field requirement is a silent failure: a Meet link auto-inserted into the invite body rather than the location field is simply never detected.
Bot or local desktop capture
“Use the Chrome extension bot to join and take notes automatically, or use the desktop app to capture directly from your device with no bot in the call.”
“Google now flags third-party notetaker bots as 'potential risk' and defaults to denying them entry”
- Bot path: Chrome, the extension, and host admission past Google's risk prompt
- Bot-free path: the desktop app, published as separate Mac (M-series), Mac (Intel) and Windows builds
tl;dv publishes no minimum OS version for the desktop app anywhere on its own site, so a buyer cannot check fleet compatibility from vendor sources before committing.
Bot, or bot-free capture through the Google Meet SDK
“make sure your (or the workspace that is hosting the meeting) Google Meet configuration allows external guests and bots to join”
“even if your Fireflies setup is perfect, Fred won't be able to join if the host organization's settings block guests or external bots”
“The Google Meet SDK captures audio and video from up to three active participants at a time - this is a Google API limitation.”
“The SDK currently doesn't support chat messages or captions - only live audio and video streams are recorded.”
- Admin Console, Apps > Google Workspace > Google Meet set to "All users (including users not signed in with a Google account)"
- The host must find Fireflies under the "With potential risks" section and select "Admit entry"
- The SDK path additionally needs admin authorisation of Meet SDK scopes for recording and media access
On the bot-free SDK path there is a hard three-active-participant ceiling imposed by Google's own API, no captions and no chat capture, and "Google Meet SDK supports only one active integration per meeting session", so a second notetaker on the same call is locked out.
Bot-free, local device capture
“Granola captures audio at the operating system level without joining as a bot, so you can use any browser with Google Meet”
“Granola transcribes but doesn't capture video. Granola doesn't record your screen or save audio files.”
- macOS: grant Microphone and Screen & System Audio Recording in System Settings
- Windows: granted automatically
- Calendar connection for meeting context
No video and no retained audio: the transcript generates in real time and the audio is discarded when the session ends, so there is nothing to re-review or re-transcribe if the transcript is wrong. Granola also publishes two different macOS floors, catalogued in the contradictions section below.
Bot-free, local device capture
“Jamie can only be used on your macOS or Windows device and therefore does not require any virtual bot”
“Jamie will use your default microphone automatically”
- macOS or Windows desktop device
- Microphone permission granted in System Settings
- A microphone must be connected for the recorder to run
Jamie publishes no Google Meet documentation at all: its docs index contains no Google Meet page, and Meet appears only in marketing posts, so no Meet-specific requirement is published. A macOS floor of 13.1 or higher is published on meetjamie.ai; no Windows minimum version is published, and whether system audio rather than only the microphone is captured is not published either. Its own docs also warn that "Very short recordings may not generate useful summaries."
Bot-free, local device capture
“Select Krisp Microphone and/or Speaker to work in Google Meet.”
“If Krisp Speaker isn't set up with your calling app, only your speech will be transcribed, and not the speeches of other participants.”
“Some browsers, like Safari, won't let you change the speaker working with it. Others, like Google Chrome, will allow the change.”
- Krisp desktop app installed with BOTH Krisp Microphone and Krisp Speaker selected as the devices inside Google Meet
- Chrome rather than Safari if the speaker device needs switching
The most consequential published failure mode in this set: selecting only Krisp Microphone and not Krisp Speaker silently produces a transcript containing only the user's own voice, with no error and no warning. And because Safari will not let the speaker device be changed, Krisp cannot capture other participants in Meet on Safari at all.
Browser extension, reads platform captions
“Tactiq automatically transcribes Google Meet meetings in your browser.”
“You do not need to turn on Google Meet captions (CC) for Tactiq to transcribe a Google Meet meeting.”
“Tactiq begins transcribing in Companion mode after Google Meet live captions are turned on.”
“Tactiq can only capture speech after live captions are enabled. Speech from earlier in the meeting cannot be recovered if it wasn't transcribed.”
- Desktop Chrome or Edge
- Extension installed and signed in
- The user must stay in the call for its whole duration, because leaving stops capture
- Transcription language set before or during the meeting
"Tactiq cannot retroactively change the transcription language of a completed live transcript", and in Companion mode anything said before captions were switched on is permanently lost. Tactiq's two help pages also give opposite answers on whether captions are required at all, catalogued in the contradictions section below.
Three vendors contradicting themselves
Both quotes and both URLs in each case, so you can check us.
Tactiq: Are Google Meet live captions required, or not?
“You do not need to turn on Google Meet captions (CC) for Tactiq to transcribe a Google Meet meeting.”
help.tactiq.io/en/articles/9535734-how-to-use-tactiq-with-google-meet
“Tactiq begins transcribing in Companion mode after Google Meet live captions are turned on.”
Two help pages, opposite answers, on the single most important dependency for Meet capture. The Companion-mode page adds that speech from earlier in the meeting cannot be recovered if it was not transcribed, so acting on the first page and skipping captions can cost the opening of the call.
Granola: What is the minimum macOS version?
“macOS 13 or above”
www.granola.ai/blog/granola-google-meet-integration-recording-transcription
“Granola requires a minimum macOS 14 to run”
docs.granola.ai/help-center/getting-started/setting-up-granola-for-the-first-time
An IT team sizing a fleet upgrade gets a different answer depending on which page it lands on.
Krisp: Is bot-free capture as clean as the product page says?
“Select Krisp Microphone and/or Speaker to work in Google Meet.”
help.krisp.ai/hc/en-us/articles/4420146557340-Set-up-Google-Meet-with-Krisp
“If Krisp Speaker isn't set up with your calling app, only your speech will be transcribed, and not the speeches of other participants.”
help.krisp.ai/hc/en-us/articles/8326933081116-AI-Meeting-Assistant-FAQ
Krisp markets bot-free recording with no caveat, while its help centre discloses that a mis-set speaker device yields a transcript containing only the user's own voice. The word "and/or" in the setup instruction is what makes the failure possible.
Contradictions across the wider data set are tracked on the vendor claim tracker.
What nobody publishes
We looked for it on all 11 vendors’ documentation on 2026-09-09 and found nothing: not one of them publishes anything about how its capture interacts with Google Meet’s own recording, or with Gemini “take notes for me”. Whether two transcripts are produced, whether the platform’s notice covers the third-party tool, whether one interferes with the other - none of it is documented by any vendor here. That is a gap in the vendor documentation. Saying so is more useful than pretending we know.
Which path fits which constraint
If you cannot get an admin override from other organisations’ domains - which is most external sales, recruiting and client work - bot paths are unreliable on Meet by Google’s own default. A local-capture tool is the answer, because nothing has to be admitted to the call at all.
If you rely on the platform’s recording notice as your consent mechanism, bot-free capture removes that notice, and it may be unusable for you. That cuts against Granola, Jamie, Krisp and Noota’s extension path alike - including our own tool, which sends no notification on the extension and desktop paths.
If you are on Linux, Fathom is out by its own statement: “If you’re using a device or operating system we don’t support, such as Linux, we’re still unable to record calls.” help.fathom.video/en/articles/276608
The mechanism question - what “no bot” actually means, and whether anyone on the call is told - is worked through on AI note takers that don’t join the meeting.
Questions buyers ask first
Does Google block AI notetaker bots on Google Meet?
By default, yes. tl;dv publishes on its own site that "Google now flags third-party notetaker bots as 'potential risk' and defaults to denying them entry" (https://tldv.io/google-meet/, read 2026-09-09), and Fireflies independently instructs hosts to find the bot under the "With potential risks" section and select "Admit entry" (https://guide.fireflies.ai/articles/7581948912-how-to-invite-fireflies-to-google-meet-meetings, read 2026-09-09). Two vendors with opposing commercial interests describe the same Google behaviour, so every bot-path tool now needs an affirmative human override.
Whose Google Workspace settings decide whether a notetaker can join?
The host organisation's, not yours. Fireflies states it plainly: "even if your Fireflies setup is perfect, Fred won't be able to join if the host organization's settings block guests or external bots" (https://guide.fireflies.ai/articles/7581948912-how-to-invite-fireflies-to-google-meet-meetings, read 2026-09-09). Otter states only that "Your meeting and organization settings must allow guest participants for Notetaker to join" (https://help.otter.ai/hc/en-us/articles/4425393298327-Otter-Notetaker-Overview, read 2026-09-09), which understates the point: the controlling Admin Console is frequently the other organisation's, and you have no access to it.
How can I test whether a notetaker will be admitted before the meeting?
Fireflies publishes a free pre-flight test: "Ask the host to test their meeting link by opening it in Incognito mode without logging into a Google account. If they get blocked, so will Fred" (https://guide.fireflies.ai/articles/7581948912-how-to-invite-fireflies-to-google-meet-meetings, read 2026-09-09). It works for any guest-joining bot, not only Fireflies.
Which Google Meet notetakers publish no Workspace admin documentation?
Noota, whose team edits this site, publishes no Google Workspace admin-configuration article at all - nothing on Meet safety settings, external-participant policy or the potential-risks admission prompt. Jamie publishes no Google Meet documentation of any kind; Meet appears only in its marketing posts. In both cases an IT admin has no vendor page to work from before the first meeting.
Do any of these tools document how they interact with Google Meet's own recording or Gemini notes?
No. We checked all 11 vendors' documentation on 2026-09-09 and not one publishes anything about how its capture interacts with Google Meet's own recording or with Gemini "take notes for me". That is a gap in the vendor documentation, and we would rather say so than guess.
Every fact on this page was verified on 2026-09-09 against the vendor documentation linked beside it. The other platform guides - Microsoft Teams and Zoom - were read on their own earlier date and carry it. How we assess tools generally is on the methodology page.