Meeting sources
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 for each requirement and bug. You review the list and publish the stories to your tracker.
How Fireflies.ai fits in
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 the team's tracker (Jira, Linear, or Shortcut), and the requirements, scope log and project memory update from the same call.
API key, created on the Fireflies API page under Integrations and pasted into the Spectr project. Whose key it is decides which meetings Spectr can list.
No paid Fireflies plan is required - the API is available on their free tier. What the key can see is what Spectr can import: the meetings its owner recorded or can open in Fireflies.
On the Fireflies API page under Integrations, create a key from the account that records this project's meetings.
Open the Spectr project's Integrations tab and pick Fireflies.
Paste the key. If Fireflies refuses it, Spectr tells you the first time it lists your meetings, and reports a plan or credit limit as a plan or credit limit.
Use Import meeting to see the meetings that key can reach, optionally narrowed to the ones that mention the project's keywords.
Choose one, or up to three, and process them. When the run ends, the spec sheet and its draft stories are ready to review.
Anything else? Email hello@crowdlinker.com and a person will answer.
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.
Fireflies scopes an API key to the person who created it, so it returns the meetings that person can open. Spectr cannot widen it. Connect with the key of whoever records the project's calls, or have meetings shared with that account in Fireflies, if you want imports beyond your own calls.
Yes. One project can import from Fireflies, Fathom, Granola and Read.ai side by side, and up to three meetings can be processed as one run, each keeping its own share of the reading budget.
Spectr imports the text of a meeting from Fireflies: the recap, the chaptered bullets, the action items and the transcript. It never imports audio or video. The text is stored encrypted on AWS in the US and used only inside the project you imported it into, and Spectr does not train any AI model on it. Deleting a meeting in Spectr archives it; to have it removed completely, email hello@crowdlinker.com.
Use case
Import a call, get a draft backlog, approve what is right
Import a Fathom call and get structured specs and stories from its notes, action items, and transcript
Native Granola import - no Zapier, no scripts - straight through to Jira, Linear or Shortcut
Connect Read.ai over OAuth and mix its meetings freely with Fathom and Granola in one project
Publish stories as Linear issues and keep their status and labels in sync
Publish stories as Jira issues, with sub-task nesting, and read their status back
Shortcut