Granola to Linear

Turn Granola notes into Linear issues, natively

Right now, getting Granola notes into Linear means a Zapier automation or a community script that watches Granola's local cache. Spectr replaces both. It talks to Granola and Linear directly, reads the whole note and transcript, pulls out a structured spec, and drafts a proper Linear-ready story for each item with acceptance criteria, priority and an estimate. Nothing is created until you approve it.

How it connects

Granola: API key. You generate a key in Granola 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

Granola gates API access by plan, so a Granola Business or Enterprise subscription is required to connect.

Notes in, a reviewed backlog out

The scripts and Zaps that fill this gap all work the same way: one action item becomes one thin issue, straight away, unreviewed. That is a to-do list in Linear, not a backlog. Spectr reads the note alongside the Notion docs, Figma files and repos you pinned, so the story names your real features and the code that already exists. Several stories from one requirement get nested under a parent, and the whole set waits on a review page until you say yes.

What Spectr reads from Granola

Note summary: Granola's enhanced note - the summary it writes from the call - is imported as the leading section, ahead of the transcript.
Full transcript: The transcript is fetched alongside the note and speaker-attributed, distinguishing your own audio from the other participants'.

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 Granola, generate an API key (Business or Enterprise plan required).
Choose Granola, 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 Granola. 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

How is this different from the Granola-Linear Zap?

The Zap copies an action item into an issue. Spectr reads the full note and transcript, gathers context from your other connected tools, produces requirements, bugs and decisions as separate items with acceptance criteria, and requires human approval before publishing.