Fathom to Shortcut

Turn Fathom calls into Shortcut stories

Fathom captures the conversation. Shortcut tracks the work. Spectr does the translation: it reads the notes, action items and transcript, pulls out a structured spec, and drafts a Shortcut story with acceptance criteria and an estimate for each item. Nothing is created in Shortcut until you approve it.

How it connects

Fathom: API key. You generate a key in Fathom 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 plan requirement. Connections are configured per project, and every credential is encrypted at rest.

Estimates and workflow state, set on the way in

Spectr works out the right Shortcut story type for each item, sets the estimate and tags, and creates it in the workflow state you picked at setup rather than dumping everything in a default column. Shortcut limits how fast you can create stories, so Spectr paces the publish 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 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 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

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.
In Shortcut, create an API token from your account settings.
Choose Shortcut, paste the token, then pick the team and the workflow state new stories start 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 Shortcut.