> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/settings/call-recorders/notion.md).
# Notion
If your meeting notes already live in Notion, connecting it brings the Notion AI summaries and transcripts into Zero rather than asking you to move them. Notes are matched to their calendar event, transcripts are stored speaker by speaker, and action items can become Zero tasks.
## Set up the integration
{% stepper %}
{% step %}
### Open the Notion setup in Zero
Go to **Settings → Connections → Notetakers** (the **Meeting notetakers** page). Under **Available notetakers**, click the Notion tile.
{% endstep %}
{% step %}
### Select a default meetings database in Notion
In Notion, go to Settings > Notion AI > Meeting notes > Select default meetings database. Make sure all your meeting notes flow into this database, then grant Zero permission to access it when you connect.
{% endstep %}
{% step %}
### Choose whether action items become tasks
The wizard includes a "Turn Notion action items into Zero tasks" toggle. It is on by default; turn it off if you only want notes and transcripts. After connecting, the same setting is available on the integration's settings page as "Turn action items into tasks".
{% endstep %}
{% step %}
### Grant Zero access to the meetings database
Click "Connect with Notion" and authorize Zero in the Notion OAuth flow. Notion asks you to authorize Zero as your user so it can find meeting notes for meetings you attended; Zero only requests read access to your content. Once authorized, previous and new Notion AI meeting notes sync to your workspace, and Notion appears under "Connected" on the Meeting notetakers page showing the connected Notion workspace name.
{% endstep %}
{% endstepper %}
## What syncs
* **Meeting summaries and notes** are attached to the matching calendar event in Zero as the event summary.
* **Transcripts** are stored on the calendar event, segmented by speaker.
* **Action items** are extracted from the meeting summary and converted into Zero tasks when the "Turn action items into tasks" toggle is on.
* **Previous meeting notes** are back-synced once right after you authorize the connection.
Only Notion AI meeting notes whose transcription has finished are synced; trashed notes are skipped.
Zero matches each incoming meeting note to a calendar event you attended by the meeting title and start time (within 30 minutes of the Notion meeting's calendar-event or recording start time). Meeting notes that cannot be matched are still stored and linked to the event later when a match is found.
## Sync schedule
After the initial back-sync, Zero checks every five minutes for calendar meetings of yours that ended at least five but less than ten minutes before the check. If a meeting qualifies, Zero immediately queues a sync of Notion meeting notes edited in the last two days. For example, a meeting ending at 12:00 is picked up at 12:05, with no added delay; actual start time depends on worker availability. Adjacent checks do not overlap. You can also trigger a sync manually from the connected integration's menu on the Meeting notetakers page: "Sync last 7 days" re-syncs recently edited notes, and "Sync previous meetings" re-runs the full history sync.
## Disconnect
To disconnect, open the connected integration's menu on the Meeting notetakers page and click "Disconnect". Your meeting transcripts and summaries will no longer be synced with Zero. To re-authorize an existing connection (for example after changing the database access grant), use "Reconnect Integration" on the integration's settings page instead.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.zero.inc/settings/call-recorders/notion.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
