Fireflies.ai

Fireflies.ai to Shortcut

Turn Fireflies.ai meetings into Shortcut stories

Fireflies records and transcribes. Shortcut tracks the work. Spectr connects to both and produces what neither can on its own: a structured spec from the meeting, plus a Shortcut story with acceptance criteria and an estimate for every requirement, bug and decision in it. You review the set before any of it is created.

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. Shortcut: API token. You create a token in Shortcut and paste it into the project, then pick the team and the workflow state new stories should land in.

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.

Estimates and workflow state, set on the way in

A meeting rarely produces just one kind of work. Spectr splits what it finds into requirements, bugs, decisions and action items, then gives each the right Shortcut story type and estimate instead of filing everything as a generic task. Stories arrive in the workflow state you picked rather than a default column, and Spectr reads their state back afterwards so what is finished in Shortcut is what Spectr thinks is finished. Shortcut limits how fast stories can be created, so the publish is paced in small batches - a spec sheet with forty stories finishes instead of failing halfway and leaving you to work out what landed.

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 Shortcut

Stories, only after approval
Nothing reaches Shortcut until a person approves it in Spectr's review step.
Estimates, tags and assignee
Mapped onto Shortcut's own fields, with story type resolved from Spectr's feature, bug, chore and spike classification.

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

  1. In Spectr, open the project you want to connect and go to Integrations.

  2. In Fireflies, create an API key from the Fireflies API page under Integrations.

  3. Choose Fireflies, paste the key, and let Spectr validate it.

  4. In Shortcut, create an API token from your account settings.

  5. Choose Shortcut, paste the token, then pick the team and the workflow state new stories start in.

  6. Import a meeting from Fireflies.ai. Spectr gathers project context, extracts a structured spec, and writes a story per item.

  7. Review the generated stories - approve, edit inline, or reject - then publish the approved ones to Shortcut.

Frequently asked questions

Which Shortcut team do stories go to?

One team per Spectr project, selected at setup along with the workflow state new stories should start in.

Which Fireflies plan do I need?

Any of them, including the free tier - Fireflies does not gate its API by plan. Whose key you connect matters more than which plan: a member key returns only that member's meetings, a team-admin key that team's.

Related

Use case

Turn meeting notes into tickets your team can start

Import a call, get a draft backlog, approve what is right

See all 15 integrations →

Connect Fireflies.ai and Shortcut

Free plan available - five spec sheets a month, two seats, no card required.

Free plan available. 30-day free trial on Starter.