Fathom

Meeting sources

Turn Fathom calls into review-ready user stories

Fathom records your calls and writes the summary. Spectr takes it from there. Import a Fathom meeting and Spectr reads the notes, 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 Fathom fits in

Import your Fathom call. Let Spectr take over.

A call is imported from Fathom. 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.

How it connects

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

Before you start

A Fathom account that can create an API key. Spectr does not ask for a particular Fathom plan, and nothing is imported until you choose a call.

What Spectr reads from Fathom

AI notes and summary
Fathom's own generated summary is imported first and read first, ahead of the raw transcript. It is the highest-precision account of the call, so it is the part Spectr protects from truncation on a long meeting.
Structured action items
Fathom is the only meeting source that exposes action items as real structured data rather than prose. Spectr imports them as their own section and the spec-extraction prompt requires every listed action item to be accounted for in the output.
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 call is sent rather than cut off.

Setting it up

  1. In Fathom, create an API key from your account settings.

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

  3. Choose Fathom and paste the API key. If it is wrong, Spectr says so the first time it lists your calls.

  4. Click Import meeting. Spectr lists your Fathom calls and can narrow them to the ones that mention the project's keywords.

  5. Pick one or more meetings and start processing. A spec sheet and its user stories appear when the run finishes.

Frequently asked questions

Anything else? Email hello@crowdlinker.com and a person will answer.

Does Spectr import Fathom meetings automatically?

No - import is manual. You choose which calls become specs, which matters because not every recorded call is project work. Fathom webhook auto-import was removed deliberately.

Can I combine several Fathom calls into one spec sheet?

Yes. Select up to three meetings and Spectr processes them as a single run, with a per-meeting character budget so one long call cannot starve the others.

Do Fathom action items become tickets?

No. They are listed on the spec sheet, and extraction has to account for every one, but stories are drafted from the requirements and bugs.

Which Fathom plan do I need?

Any. Fathom includes API keys on every plan, Free included (October 2026).

What happens to my Fathom transcripts?

Spectr imports the text of a meeting from Fathom: the AI notes, 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.

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 20 integrations →

AI ProductOps for the entire team.

Start for free at spectr.pm
  • Free plan
  • No credit card to sign up
  • 30-day free trial on Starter