Fireflies AI Assistant: Set Up Meeting Notes and Follow-Ups

Set up the Fireflies AI assistant by choosing which meetings it should capture, connecting the calendar you use, and checking the host’s Zoom or Google Meet settings. Run an authorized test, verify the recording and notes, then confirm the decisions and follow-ups before sharing them.

Tools like fenbs can keep those checked outcomes available for later work, but the transfer is manual. Fireflies handles meeting capture; the useful project record holds what people confirmed and where to start next. Getting both parts right prevents a successful recording from becoming a forgotten recap.

What should you set up first?

1. Confirm the host permits recording and tell attendees how the recording and notes will be used.
2. Connect the calendar you intend to use and choose a deliberately narrow set of meetings to capture.
3. Review recap email recipients and meeting access separately before the first real call.
4. Create an authorized Zoom or Google Meet test with a valid meeting link and invite Fireflies.
5. Check admission, audio, the resulting transcript, and who can open the notes. Assign someone to review future recaps.

The Fireflies invitation guide↗ (opens in a new tab) describes connected Google or Outlook calendars, manual invitations to fred@fireflies.ai, auto-join preferences, and adding the assistant to a live meeting. Choose the method that suits your approved recording process instead of assuming broad calendar access is necessary.

How do you control which calls it joins?

Inspect the auto-join choice before relying on the calendar connection. Start with meetings you have explicitly selected or invited the assistant to attend. Check both recurring events and one-time calls so a setup intended for internal planning does not unexpectedly extend to a client discussion.

Fireflies also distinguishes recap email delivery from permission to view the meeting. Its pre-meeting setup guide↗ (opens in a new tab) explains the separate settings. Select the audience for each, then verify the result with a permitted test recipient. An email setting alone does not establish who has access.

Make the recording arrangement clear to attendees and follow your organization’s approval process. If the host declines recording, use approved manual notes. The general AI meeting note taker guide explains why choosing the capture tool and authorizing capture are separate decisions.

What needs checking for a Zoom meeting?

For the meeting-bot route, Fireflies joins as a guest, so the host’s settings matter. The Fireflies Zoom setup guide↗ (opens in a new tab) covers guest access, authentication restrictions, encryption, waiting rooms, and meeting links. Ask the host or administrator to review those requirements against the organization’s policy.

Keep the Zoom meeting link in the invitation and ensure the intended Fireflies participant is invited. If a waiting room is enabled, arrange for the host to admit it. Check the participant list and recording state rather than assuming a calendar invitation proves the call is being captured.

Do not weaken required security settings merely to make a note taker work. If the approved meeting configuration blocks guest recording, choose a different authorized notes method. For platform-native options, the separate Zoom AI meeting assistant guide covers that nearby question.

What changes for a Google Meet meeting?

The bot route still needs a valid meeting link and host admission where required. The Fireflies Google Meet guide↗ (opens in a new tab) explains that the host organization must permit guest access. Your own Fireflies account cannot override a client’s Google Workspace settings.

Ask the host to expect the participant and verify that it enters the correct meeting. If entry is blocked, resolve the issue with the host or administrator before another attempt. Avoid repeatedly adding a bot while the meeting continues and participants are unsure what it is doing.

Fireflies also documents a Google Meet Chrome extension↗ (opens in a new tab) that can invite the Notetaker and provides a separate Live Assist experience. That guide describes Google Meet in Chrome, not a universal Zoom extension. Choose one capture arrangement intentionally so your test does not produce confusing duplicate records.

How can you test the complete setup?

Use a short, authorized test call with ordinary speech, a participant name, one clear action, and one conditional suggestion. For example, say that a proposal may be revised after someone confirms scope. Inspect whether the notes preserve the condition and distinguish that suggestion from an accepted commitment.

• Entry: did the expected participant join the right meeting, with the host’s knowledge?
• Capture: is the relevant audio present, including the closing agreement?
• Meaning: do the transcript and recap preserve names, dates, negations, and conditions?
• Access: can the intended reviewer open the notes, and are unintended recipients excluded?
• Follow-through: can someone identify the agreed action and the question still waiting on a person?

A useful test includes the work after capture. Have the reviewer check the source and ask the supposed owner to confirm the action. Record what failed rather than changing several settings at once and losing track of the cause. That makes the next test easier to interpret.

What should leave the meeting app?

Move the reviewed work forward: the person’s decision, its reason, accepted actions, dependencies, and the next checkpoint. Leave speculative ideas identifiable as ideas. The original recording is evidence of a conversation, while the project record needs the current answer about what someone should do.

This is a narrower job than the broader help described in our AI personal assistant guide. When the work later ships, release notes from tasks should use checked task outcomes rather than treating an early meeting promise as evidence of completion.

Keep that reviewed handoff in fenbs when later assistants need the same starting point; the AI handoff guide explains what to save. The next session should see what is confirmed, what is blocked, and which decision still needs a person.

How to do this with fenbs

1. Create a free account and add the project your test meeting concerns.
2. After reviewing the transcript, manually add each confirmed follow-up as an appropriate task. Put the accepted owner, any agreed date, expected result, and source reference in the note.
3. Record the person’s confirmed choice in Decisions and rules with the decider and reason. Keep unanswered choices open; assistants cannot decide or sign off.
4. Save Where we left off with what is ready, what needs checking, and where the next session should begin. Connect a supported AI app through Integrations and ask it to read context before acting.

fenbs does not connect to Fireflies or automatically import meeting notes. It is not the right fit if you only need capture, playback, and a meeting archive. Use it for the checked decisions and active work that must remain useful across sessions. Find other practical guides in AI at work.