Granola to Shortcut
Granola writes the note. Shortcut tracks the work. Spectr sits between them, connected to both directly: it reads the note and transcript, pulls out a structured spec, and drafts a Shortcut story with acceptance criteria and an estimate for every requirement and bug. You review the set and publish what you approve.
How it works
A call is imported from Granola. 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.
Two keys and no OAuth: a Granola API key and a Shortcut API token, each pasted into the Spectr project and stored encrypted. Revoking either one in the tool that issued it cuts Spectr off immediately.
A Granola Business or Enterprise plan, because Granola keeps its API to those tiers. On the Shortcut side, you can set a default team and starting workflow state under Story defaults once connected.
A meeting rarely produces just one kind of work. Spectr splits what it finds into requirements, bugs, decisions and action items, then drafts stories for the requirements and bugs, each with the right Shortcut story type and estimate instead of a generic task. Stories arrive in your default starting state, and a status refresh reads their state back so what is finished in Shortcut is what Spectr thinks is finished.
Before drafting, Spectr reads the project's requirements, its memory on paid plans, and the Notion, Figma or GitHub sources you connected. A note that says "same as the onboarding flow" becomes a story that names which onboarding flow.
If a story drafted from the note looks like one the project already has, Spectr marks it as a possible duplicate, so a request raised in two meetings does not become two Shortcut stories.
When the spec marks a task as a parent, its stories go into Shortcut under a parent story. Spectr never creates epics, so the epic structure stays the one your team built.
In Spectr, open the project you want to connect and go to Integrations.
In Granola, generate an API key (Business or Enterprise plan required).
Choose Granola 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 Granola. Spectr gathers project context, extracts a structured spec, and drafts a story for each requirement and bug.
Go through the drafts from the note, approve the ones you want, and publish. Shortcut receives them as typed stories in the starting state you set.
Anything else? Email hello@crowdlinker.com and a person will answer.
No. Granola lists Jira and Linear only through Zapier, and Shortcut not at all. Spectr connects to Granola with an API key and to Shortcut with an API token.
Spectr keeps the last workflow state it read instead of wiping the story, so a deletion in Shortcut does not erase the story's history in Spectr.
Spectr compares each new story with the project's existing ones, rejected stories included, and flags likely duplicates for review. You can reject a flagged story or mark it as a duplicate before anything reaches Shortcut.
Use case
Import a call, get a draft backlog, approve what is right
Native Granola import - no Zapier, no scripts - straight through to Jira, Linear or Shortcut
Publish stories into a Shortcut team and read their workflow state back
Fathom to Shortcut
Granola to Jira
Granola to Linear
Read.ai to Shortcut
Fireflies.ai to Shortcut