# Send meeting recaps to Notion. Dimmy Help.

> Send meeting recaps to Notion. Step-by-step help for Dimmy, the native voice dictation app for macOS, Windows, and Linux.

Source: https://dimmy.app/help/integrations-notion/

[← Back to Help center](https://dimmy.app/help/)

Integrations

# Send meeting recaps to Notion

Dimmy has a built-in Notion integration. Connect once with your own integration token, pick a destination page or database, then send any recap with one button (or auto-send every meeting).

Notion is one of the most popular places to keep meeting recaps. Dimmy talks to it directly: it uploads your recap markdown to a page or database you choose, using your own Notion integration token. No Dimmy server sits in the middle, and it works the same on Windows and macOS.

image · placeholder

Notion page receiving a Dimmy-generated meeting recap

## Connect Notion (one-time setup)

Dimmy uses a private (internal) Notion integration token. The Connect wizard walks you through it. Open Dimmy → Settings → Integrations → Notion → Connect Notion.

## Step 1: prepare your Notion workspace

1. Open the Notion integrations page (the wizard has an Open Notion integrations button, or go to notion.so/my-integrations).
2. Click New integration, name it Dimmy, pick your workspace, save.
3. Copy the Internal Integration Secret. That's your token (it looks like ntn\_… on newer tokens, or secret\_… on older ones).
4. Open the Notion page or database you want recaps to land in. Click ··· → Connections → add your new Dimmy integration. Until you do this, Dimmy sees zero pages.

warning

This last step is the one people miss. The token alone grants nothing. You must add the integration to each page or database via ··· → Connections, otherwise the destination list comes back empty.

## Step 2: paste your token

1. Paste the token into the wizard's token field.
2. Click Verify. Dimmy pings Notion and shows "Connected as <bot> in <workspace>" on success.

info

Tokens stay on this device, encrypted in Dimmy's local keystore. They never appear in config.json and are never sent to Dimmy's servers.

## Step 3: pick a destination

1. Click Refresh list. Dimmy shows every page and database your integration can see.
2. Pick one from the dropdown. That's where recaps will be created.
3. If your page isn't listed, you skipped the Connections step above. Add the integration to it in Notion, then Refresh again.

Connect Notion wizard

## Send a recap

Open a finished meeting's Done view. Click the Send recap to Notion button (the Notion mark in the toolbar). Dimmy creates a new page from the recap markdown under your chosen destination and shows a confirmation with an Open in Notion button.

video · placeholder

Click Send recap to Notion on a completed meeting, then click Open in Notion to see the new page

tip

No recap yet? Click the (Re)generate recap button on the Done view first (it runs the LLM over the transcript), then send. You can also tidy the recap text before sending.

## Auto-send every meeting

If you want every recap in Notion without clicking, turn on Settings → Integrations → Notion → the auto-send toggle. When on, each meeting's recap uploads to your destination as soon as the recap finishes. When off, you send per meeting from the Done view.

## Good to know

* Free Notion accounts work. There are no per-plan API limits, only Notion's standard rate limit (about 3 requests/second).
* Only the recap markdown leaves your machine when you (or auto-send) trigger an upload. The token and destination stay on device.
* Notion parses the markdown server-side, so headings, bullets, tables, and code fences come through as real Notion blocks.
* Disconnect any time: Settings → Integrations → Notion → Disconnect. Dimmy forgets the token and destination; your Notion content is untouched.

## Bonus: dictate straight into Notion

Separate from recaps, you can dictate into any Notion text field like any other app. Click into a page, press your Dimmy hotkey, speak, release. Pair it with the Summarize style for brain dumps that become bullets. See [Long voice notes that become structured recaps](https://dimmy.app/help/use-meeting-recaps/).

## Advanced: let Claude build richer Notion pages

The built-in integration creates one page per recap. If you want Claude to do more (set page properties, file under a specific database, combine several meetings), you can connect Notion's own MCP server to Claude alongside [Dimmy's MCP](https://dimmy.app/help/integrations-mcp-claude-cli/) and ask in plain language.

* In Claude Desktop: open Settings → Connectors, add Notion's hosted MCP at https://mcp.notion.com/mcp, and sign in. (Same per-page sharing rule applies: add the integration to the pages you want Claude to touch.)
* In Claude CLI: claude mcp add --transport http --scope user notion https://mcp.notion.com/mcp

Then chain Dimmy and Notion in one prompt, for example:

text

`Read my last Dimmy meeting (dimmy_get_recent_meetings, then dimmy_get_meeting). Write a recap with dimmy_get_recap_template. Then create a Notion page in my "Meetings" database with that recap as the body, the meeting title as the title, and today's date in the Date property.`

## Troubleshooting

* Destination list is empty: you haven't added the Dimmy integration to any page. In Notion, open the target page → ··· → Connections → add Dimmy, then Refresh.
* Verify fails: re-copy the Internal Integration Secret (it's easy to grab a truncated string). Make sure you copied from the right integration.
* "Notion not connected" when sending: finish the Connect wizard first (token + destination). The Send button can't do anything without both.
* Page created but looks thin: very deeply nested markdown can flatten. Keep the recap [template](https://dimmy.app/help/custom-prompts/) to 2 levels of bullets.

tip

Want a fully hands-off loop? Turn on auto-send, set the meeting recap [provider](https://dimmy.app/help/integrations-claude-cli/) to your Claude subscription, and every meeting ends as a polished page in Notion without a click.

Was this helpful? 

## In this category

[ IntegrationsConnect Claude Desktop to Dimmy (MCP bridge)One-click wizard installs a small MCP server. Ask Claude Desktop about your meetings, dictations, and let it write recaps back into Dimmy.](https://dimmy.app/help/integrations-claude-desktop/) [ IntegrationsUse your Claude subscription via Claude CLI (no API key)If you already pay for Claude Pro, Team, or Max, route Dimmy's LLM rewrites and recaps through the local claude CLI. No API key, no per-token cost.](https://dimmy.app/help/integrations-claude-cli/) [ IntegrationsUse Dimmy's MCP server from Claude CLI (advanced)Dimmy's MCP bridge has a one-click setup for Claude Desktop. There's no built-in button for the terminal, but you can point the Claude CLI at the same binary by hand. Here's how.](https://dimmy.app/help/integrations-mcp-claude-cli/) [ IntegrationsUse your ChatGPT subscription via Codex (no API key)If you already pay for ChatGPT Plus, Pro, Team, Business, or Enterprise, route Dimmy's LLM rewrites and recaps through the local codex CLI. No API key, no per-token cost.](https://dimmy.app/help/integrations-codex-cli/) [ IntegrationsSend audio from your phone with TelegramConnect Dimmy to your own Telegram account. Record audio on your phone with any app, share it to your Telegram Saved Messages, and Dimmy transcribes it and writes a recap on your computer. Windows and macOS.](https://dimmy.app/help/integrations-telegram/)

Last updated: 2026-05-22

On this page

1. [01 Connect Notion (one-time setup)](#connect-notion-one-time-setup)
2. [02 Step 1: prepare your Notion workspace](#step-1-prepare-your-notion-workspace)
3. [03 Step 2: paste your token](#step-2-paste-your-token)
4. [04 Step 3: pick a destination](#step-3-pick-a-destination)
5. [05 Send a recap](#send-a-recap)
6. [06 Auto-send every meeting](#auto-send-every-meeting)
7. [07 Good to know](#good-to-know)
8. [08 Bonus: dictate straight into Notion](#bonus-dictate-straight-into-notion)
9. [09 Advanced: let Claude build richer Notion pages](#advanced-let-claude-build-richer-notion-pages)
10. [10 Troubleshooting](#troubleshooting)
