TranscriptExporter for Granola documentation

Getting started

TranscriptExporter for Granola is a Chrome extension. A license is $29 once, works forever, and includes every export format. There are two ways people arrive:

Your license key

Keys look like GRANOLA-XXXXXXXX-XXXXXXXXX. Open the extension, paste the key, and click Validate License.

• One license activates on up to 3 devices.
• Your key is printed in the README.pdf of every export, so you always have a copy.
• Lost it entirely? Email hello@transcriptexport.com and it will be resent.

Browser support

Google Chrome 88 or newer. The extension does not run on Firefox, Safari, Edge or any mobile browser.

Creating your Granola API key

The extension connects to Granola with an API key that you create yourself. Granola offers API keys on its Business and Enterprise plans. Setup takes about a minute and you only do it once. On Enterprise plans, a workspace admin may need to enable API access for members first.

1. Open the Granola desktop app and go to Settings.
2. Open Connectors, then API keys.
3. Under Personal API key, create a new key and tick its notes access checkboxes (see below), then copy the key.
4. Paste the key into the extension and click Save and connect.

Notes access: Personal, Public, or both

Your key decides what you can export. When you create a Personal API key, Granola shows two checkboxes. Tick one or both:

Workspace API keys (admins)

Next to Personal API key, workspace admins also see Workspace API keys. There are no options to pick: click create and Granola issues the key. A workspace key belongs to the workspace rather than to you, never expires, and covers the workspace's public notes, which makes it the right key for a standing team backup that survives staff changes.

Running an export

1. Click the TranscriptExporter icon in your Chrome toolbar.
2. Set filters if you want to narrow things down (all optional).
3. Choose your content and formats.
4. Check the estimate line, then click export.
5. The export runs in the background. Keep browsing, or close the popup, and a ZIP downloads automatically when it finishes.

Filters

Content

Checkboxes control what each exported file includes:

• AI notes - Granola's generated summary for the meeting.
• Full transcript - the complete transcript with timestamps.
• Attendees and emails - who was in the meeting.
• Calendar details - date, time, duration, organizer.
• Folder names - which Granola folders the meeting belongs to.

Formats

Pick one format or several. With several selected, each format gets its own folder inside the ZIP.

What's in your export

Every export is a ZIP named like granola-notes-2026-08-14.zip, with README.pdf at the root so it is easy to find.

granola-notes-2026-08-14/
├── README.pdf              summary of this export, plus your license key
├── txt/
│   ├── Weekly_Product_Sync_Aug_12_2026_a1b2c3.txt
│   └── Client_Kickoff_Aug_10_2026_d4e5f6.txt
├── md/
│   └── ...                 same meetings, Markdown
└── json/
    └── ...                 same meetings, structured JSON

Each file follows the same layout:

1. A metadata header: title, date, duration, owner, attendees, organizer, folders, and the Granola URL.
2. An AI NOTES section: Granola's summary for the meeting. In Markdown files it keeps Granola's own headings and formatting.
3. A TRANSCRIPT section: every line with an elapsed [MM:SS] timestamp and a speaker label.

Speaker labels

Speaker labels come straight from Granola. The extension never invents names. What you see depends on what Granola knows about each line:

Granola transcripts without speaker tags only distinguish your microphone from other people's audio, so on many desktop recordings the transcript alternates between "Name (me)" and "Other participant". That is exactly how Granola stores it, and your export reflects it faithfully.

Which meetings appear

The export list contains every meeting your API key can see that has a finished AI summary. That is a Granola API rule, not an extension setting:

• A meeting that just ended appears once Granola finishes generating its summary, usually within a few minutes.
• A meeting recorded without a summary (for example a cancelled processing run) will not appear.

Cloud backup with Granola Pro

Granola Pro ($6.99/month or $69/year) backs up every new meeting to storage you own, automatically. Connect Google Drive or Dropbox in Settings and the extension checks Granola every 10 minutes, uploading anything new. A meeting still processing in Granola when a check runs is picked up as soon as Granola finishes it, never skipped.

• Upload on export also copies your one-time exports to the same cloud folder.
• Backups mirror your saved export formats and include the full notes and transcript.
• Manage or cancel the subscription anytime from Settings.

Obsidian vault sync

Every Granola meeting can land in your Obsidian vault as a Markdown note, about ten minutes after the call ends, with nothing to click. Part of Granola Pro.

How it works

The extension pairs with TranscriptExporter Sync, our free companion plugin in Obsidian's community store. The plugin runs a small receiver inside Obsidian that listens only on your own computer (127.0.0.1). The extension fetches new meetings from Granola and hands them to the plugin, which writes one .md file per meeting into your vault. No cloud relay, no account, and your meeting data never touches our servers.

Setting it up

Three clicks, under a minute.

1. In the extension open Settings, find Obsidian Vault, click Set up. Chrome asks permission to talk to Obsidian on your computer. Allow it.
2. Obsidian opens on our plugin's page. Click Install, then Enable. The extension notices by itself.
3. Obsidian shows a pairing request naming your vault. Click Allow. Done.

Sync starts immediately with your last 24 hours of meetings, then keeps itself current from there.

What lands in your vault

• One Markdown file per meeting. Granola's AI notes on top, the full timestamped transcript below.
• A metadata block at the top with the date, attendees and source link, which Obsidian reads as properties.
• Files go into a Granola folder in your vault. Rename it in Settings, and nested paths like Meetings/Granola work.

Your edits are safe

A file already in your vault is never modified or overwritten. Add tags, add links, rewrite the whole note. The next sync leaves your version alone. Want a fresh copy of one meeting? Delete its file and it returns on the next sync.

Timing

The extension checks every 10 minutes while Chrome is running. Granola needs a couple of minutes after a call before the note is ready in their API, so a meeting typically appears within 10 to 15 minutes of ending. Long meetings are covered too. The sync keeps rechecking a trailing window, so a meeting that finishes processing late is never missed. If Obsidian is closed, notes simply wait and land on the first check after it reopens.

Changing vaults

Obsidian installs plugins per vault. To sync into a different vault, open that vault in Obsidian and enable TranscriptExporter Sync there, then click Change vault in the extension's Obsidian settings and approve the new pairing. Files already synced stay where they are.

Privacy and the plugin

• The plugin listens only on 127.0.0.1. Nothing on your network or the internet can reach it.
• Every delivery is authenticated with a pairing key created on your machine.
• The plugin makes no outbound requests at all. No telemetry, no phoning home.
• It is MIT licensed with public source at github.com/TranscriptExporter/transcriptexporter-sync, and Obsidian's directory verifies every release is built byte for byte from that source.

If something looks off

Nothing appears in the vault. Obsidian must be open with the plugin enabled, and Chrome must be running (the extension does the fetching). Check the plugin's settings in Obsidian. The status line should read Running.

The plugin says the port is already in use. Another app, or a second vault with the plugin enabled, holds port 27125. Disable the plugin in other vaults, or change the port in the plugin settings and match it under Advanced in the extension.

The pairing request never appears in Obsidian. Update the plugin (in Obsidian go to Settings, Community plugins, check for updates). Plugin versions before 1.1.0 pair with a copied key instead, and the extension shows that fallback on its own.

Denied the pairing by accident. Click Try again in the extension and approve in Obsidian.

Troubleshooting

API key rejected (401)

• Check for copy-paste mistakes. Granola API keys start with grn_.
• The key may have been revoked in Granola. Create a fresh key under Settings, Connectors, API keys, and paste it into the extension.
• API keys stop working if your workspace drops below a Business or Enterprise plan.

Rate limits

Handled automatically. The extension paces its requests under Granola's limits, and if Granola asks it to slow down mid-export, it waits and resumes on its own. You never lose progress. Very large exports simply take a little longer.

A meeting is missing from the export

• Most common cause: its AI summary has not finished yet. Wait a few minutes and export again.
• Check your filters. A date range, folder, or keyword filter may be excluding it.
• Check your key's notes access. A Personal-notes-only key cannot see teammates' meetings; you need Public notes access for that.
• A workspace key that finds 0 meetings usually means nothing has been shared workspace-wide yet. Workspace keys only see public notes and the Team space, never anyone's private notes. Share a note into the Team space and it will appear.

"Invalid License" error

• Double-check the key for typos. It must start with GRANOLA-.
• Ensure you have not exceeded the 3-device limit.
• Contact support if you purchased within the last 24 hours.

Extension not working at all

1. Verify the extension is enabled in chrome://extensions/.
2. Restart Chrome completely.
3. Remove and reinstall the extension from the Chrome Web Store. Your license reactivates with the same key.

Support

Email hello@transcriptexport.com for technical issues, license problems, or general questions. We typically respond within 24 hours on business days.

When contacting support, please include:

• Your license key (first 10 characters)
• Chrome version
• A description of the issue, with screenshots if applicable

You can also browse the FAQ and the general support center.

Changelog