Fireflies.ai to Linear
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 requirement and bug with acceptance criteria, priority and an estimate.
How it works
A call is imported from Fireflies.ai. Spectr picks out a requirement, a bug, an action item and an out-of-scope ask, and drafts a story and a bug with acceptance criteria. A person approves both, they are published to Linear, and the requirements, scope log and project memory update from the same call.
A Fireflies API key, pasted into the project, and an OAuth approval on Linear, then the team picked in Spectr. Spectr handles Linear's rotating tokens; the Fireflies key works until you revoke it.
The free Fireflies plan connects. The key you use decides which meetings Spectr can see.
Meetings get revisited. When a later Fireflies meeting changes a story that is already in Linear, you correct it once in Spectr and the new title, description, acceptance criteria, priority, estimate and labels sync to the Linear issue, so nobody keeps working from the old version.
A short ad-hoc meeting that Fireflies never summarised is still imported on its transcript alone, so a quick call with the client is not lost when the recap is missing.
Fireflies groups action items under the person who took them on, inside one block of text. Spectr reads the owner and the timestamp back out, so each action item on the spec sheet shows who took it on and when.
Each Spectr project publishes to exactly one Linear team, chosen when you connect, so issues from Fireflies meetings always land with the team that owns the project.
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 and paste the key.
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 drafts a story for each requirement and bug.
Approve the drafts and publish to your Linear team. Edit a story in Spectr afterwards and the Linear issue updates to match.
Anything else? Email hello@crowdlinker.com and a person will answer.
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, separates requirements, bugs and decisions, drafts stories with acceptance criteria and an estimate for the requirements and bugs. Use the native integration for a quick to-do list; use Spectr when the output has to be a backlog somebody can work from.
A key only returns the meetings its owner can open in Fireflies, and Spectr cannot widen it. Use the key of the person who records the project's calls, or share those meetings with them in Fireflies.
Yes. Title, description, acceptance criteria, priority, estimate and labels can all be changed on the review page before you publish. Fireflies' own integration has no review step; its issues go straight to Linear.
Use case
Import a call, get a draft backlog, approve what is right
Import a Fireflies meeting and get structured specs and stories from its recap, action items, and transcript
Publish stories as Linear issues and keep their status and labels in sync
Fathom to Linear
Granola to Linear
Read.ai to Linear
Fireflies.ai to Jira
Fireflies.ai to Shortcut