Fathom to Shortcut
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 requirement and bug.
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 Shortcut, and the requirements, scope log and project memory update from the same call.
Both sides use a credential you create yourself, with no OAuth step. The Fathom API key and the Shortcut API token go into the Spectr project, are encrypted at rest, and can be revoked from the tool that issued them.
Once Shortcut is connected, set a default team and starting workflow state under Story defaults. They are optional: without them, stories land in the first unstarted state of your first workflow.
Set a starting workflow state under Story defaults and every approved story is created there, with its estimate and tags already set. Work from a Fathom call then turns up in the column your team triages from.
When you import, Spectr lists your Fathom calls and can narrow them to the ones that mention the project's keywords, with the rest one click away. A sales demo recorded the same week is easy to leave out.
Every draft is classed as a feature, bug, chore or spike, and that class decides the Shortcut story type. You can change the class, the estimate or the tags on the draft before anything is created.
When someone tags a published story in Shortcut, the tag comes onto the story in Spectr at the next status refresh. The marker Spectr uses to carry priority is filtered out, so the tags you see are the ones people chose.
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.
In Shortcut, create an API token from your account settings.
Choose Shortcut and paste the token, then optionally set a default team and starting workflow state.
Import a meeting from Fathom. Spectr gathers project context, extracts a structured spec, and drafts a story for each requirement and bug.
Approve the drafts and publish. The stories appear in the Shortcut team and workflow state you chose, with estimate and tags already filled in.
Anything else? Email hello@crowdlinker.com and a person will answer.
No. Fathom has no Shortcut integration, and Zapier lists no Fathom-to-Shortcut template. Spectr connects to Fathom with an API key and to Shortcut with an API token.
The default team you set under Story defaults, if any, starting in the workflow state set there. Without a default, stories are created without a team, in your first workflow's first unstarted state.
No. Action items are read when a call has them, but the summary and transcript are enough for Spectr to find requirements, bugs and decisions on their own.
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 into a Shortcut team and read their workflow state back
