Meeting sources

Turn Fireflies.ai meetings into review-ready user stories

Fireflies records and transcribes the meeting and writes the recap. Spectr takes it from there. Import a Fireflies meeting and Spectr reads the recap, the chaptered bullets, the action items and the full transcript, then splits what it finds into requirements, bugs, decisions and action items - with a draft user story and acceptance criteria under each one. You review the list, and only what you approve reaches your tracker.

How it connects

API key. You generate a key in Fireflies under Integrations and paste it into the project you want to connect.

Before you start

No paid Fireflies plan is required - the API is available on their free tier. What the key can see is what Spectr can import: a key made by a team admin covers that team's meetings, a personal key covers only your own.

What Spectr reads from Fireflies.ai

Recap and chaptered bullets: Fireflies renders the same meeting eight different ways. Spectr stores two of them - the prose recap and the chaptered bullets that keep names, numbers and timestamps - and reads them ahead of the transcript. The other six are shorter restatements of those two, and sending them would spend prompt budget saying the same thing three times.
Action items, recovered from prose: Fireflies captures action items but hands them over as one free-text block grouped by assignee, not as a list. Spectr parses the assignee and the point in the recording back out of it, so Fireflies action items land in the same high-precision section Fathom's structured ones do rather than being buried in summary text.
Full transcript: The complete speaker-labelled transcript, up to a 200,000-character budget for a single meeting - large enough that the whole of almost any meeting is sent rather than cut off. A meeting Fireflies never summarised is still imported on its transcript alone.

A person approves everything before it is published

Spectr generates specs and stories, then stops. Every story goes to a review page where you approve it, edit it inline, or reject it - individually or in bulk. Only approved stories reach an issue tracker. There is no auto-publish setting to switch on, because a backlog nobody read is not a saving.

Setting it up

In Fireflies, create an API key from the Fireflies API page under Integrations.
In Spectr, open the project you want to connect and go to Integrations.
Choose Fireflies and paste the API key. Spectr validates it before saving.
Click Import meeting. Spectr lists the meetings that key can see and filters them down to the ones relevant to this project.
Pick one or more meetings and start processing. A spec sheet and its user stories appear when the run finishes.

Frequently asked questions

Do I need a paid Fireflies plan?

No. Unlike Granola, Fireflies exposes its API on the free tier, so a free account can connect. Plan, permission and credit limits on the Fireflies side are reported as exactly that rather than as a bad key, so you are never sent round a reconnect loop that cannot fix them.

Why can I only see my own meetings?

Fireflies scopes an API key to whoever issued it - a member key returns only that member's meetings, a key made by a team admin returns that team's. There is no way to widen it from Spectr's side, so connect with a team-admin key if you want imports beyond your own calls.

Can I combine several Fireflies meetings into one spec sheet?

Yes. Select multiple meetings and Spectr processes them as a single run, with a per-meeting character budget so one long meeting cannot starve the others. Fireflies meetings also mix freely with Fathom, Granola and Read.ai imports in the same project.

Use case