> ## Documentation Index
> Fetch the complete documentation index at: https://docs.granola.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Import meeting transcripts with your AI assistant

> Bring past meetings from Zoom, Gong, Otter, Fathom, Google Meet, Notion, Wispr Flow and Claude into Granola by asking Claude, ChatGPT or another AI assistant connected to Granola MCP.

Ask an AI assistant connected to [Granola MCP](https://docs.granola.ai/help-center/sharing/integrations/mcp) to bring your past meetings from another tool into Granola. Each meeting becomes a private note with its transcript, and Granola writes a summary for it.

# What you can import

Import the meeting's full transcript, not its summary, recording or video. Each transcript file can be up to 1 MB.

| Import from | What your assistant uses |
| - | - |
| **Zoom** | The **Audio transcript** (.vtt) of a cloud recording, from **Recordings & Transcripts > Cloud recordings**. Needs cloud recording and audio transcripts turned on in a paid Zoom plan. |
| **Gong** | **More actions > Download transcript** (.txt) on the call. |
| **Otter** | **Export > TXT** on the conversation. Works on Otter's free plan. |
| **Fathom** | **Copy Transcript** on the call, saved as a .txt file. For many meetings, your assistant can fetch them with a Fathom API key from **User Settings > API Access**. |
| **Google Meet** | The transcript Google Doc, downloaded with **File > Download > Plain Text (.txt)**. |
| **Notion** | An AI Meeting Notes transcript copied into a .txt file. For many meetings, your assistant can fetch them with a Notion internal integration. Needs a Notion Business or Enterprise plan. |
| **Wispr Flow** | Your assistant signs in to Wispr Flow in your browser and fetches the meetings itself. |
| **Claude** | A meeting transcript you already have in a Claude chat, such as one you pasted or attached. Ask Claude to save it to Granola, and the note is marked **Imported from Claude**. |

Only meetings that were transcribed at the time can be imported. Turning on transcription in the other tool now won't create transcripts for old meetings.

# Before you start

* **Connect Granola to your assistant.** Follow [How to connect](https://docs.granola.ai/help-center/sharing/integrations/mcp#how-to-connect) in the Granola MCP guide. Sign in with the Granola account and workspace you want the notes in.
* **Use an assistant that can run code and read files on your computer**, such as Claude Code, Claude Desktop or ChatGPT. In Claude Desktop, allow Claude to access your files and run code.
* **On Enterprise**, your admin must turn on the **Read transcripts** and **Edit notes** [MCP permissions](https://docs.granola.ai/help-center/sharing/integrations/mcp#permissions).

# Start an import

1. Start a new chat in your assistant with Granola turned on.
2. Ask it to import your meetings, naming the tool they're in. For example:
   * *Help me import my past meetings from Otter into Granola.*
   * *Import my Gong calls from October into Granola.*
3. Follow its lead. Your assistant will:
   * Ask whether you want all your meetings or a date range.
   * Walk you through any export steps, and ask where the files are saved.
   * Ask for each meeting's title and start time if the export doesn't include them. It won't guess a date.
4. Your assistant uploads each transcript to Granola, then tells you how many meetings were imported, are still processing, or failed.

Your assistant moves transcript files with code, so you don't need to paste transcripts into the chat. If it needs an API key for Fathom or Notion, it keeps the key in its local script. Don't paste API keys into the chat.

## If your assistant can't run code

If your assistant can't run code, or its network blocks the upload, import the meetings from the Granola desktop app instead:

* **Many meetings:** attach your export to a chat with an assistant that can run code on attachments. It converts the export into a file named `granola-import.jsonl`. Upload it in **Settings > Import meeting history > Upload an import file**. That page has a request you can copy into your assistant.
* **One transcript:** paste it or choose its file in **Settings > Import meeting history > Import a transcript**.

If an upload stops partway, for example at the daily limit, upload the same file again later. Meetings already imported are skipped.

Meetings in an import file aren't matched with meetings your assistant uploaded directly, so import each meeting one way only.

## What each meeting can include

Your assistant writes these fields for each meeting in an import file. When it uploads files directly, it sends the title and start time, plus attendees and the calendar event when it knows them.

| Field | Required | What it is |
| - | - | - |
| `title` | Required | The meeting title, up to 1,000 characters. |
| `meeting_started_at` | Required | When the meeting started, with its timezone, for example `2026-10-01T09:30:00-04:00`. Must be between 2000 and tomorrow. |
| `transcript` | Required | The whole transcript as text, one line per speaker turn, such as `Alice Smith [01:23]: Let's start with the roadmap.` Up to 200,000 characters. |
| `source` | Recommended | The other tool's name and its ID for the meeting, such as `{"app": "otter", "meeting_id": "…"}`. Granola uses it to recognise the meeting if you import it again. |
| `attendees` | Optional | Names and email addresses of people in the meeting, up to 500. Only people whose email address is in the export. |
| `meeting_ended_at` | Optional | When the meeting ended, in the same format. Must be after the start. |
| `meeting_platform` | Optional | Where the meeting took place, such as Zoom, Google Meet, Teams, Webex, Slack huddle, phone or in person. Other values are recorded as other. |
| `calendar_event` | Optional | The meeting's event in your Google or Outlook calendar: `provider` (`google` or `microsoft`), `calendar_id` and `event_id`. Links the note to that event and adds its attendees. |

Two things to watch:

* **Attendees are never guessed.** Your assistant only adds people whose email address it has from the export or your calendar. It won't make up an address from a speaker's name, so attendees without one are left off.
* **A calendar event is optional, but a wrong one fails the meeting.** Meetings import fine without one. If your assistant does add one, it must be in a calendar synced to Granola, and for a recurring meeting it must be that day's occurrence, not the series. If Granola can't find the event, that meeting isn't imported, so your assistant should leave it out rather than guess.

# Limits

* **Size:** up to 1 MB per transcript file, or 200,000 characters per transcript in an import file or pasted into Granola.
* **Daily limit:** 50 new imports in a rolling 24 hours on Basic (Free), and 500 on paid plans. The limit applies across all your workspaces. Retrying an import doesn't count again.
* **Summaries take time:** Granola writes summaries in the background. For a large import, the last summaries can take a few hours. The transcripts are available straight away.

# What you get

Each imported meeting becomes a note in your active workspace:

* **Private:** only you can see it, and it has no share link. [Share it](https://docs.granola.ai/help-center/sharing/sharing-notes.md) or add it to a folder like any other note.
* **Dated to the meeting:** it appears in your notes list on the day the meeting took place, not the day you imported it.
* **Marked as imported:** a small badge on the note's icon. Hover it to see where the note came from, such as **Imported from Otter**.

![Imported meetings in the Granola notes list, each with an import badge and marked Private](https://mintcdn.com/granola-c3940166/V_Z5zT4OyfIYMw74/help-center/assets/mcp-import/imported-notes-list.png?fit=max\&auto=format\&n=V_Z5zT4OyfIYMw74\&q=85\&s=7f7a6c8155957204ab763bbbc7b95eeb)

Open the note to see the transcript. Lines labelled with your name are shown as yours. **Analyzing transcript** shows while Granola writes the summary.

![An imported meeting note showing its transcript while Granola writes the summary](https://mintcdn.com/granola-c3940166/V_Z5zT4OyfIYMw74/help-center/assets/mcp-import/imported-note-transcript.png?fit=max\&auto=format\&n=V_Z5zT4OyfIYMw74\&q=85\&s=a8515fd5edb154c999e21a2eb21aabe5)

How the transcript looks depends on the source:

* **Import files, pasted transcripts and Zoom:** split into separate lines by speaker and time.
* **Gong, Otter, Fathom, Google Meet, Notion and Wispr Flow:** kept as one block of text, with the original speaker names, and timestamps when the export has them, inside it.

Importing the same meeting again returns the existing note instead of making a duplicate. It doesn't update the existing note, and it won't bring back a note you deleted. An edited transcript file uploaded by your assistant is imported as a new note.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.