How to Get Fireflies to Join and Summarize Your Meetings

November 16, 2026

Fireflies is a meeting notetaker that joins your calls, transcribes them, and writes a summary with action items. You connect a calendar, it joins meetings automatically, and you read the transcript afterwards.

Setup takes ten minutes. Getting output you actually use takes a bit more, because the default summary is written for scanning, not for follow-up.

How do Fireflies and your calendar connect?

Sign in with Google or Microsoft, authorise calendar read access, and Fireflies watches for events with a conferencing link. Zoom, Google Meet, and Teams links all trigger it.

The free plan covers a limited number of transcription credits per month, which for one person is roughly a handful of hour-long calls. Paid tiers raise storage from 800 minutes to thousands and add team features like shared search.

Two behaviours to set on day one: which calendars it watches, and whether it joins by default. If you leave the default on across a shared team calendar, it will join calls where nobody expected a bot in the room.

How do you control which meetings get recorded?

Use the dashboard’s calendar rules. You can scope by calendar, exclude events with a keyword in the title, and require an invitee from a specific domain.

A workable policy for a small team:

  • Record internal standups and client calls.
  • Exclude anything with “1:1” or “HR” in the title.
  • Exclude events where the organiser is outside your domain, then add the bot manually when needed.

That last rule saves you the awkward moment where a prospect notices a recording notice. Not every company is fine with it, and consent requirements vary by region — two-party consent states in the US require telling participants.

What does the default summary contain?

The template covers an overview, key topics, and a bulleted action items list with owners when names are clear enough for the model to attribute them.

Attribution is the weak link. If three people say “I’ll take care of that,” the summary picks one or writes “the team.” You can improve this by using the transcript view and editing, but the automatic version is only reliable with two or three speakers who address each other by name.

For calls with heavy crosstalk, the transcript is worth more than the summary. Fireflies timestamps each line and labels the speaker, so you can search for a phrase and jump to the audio.

How do you customise the summary format?

In settings, there is a summary template you can rewrite. Three changes that make output far more useful:

  • Replace the “topics” section with “decisions made” — topics are easy to generate and rarely what you need later.
  • Force the action items list to include a due date field, even if the model writes “unassigned.” Gaps are visible that way.
  • Ask for a one-sentence “what changed” line at the top, for anyone catching up.

After editing, run it on an old recording and compare. The difference between a generic summary and one with decisions plus owners is the difference between a document people read and one they ignore.

How do you push summaries where people will see them?

Fireflies integrates with Slack, Notion, HubSpot, and via Zapier or its API for anything else. The useful pattern is narrow: post only to the channel that owns the account, and only when the meeting title contains a client name.

A blanket integration that posts every summary to one channel produces noise. Turn on selective sharing, or send summaries to email and let people opt in.

What are the honest downsides?

Accuracy on accented English and on technical jargon drops noticeably. Add your product’s terms to the vocabulary list in settings if it offers one; unrecognised names appear as plausible but wrong words throughout the transcript.

It also cannot read slides. If a decision was made in a shared screen, the transcript may miss the context entirely. For those calls, keep the notes.

And the bot joining is visible. Some prospects ask about it. Decide your answer in advance.

Quick Summary

  • Fireflies joins calendar meetings, transcribes them, and writes summaries with action items.
  • Set calendar rules first so the bot does not join sensitive calls by default.
  • Default action-item attribution is unreliable with more than three speakers; the transcript is more trustworthy.
  • Rewrite the summary template around decisions and owners, not topics.
  • Two-party consent rules mean you must tell participants you are recording in some regions.