Fireflies Not Joining Your Meeting? Causes and Fixes

A notetaker that does not turn up is worse than no notetaker, because you stopped taking notes. You get to the end of an important call, reach for the transcript, and there is nothing there at all.

Fireflies publishes a troubleshooting guide for exactly this, and the causes group into three buckets: your settings, the meeting platform's settings, and the small print about what Fireflies will and will not process once it does get in.

Is your auto-join setting actually covering this meeting?

Check it before anything else. Fireflies documents an Auto-join calendar meetings control under Settings, in Meeting Settings, with four options, and three of them deliberately skip most of your calendar. If yours is narrower than you remember, the bot is behaving correctly.

• All meetings with web-conf link: Fireflies joins every calendar meeting that carries a conferencing link.
• Only meetings that I own: it joins meetings where you are the host, and skips the ones you were invited to.
• Only meetings with teammates: internal calls are covered, external ones are not.
• Only when I invite [email protected]: nothing is automatic. If you forget to add that address as a guest, no bot arrives.

Then check your rules. Fireflies documents recording rules built on keywords, email addresses or domains, and its troubleshooting guide notes rules can override your auto-join choice. A rule that skips anything containing 1:1 or confidential is the usual reason a specific meeting is quietly excluded.

Two more basics from their guide. Your Google or Microsoft calendar has to be synced to Fireflies, using the same email address as your Fireflies account. And the calendar invite needs a valid conferencing link, since a broken or incomplete URL gives the bot nothing to join.

Is your meeting platform refusing to let a guest in?

This is the second big bucket, and it is usually the one that survives every other fix. A notetaker joins as an unauthenticated guest, so any setting that requires sign-in, verification or manual admission will block it. Fireflies documents the specific settings per platform.

For Zoom, Fireflies says to turn off Only authenticated users can join from Web client, turn off end to end encryption, disable the waiting room, and enable join before host. Their guide adds an easy-to-miss detail: configure those settings before you generate the meeting link, because an already-created link carries the old rules.

For Microsoft Teams, they document enabling guest access, allowing lobby bypass for guests, setting the verification check to not required, and turning on Anonymous users can join a meeting in both Meeting Settings and Meeting Policies. For Google Meet, the Workspace safety setting has to allow all users, including people not signed in with a Google account.

A quick test settles it. Copy your meeting link, open an incognito window, and try to join without signing in. If you cannot get in as an anonymous guest, neither can the notetaker, and the fix belongs to the meeting platform rather than to Fireflies.

Work through a Fireflies no-show

1. Confirm the auto-join option matches the meeting — Settings, Meeting Settings, Auto-join calendar meetings. If it is set to Only when I invite [email protected], the address must be on the guest list. If it is set to meetings you own or meetings with teammates, an external invite is excluded by design.
2. Check for a rule that skips this meeting — Fireflies documents recording rules based on keywords, email addresses and domains, and states rules can override your auto-join setting. Look for a rule matching the meeting title, a participant address or a whole domain.
3. Verify the calendar connection and the link — The calendar must be synced with the same email as your Fireflies account, and the invite must carry a working Zoom, Teams or Meet URL. Fireflies calls out broken or incomplete links specifically.
4. Test anonymous access to the meeting — Open the meeting URL in an incognito window without signing in. If you are blocked by authentication, a captcha, a domain restriction or end to end encryption, the notetaker will be blocked by the same thing.
5. Fix the platform settings, then regenerate the link — Adjust the Zoom, Teams or Meet settings Fireflies lists, then create a fresh meeting link. Their guide notes Zoom settings need to be in place before the link is generated for the change to take effect.
6. Admit it from the lobby, and do it promptly — Fireflies documents waiting up to 10 minutes for Google Meet and 15 minutes for other platforms before it gives up and leaves. Someone with host rights has to let it in inside that window.
7. Add it manually if the call is already running — Fireflies documents an Add to live meeting control on the dashboard, so you can bring the notetaker into a call that has already started rather than losing the meeting entirely.

It joined, so why is there no transcript?

Three documented reasons cover most of these. Fireflies does not process meetings that last less than three minutes. Transcripts can take five to ten minutes to generate after the call. And if you were not the host, the recap privacy setting may be limited to the owner, so it exists but is not shared with you.

Their guide points at a Meeting Status dashboard for checking progress, and lists poor connectivity during the call, long transcripts, many speakers and browser cache issues as reasons processing runs slow. Refreshing, or opening the dashboard in a private window, is their suggested first move.

One more case is worth knowing. Fireflies documents that if the notetaker is removed part way through, transcription ends but you still receive notes for the portion it recorded. So a half transcript is not a bug, it is a record of when someone showed the bot the door.

Why did it join on a colleague's account instead?

Because someone else's auto-join or rules matched the meeting first. Fireflies lists joining on a teammate's account as its own documented outcome, driven by their auto-join and meeting rule settings rather than yours. The recording exists, it is simply filed somewhere you were not looking.

If that is what happened, the fix is a conversation rather than a setting. Ask the teammate to share the recap, then decide between you who owns the notetaker for that recurring call so the transcripts stop scattering across accounts.

Where does consent fit into this?

Recording rules differ by country and by state, and the obligation sits with whoever is doing the recording, not with the tool. Some jurisdictions need every participant to agree, others need only one. When your calls cross borders, the safe assumption is the strictest rule in the room.

Some of the settings above make a meeting easier for any guest to enter, not only your notetaker. Turning off a waiting room or allowing anonymous joins is a real trade, so make it deliberately rather than because a troubleshooting list told you to.

What are you actually trying to get out of the call?

Worth asking, because almost nobody wants a transcript for its own sake. You want the follow-up sent, the commitment logged, the CRM updated and the next meeting booked. The recording is a means to that, and it is a step that can fail while the real work still needs doing.

That is the gap we built Sistava for. You hire an AI Employee, describe in plain English what should happen after your calls, and it handles that end instead of handing you a document to work from.

What this will not fix

A meeting your organisation deliberately locks down. If your admin requires authenticated participants for good security reasons, no notetaker gets in, and that is the policy working. The answer there is to agree an exception with your admin, not to quietly loosen the settings.

It also will not bring back the call you already lost. There is no retroactive transcript, so if the bot missed a meeting that mattered, write your recollection down while it is fresh and treat the settings work as protection for next time.

And it will not resolve a participant who does not want a bot present. That is a reasonable position, and it beats a settings war. Ask, agree who takes notes, and move on with the actual meeting.

Sources

• Fireflies Knowledge Base, Why Fred did not join your meeting: troubleshooting guide
• Fireflies Knowledge Base, Troubleshoot transcription issues
• Fireflies Knowledge Base, Fireflies auto-join settings
• Fireflies Knowledge Base, How Fireflies joins and records your meetings, FAQs
• Fireflies Knowledge Base, How to invite Fireflies to meetings