Fathom to Linear

Turn Fathom calls into Linear issues

Between a Fathom recording and a Linear backlog sits about half a day of writing tickets from memory. Spectr does that half-day. Import the call and it reads the notes, action items and transcript, separates out requirements, bugs and decisions, and drafts a Linear-ready story for each with acceptance criteria, priority and an estimate. You approve what is right and publish.

How it connects

Fathom: API key. You generate a key in Fathom and paste it into the project you want to connect. Linear: OAuth. You authorise Spectr from Linear's consent screen and choose the team. Tokens rotate on every refresh and Spectr handles that itself.

Before you start

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

Built for the way Linear teams actually triage

Linear rewards a tidy backlog, and bulk-importing raw action items is the fastest way to ruin one. Spectr publishes into one Linear team per project, sets priority, labels, estimate and assignee on the way in, and puts several stories from one requirement under a parent issue rather than scattering them as unrelated siblings. Labels you add in Linear later sync back. A cancelled issue counts as cancelled rather than quietly as done, which matters when the same data feeds your budget forecast.

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.

What Spectr writes to Linear

Issues, only after approval: Nothing reaches Linear until a person approves it in review. You can edit a story inline first - title, description, acceptance criteria, priority, estimate, labels - and publish the corrected version.
Priority, labels, estimates and assignee: Mapped onto Linear's own fields. Later edits in Spectr sync across, so a story corrected after publish does not leave a stale issue behind.
Parent and sub-issue nesting: A spec-sheet task that generates several stories publishes as a parent issue with the rest nested beneath it, rather than as a flat list that loses the grouping.

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 Spectr, open the project you want to connect and go to Integrations.
In Fathom, create an API key from your account settings.
Choose Fathom, paste the key, and let Spectr validate it.
Choose Linear, click Connect, and authorise on Linear.
Select the Linear team new issues should be created in.
Import a meeting from Fathom. Spectr gathers project context, extracts a structured spec, and writes a story per item.
Review the generated stories - approve, edit inline, or reject - then publish the approved ones to Linear.

Frequently asked questions

Can I edit a story before it reaches Linear?

Yes - that is the point of the review step. Title, description, acceptance criteria, priority, estimate and labels are all editable inline, and the version you publish is the version you edited.