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 under each one. You review the list, and only what you approve reaches your tracker.

How it connects

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

Before you start

No plan requirement. Connections are configured per project, and every credential is encrypted at rest.

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.

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 Fathom, create an API key from your account settings.
In Spectr, open the project you want to connect and go to Integrations.
Choose Fathom and paste the API key. Spectr validates it before saving.
Click Import meeting. Spectr lists your Fathom calls and filters them down to the ones relevant to this project.
Pick one or more meetings and start processing. A spec sheet and its user stories appear when the run finishes.

Frequently asked questions

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 multiple 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?

They become part of the extracted spec, and the prompt requires each one to be accounted for. Whether an action item becomes a published story is your call at the review step.

Use case