Fireflies

Fireflies records and summarises meetings, which makes it an unusually clean source: the distillation has already happened, and what's left is a deliberate record of what a meeting produced.

What Pensieve reads

The AI summary only — never the transcript. Pensieve stores the overview, the action items, the topics discussed, the outline, and any custom sections your workspace has configured. Fireflies also produces several shorter restatements of the same summary — a one-line gist, a one-paragraph version, bullet forms — and Pensieve deliberately keeps none of them: they are the same meeting said again, and storing all of them would make search return the same content several times over.

What you choose

Nothing, and that is the design. Fireflies has no folder or project to pick from — what a key can see is decided by Fireflies itself, from your workspace's own privacy settings. So connecting the key is the selection.

In practice that usually means the whole workspace. Fireflies shares meetings with teammates by default, so a single key generally reaches everything the team has recorded — which is why which account you connect matters more than how many. See Authentication below.

You can set how far back to go. The range is measured by the date each meeting took place.

Authentication

Fireflies connects with an API key rather than OAuth, generated under Settings → MCP & Dev Tools.

Use a shared workspace account, not your own. Fireflies issues API keys per person and has no organisation-level key, so the account you connect with is the account the connection depends on. Creating a Fireflies seat that belongs to the company — pensieve@yourcompany.com, say — and connecting its key means the connection outlasts any one person leaving, and an admin can rotate it without touching anyone's personal account. That account needs to be a workspace member; making it an admin is simplest.

Connecting a personal key works and syncs the same meetings — the coverage is decided by your workspace's privacy settings, not by whose key it is. It just ties the connection to one person.

More than one key can be connected to the same context, and their coverage adds together. Pensieve stores each meeting once, however many keys can see it — useful if some meetings are restricted to their attendees, since only an attendee's key reaches those.

What it can't see

• Meeting transcripts, audio and video.
• Meetings restricted to their attendees, or to the person who recorded them.
• Meetings recorded before your chosen history range.

Worth knowing

Fireflies limits how often Pensieve can ask. On the Free and Pro plans that limit is a daily one — 50 and 500 requests a day respectively — rather than a per-second throttle. If a sync runs out, Pensieve stops for the day and starts the walk again after the allowance resets. Nothing already synced is lost or removed, and any meetings it hadn't reached yet arrive on the next run.

If you already push Fireflies into another connected tool, such as Notion, HubSpot or Attio, and Pensieve syncs that tool too, each meeting will arrive twice by two different routes. Pick one.