How do I export my Granola notes?

There are three paths, and which one you want depends on whether you need it once or every week. For a single note, open it, use the Shared button, and choose Email: Granola opens a draft in Gmail or Outlook with the note contents already in the body, addressed wherever you like. Copy notes does the same thing through your clipboard, as markdown. For a full backup, Settings, Profile, Generate CSV produces a file with titles, summaries, and transcripts, but it is emailed to your own account address, the link lasts 24 hours, and you get one export per day, so it is a backup rather than a workflow. For automatic export after every meeting, Granola's Zapier integration has triggers for a note added to a folder and a note shared to Zapier, and Zapier sits on Granola's Business plan.

Where should I keep my meeting transcripts?

Somewhere that outlives the notetaker, and ideally in the same place as the documents the meetings produced. Notetakers are subscriptions with limited history on their free tiers, so the record of years of conversations sits inside a product you may stop paying for. A note app like Notion or Obsidian is a common destination and works fine, but it keeps the notes separate from the contract, invoice, or statement they relate to, which is where the questions actually come from later. The practical test is whether you can ask a question, like what rate you agreed with a particular client and what you then invoiced, and get an answer without knowing which app to look in. That points toward a searchable document archive rather than a second notes app.

Can I email meeting notes into Granite?

Yes. Every Granite vault has its own private email-in address, something like jane-maple-otter@in.granite.co, and anything sent to it is saved into that vault. Attachments run through the normal reading pipeline, and an email with no attachment is saved as a text document, so a pasted markdown summary works as well as an attached PDF or TXT transcript. Granite reads the notes, summarizes them, and files them alongside the other documents about that client or project. The address is a credential, so keep it private; if it leaks you can regenerate it in Settings and the old one stops working immediately. Email-in is part of Granite Paid, which is $99 a year.

Does Granite record or transcribe meetings?

No, and it is not planned. Granite does not join calls, record audio, or produce transcripts. It is the archive the notes land in, not the microphone that captures them. Keep using Granola, Fathom, Otter, or whatever your team already runs, and send the output to Granite so it sits with the contracts, invoices, and statements from the same relationship. The two jobs are different products, and the notetakers are better at their half than a document vault would be.

Is there a Granola to Notion or Obsidian alternative?

Plenty of people wire Granola into Notion or Obsidian, either through Granola's own Business-tier integrations or with a hand-rolled sync script, and if you already work in one of those it is a sensible choice. The alternative worth considering is sending the notes to a document archive instead of a notes workspace, because most later questions span both the meeting and the paperwork that followed it. Email is the most durable route: it works from every notetaker, it does not break when a vendor changes an API, and it needs no script to maintain. In Granite that means forwarding to your vault's email-in address, after which the notes are searchable next to everything else you have filed.

Which notetaker export paths are free?

Sharing a single Granola note by email works on its free Basic plan, and so does Copy notes. Fathom's free plan covers unlimited recording and transcription, and Copy Summary lets you paste the notes into an email at no cost. Otter's free Basic plan exports TXT and MP3, which is enough to attach a transcript to an email, though PDF and DOCX need Otter Pro and only the 25 most recent conversations are kept. The Apple Notes call recorder is free where it is available, which excludes the EU and a number of other countries. The parts that usually cost money are the automatic ones: Granola's Zapier integration is on its Business plan, and on the Granite side email-in and Ask are part of Granite Paid at $99 a year.

How to export your meeting notes

Notes stranded in the notetaker

AI notetakers solved the part of meetings everyone hated. You stop typing, you pay attention, and a few minutes after the call there is a clean summary with the decisions, the numbers, and the things you promised to do. Granola, Fathom, and Otter are all genuinely good at this, and none of what follows is a complaint about the notes themselves.

The problem shows up three months later. The notes are still in the notetaker, in a reverse-chronological list of every call you have taken since you installed it, titled whatever the calendar invite was called. The contract that came out of that meeting is in your document vault. The invoice is in your accounting tool. The signed statement of work is in your email. The one record of what was actually agreed, as opposed to what was later written down, sits in a fourth place that nothing else can see.

That split matters more than it sounds. The question you ask later is almost never "what did we say in the June 4 call." It is "what rate did we agree with Northwind, and when." Answering it means checking the contract, then the invoice, then hunting through a notetaker's search box for a meeting you cannot quite name. Every one of those is a different app with a different search, and the notetaker is the one most likely to have quietly aged the meeting out of view.

There is a second, more practical reason to get the notes out: the notetaker is a subscription. If you stop paying, or the company pivots, or you switch to whatever comes next, the record of years of conversations is held by a product you no longer use. Notes about your own business should outlive the tool that took them. That is the same argument as not treating your inbox as a filing system, applied to a newer kind of inbox.

What is worth keeping

Not every meeting deserves an archive entry, and forwarding all of them is how you turn a useful record into noise. A useful filter: keep the meetings that have a paper trail attached, or that will need one later.

Client and vendor calls. Scope, price, timeline, and the promises on both sides. These are the notes that belong next to the engagement letter and the invoice.
Anything financial or legal. Conversations with an accountant, a lawyer, an insurance adjuster, a lender, a contractor. The document that follows the call almost always references the call.
Medical and care conversations. Appointment summaries and the decisions made in them, especially for anyone whose care you help manage.
Anything with a number in it. A rate, a deadline, a deductible, a quantity. These are the details you will need to check exactly once, eighteen months from now, and will not remember.

What to leave behind: internal standups, recurring one-on-ones, and the meetings whose entire value expired the same week. Those are what the notetaker's own history is for. The archive is for the conversations that a document later depends on.

One more choice worth making up front: the summary or the full transcript. The summary is what you will actually read, and it is what most notetakers send when you share by email. The full transcript is what you want when the exact wording matters, which for a handful of conversations a year it does. Sending both is fine, and costs you nothing but a second document.

Getting them out, app by app

Every notetaker can get your notes into an email. The differences are how much text actually travels, whether the recipient needs an account, and which plan the automatic version sits behind. Here is where each one stands as of September 2026. Plans and menus move, so treat this as the shape of the answer rather than a screenshot.

Granola

Open a note, use the Shared button, and choose Email. Granola opens a draft in Gmail or Outlook with the note contents already in the body, and you address it to whatever you like. There is also Copy notes, which puts the AI summary on your clipboard as markdown, so pasting into a new email works just as well. Both are the summary, not the raw transcript.

Granola's own docs do not gate sharing behind a plan, so the manual path works on the free Basic plan. The automatic path does cost money: Zapier is a Business-tier integration ($14 per user per month at time of writing), and it exposes two triggers, "Note Added to Granola Folder" and "Note Shared to Zapier." The folder trigger is the useful one, because it lets you drop the meetings worth keeping into a single folder and have only those forwarded.

One thing not to plan around: the bulk CSV export under Settings, Profile, Generate CSV. It includes titles, summaries, and transcripts, but it is emailed to your own account address, the link expires in 24 hours, and you get one export per day. It is a good backup and a bad pipeline.

Fathom

In a call recording, the Share button under the meeting title takes any email address, and link permissions can be set to anyone with the link. That gets a Fathom link into an inbox rather than the notes themselves, so if what you want is the text, use Copy Summary and paste it into an email. That is the version we would trust in an archive, because a link is only as durable as the account behind it.

Fathom also has an auto-share setting that sends the summary (or summary and recording) after every meeting to everyone on the calendar invite. If you already add a shared address to your own invites, that is a route worth testing with one meeting before you rely on it. For the reliable automatic version, Fathom's Zapier app has six triggers, including New Transcript and New AI Summary, which is the cleanest "every meeting, no thinking" setup of any tool here. Fathom's free plan includes unlimited recording and transcription, and Fathom's official plan comparison says its personal-use Zapier integration is included on both Free and Premium.

Otter

Otter is the one where the obvious path does not work. Sharing a conversation by email sends a link that requires an Otter login, so pointing it at an archive inbox gets you a sign-in page instead of a document.

Use export instead. On the free Basic plan you can export TXT and MP3, which is enough: a TXT transcript attached to an email is a perfectly good document. PDF and DOCX exports need Otter Pro, and bulk export needs Business. Basic also keeps only your 25 most recent conversations, which is its own argument for moving the ones that matter somewhere permanent. For automation, Otter's Zapier app has a single trigger, New Recording.

The Apple Notes call recorder

Recorded calls land in a Call Recordings folder in Notes, with the transcript attached. In the transcript view you can Add Transcript to Note or Copy Transcript, and pasting that text into an email is the path we would use. Sharing the recording itself is less predictable, and there is no automation hook, so this one stays manual.

Worth knowing before you build a habit on it: call recording is not available in the EU or in a long list of other countries, and transcription is limited to certain regions and languages. It is free where it works, because it is part of the operating system rather than a subscription.

Where the notes should land

Most people export their notes into a note app: Notion, Obsidian, Apple Notes, a folder of markdown files. It works, and if you already live in one of those, it is a reasonable answer. It also recreates the original problem one level down, because the notes are now in a fifth place, still nowhere near the contract and the invoice, and still organized by whatever folder discipline you can sustain.

The better test is the one you will apply later: can you ask a question and get the answer, without knowing which app the answer is in? That points at the place where the rest of the paperwork already lives. Meeting notes belong in the same archive as the documents they produced, filed against the same company, the same project, and the same year.

Granite is built for exactly that shape: you send a document in, it gets read and filed automatically, and later you ask a plain-English question and get the answer with a citation to the source. A set of meeting notes is just another document to it. Forward the notes and they are read, summarized, and grouped with the other documents about that client or project, which is the part that makes the answer to "what did we agree with Northwind" a single result instead of a three-app search.

The forward-to-an-address method

The simplest way to move notes out of any notetaker is the oldest one: email. Every tool in this guide can put your notes in an email, either directly or through an automation step, and email is the one integration that never breaks when a vendor reshuffles its API.

Every Granite vault has its own private email-in address, something like jane-maple-otter@in.granite.co. Anything you send to it is saved into that vault. Attachments run through the normal reading pipeline, and an email with no attachment is saved as a text document, so a markdown summary pasted into the body works exactly as well as a PDF. Multiple vaults get multiple addresses, so client notes can go to the business vault and nothing else has to move.

01
Copy your vault's email-in address
In Granite, open Settings, then Email-in, and copy the private address for the vault you want the notes in. It looks like jane-maple-otter@in.granite.co.
02
Send one meeting to it by hand
Use your notetaker's share or export option and send a single set of notes to that address. Confirm it lands and looks right before you automate anything.
03
Make it the default
Set the notetaker to send every meeting there, or wire it up in an automation tool so the forward happens without you.
04
Ask about it later
The notes are a document now, filed alongside the contract, invoice, or statement from the same relationship, and answerable in plain English.

Four moves, and only the first three take any effort. Step two is the one people skip; send a single meeting by hand and look at the result before you route a year of calls into it.

Two honest notes about the address. First, it is a credential: anyone who has it can add documents to that vault, so keep it out of shared docs and group threads. If it ever leaks, you can regenerate it from Settings, and the old one stops working immediately. Second, email-in is part of Granite Paid, which is $99 a year. Granite Free holds 25 documents and does not include email-in or Ask, so this particular workflow is a paid one on our side too. We would rather say that here than in a footnote after you have set up the forwarding rule.

Automating it

Sending notes by hand is fine for the handful of meetings a month that matter, and honestly it is the version most people should start with, because it keeps you deciding what is worth keeping. If you want it to happen without you, there are two ways.

Let the notetaker send it. If your tool can email a summary automatically after every meeting, point that at your email-in address and you are done. This is the version with the fewest moving parts.

Or put an automation tool in the middle.In Zapier, the shape is a two-step Zap: your notetaker's new-meeting trigger, then the Email by Zapier action, Send Outbound Email, addressed to your email-in address with the notes in the body. Two steps is what Zapier's free plan allows, so the glue itself can be free even when the trigger app is not. The caps are the thing to check: Zapier's free plan allows 100 tasks a month and five outbound emails a day, and paid plans cap outbound email at ten an hour. That is plenty for real meetings and not enough for a firehose.

The middle step also buys you a filter, which is worth having. Forward only the meetings with a client name in the title, or only the calls over fifteen minutes, instead of every standup you have ever taken.

Either way, check the first few results in your library before you trust it. Automations are cheap to set up and easy to forget, and the failure mode you want to avoid is discovering a year later that every meeting landed with the same generic title.

What changes once they are filed

The payoff is not that the notes are backed up. It is that the meeting stops being a separate kind of thing. Once the notes are in the same archive as the paperwork, they answer questions together.

The conversation sits next to its documents. The kickoff call, the engagement letter, and the first invoice end up in the same place, because they concern the same client.
Questions cross the boundary."What rate did we agree with Northwind, and what did we actually invoice" is one question against one archive, not a document search plus a notetaker search.
The record outlives the tool. Switch notetakers next year and everything you already forwarded is still yours, in a vault you can export whole at any time.
Old meetings stay findable.Notes from three years ago are as searchable as this morning's, without scrolling a history list.

What Granite does not do

Granite does not join your calls, does not record audio, and does not transcribe anything. There is no bot to admit to the meeting and no plan to build one. Your notetaker is the microphone; Granite is the filing cabinet, and the two jobs are genuinely different products.

That means this workflow depends on a tool you already pay for, and we are fine with that. Granola, Fathom, and Otter are better at capturing a conversation than a document vault is ever going to be. What none of them are built to do is hold ten years of your paperwork and answer a question that spans a contract, an invoice, and the call where the terms were set. That is the part we are good at.

So the honest version of the pitch is narrow: keep using the notetaker you like, and give its output somewhere permanent to land. If that is a folder of markdown files you maintain by hand, that is a real answer too. If you would rather the filing happened without you, that is what Granite is for.

How to export your meeting notes (and where to keep them after)