Fireflies.ai to Linear

Turn Fireflies.ai meetings into Linear issues

Fireflies can already push meeting action items into Linear itself. What it pushes is the action-item list, as it found it, straight into your backlog. Spectr does the harder part: it reads the recap, the chaptered bullets and the full transcript, separates out requirements, bugs and decisions as well as action items, and drafts a Linear-ready story for each with acceptance criteria, priority and an estimate. Nothing is created in Linear until you approve it.

How it connects

Fireflies.ai: API key. You generate a key in Fireflies under Integrations and paste it into the project you want to connect. Linear: OAuth. You authorise Spectr from Linear's consent screen and choose the team. Tokens rotate on every refresh and Spectr handles that itself.

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.

Built for the way Linear teams actually triage

Linear rewards a tidy backlog, and bulk-importing raw action items is the fastest way to ruin one. Spectr publishes into one Linear team per project, sets priority, labels, estimate and assignee on the way in, and puts several stories from one requirement under a parent issue rather than scattering them as unrelated siblings. Labels you add in Linear later sync back. A cancelled issue counts as cancelled rather than quietly as done, which matters when the same data feeds your budget forecast.

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.

What Spectr writes to Linear

Issues, only after approval: Nothing reaches Linear until a person approves it in review. You can edit a story inline first - title, description, acceptance criteria, priority, estimate, labels - and publish the corrected version.
Priority, labels, estimates and assignee: Mapped onto Linear's own fields. Later edits in Spectr sync across, so a story corrected after publish does not leave a stale issue behind.
Parent and sub-issue nesting: A spec-sheet task that generates several stories publishes as a parent issue with the rest nested beneath it, rather than as a flat list that loses the grouping.

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 Spectr, open the project you want to connect and go to Integrations.
In Fireflies, create an API key from the Fireflies API page under Integrations.
Choose Fireflies, paste the key, and let Spectr validate it.
Choose Linear, click Connect, and authorise on Linear.
Select the Linear team new issues should be created in.
Import a meeting from Fireflies.ai. Spectr gathers project context, extracts a structured spec, and writes a story per item.
Review the generated stories - approve, edit inline, or reject - then publish the approved ones to Linear.

Frequently asked questions

Can I edit a story before it reaches Linear?

Yes - that is the point of the review step. Title, description, acceptance criteria, priority, estimate and labels are all editable inline, and the version you publish is the version you edited.

How is this different from the native Fireflies-Linear integration?

Fireflies sends its own action items to Linear, automatically, as it found them. Spectr reads the whole meeting instead of just that list, gathers context from the Notion pages, Figma files and repos you pinned, produces requirements, bugs and decisions as separate items with acceptance criteria and an estimate - and publishes nothing until a person approves it. Use the native integration for a quick to-do list; use Spectr when the output has to be a backlog somebody can work from.