Fathom to Linear
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 requirement and bug with acceptance criteria, priority and an estimate. You approve what is right and publish.
How it works
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 Linear, and the requirements, scope log and project memory update from the same call.
Paste a Fathom API key into the Spectr project, then authorise Linear on its own consent screen. Linear rotates its refresh tokens every time they are used; Spectr stores each new pair as it arrives, so the connection does not quietly lapse.
Nothing to upgrade on either side. Know which Linear team owns this work before you connect: a Spectr project publishes to exactly one.
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, estimate, assignee and the team's matching labels on the way in, and puts the stories of a parent task under one parent issue rather than scattering them as unrelated siblings. Labels you add in Linear come back on the next status refresh. A cancelled issue counts as cancelled rather than quietly as done, which matters when the same data feeds your budget forecast.
Fathom's own summary is read ahead of the transcript, and the transcript is sent whole up to 200,000 characters, which covers almost any call. A requirement raised seventy minutes in is as likely to reach Linear as one raised in the first five.
Each draft explains why the work came up, lists criteria a reviewer can test, and draws on what the project already knows from earlier calls and, on paid plans, its memory. Whoever picks up the Linear issue does not need to have been on the call.
You assign drafts from the project's team, which Spectr syncs from your Linear team's members. When someone reassigns an issue in Linear, the next status refresh matches the new assignee to the same person in Spectr rather than storing them a second time.
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 and paste the key.
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 drafts a story for each requirement and bug.
Approve what is right, one at a time or all at once, and publish into your Linear team, where each issue arrives with its priority and estimate set, plus any labels that already exist in the team.
Anything else? Email hello@crowdlinker.com and a person will answer.
Not on its own. Fathom's task integration is Asana, and the usual route to Linear is a Zapier template that turns each action item into an issue. Spectr connects to Fathom with an API key, on any Fathom plan, and to Linear over OAuth.
Yes. Title, description, acceptance criteria, priority, estimate and labels can all be edited before publishing, and the version you publish is the version you edited.
Edits made in Spectr sync across, and Linear's workflow state, labels and assignee are read back onto the story.
Whoever you pick on the draft, from the project's team, which Spectr syncs from your Linear team's members. A story with no one picked is created unassigned.
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
Publish stories as Linear issues and keep their status and labels in sync
