> 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.md). # Notetakers What was said on a call is the most valuable record you have of a deal, and it usually sits in a tool nobody else opens. Zero pulls summaries, transcripts and action items out of the notetaker you already use and attaches them to the matching calendar event — which is also what makes follow-up drafts and meeting prep possible. Each person connects their own, in **Settings → Connections → Notetakers**: pick a tile under **Available notetakers**, run the setup wizard, and it appears under **Connected** with its sync status and last sync time. Every wizard has a **Turn action items into Zero tasks** toggle, on by default. Turn it off if you only want summaries and transcripts. ## Supported notetakers | Notetaker | Connection | What syncs | Sync cadence | Action items → tasks | | ----------------------------------------------------- | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | [Circleback](/settings/call-recorders/circleback.md) | Circleback automation webhook + OAuth (required for back-sync) | Meeting notes, per-speaker transcripts, action items | Webhook after every meeting; previous meetings back-synced once after OAuth | Yes (toggle) | | [Fathom](/settings/call-recorders/fathom.md) | OAuth (Zero registers the webhook for you) | Meeting summaries, per-speaker transcripts, action items | Webhook as meetings end; past meetings synced right after connecting | Yes (toggle); external meetings only, skips meetings older than 7 days | | [Fireflies.ai](/settings/call-recorders/fireflies.md) | API key + `Meeting Summarized` webhook (Business/Enterprise plan) | Overview and action items in event notes, per-speaker transcript, link to audio/video recording | Webhook when Fireflies finishes summarizing; first sync imports the past two years | Yes (toggle) | | [Granola](/settings/call-recorders/granola.md) | API key from the Granola desktop app (legacy OAuth still syncs) | Meeting notes, "Me"/"Them" transcripts, action items, follow-up draft | Every 5 minutes, checks meetings ending 10–5 minutes ago and immediately queues syncs; manual 7-day/full sync | Yes (toggle) | | [Notion](/settings/call-recorders/notion.md) | OAuth (read access to your default meetings database) | Notion AI meeting summaries and notes, per-speaker transcripts, action items | Every 5 minutes, checks meetings ending 10–5 minutes ago and immediately queues syncs; initial back-sync and manual 7-day/full sync | Yes (toggle) | | [Garba](/settings/call-recorders/garba.md) | API token; optional webhook | Summaries in event notes, transcripts, action items | Hourly poll (meetings from the last 2 days); webhook syncs a meeting as soon as its summary is ready | Yes (toggle); falls back to extracting tasks from the summary when there are no action items | | [Jamie](/settings/call-recorders/jamie.md) | Personal API key + `meeting.completed` webhook (Pro plan and up) | Meeting summaries, transcripts, action items | Webhook as soon as Jamie finishes a meeting; existing meetings synced on connect | Yes (toggle) | | [Wispr Flow](/settings/call-recorders/wispr-flow.md) | OAuth (Notetaker notes and transcripts only, never dictations) | Meeting notes, transcripts, action items | Polled automatically; manual 7-day or full sync from the `⋯` menu | Yes (toggle) | They all match incoming meetings to your calendar events the same way: calendar invite ID first, then the meeting link, then title plus start time (the fallback window differs per tool — see each page). A meeting that matches nothing is still stored, and for Circleback, Granola and Notion it gets linked later if a match turns up. ## What happens with a synced meeting Once a meeting is matched to a [calendar event](/features/calendar.md), Zero adds the summary to the event without overwriting anything already there, attaches the transcript segmented by speaker, and — with the toggle on — creates tasks from the action items, never twice for the same meeting. As soon as the transcript lands it also drafts a [follow-up](/features/home-view/generate-follow-up.md) for each of your team who attended. Those summaries and transcripts then feed the [meeting prep](/features/home-view/meeting-prep.md) Zero writes before your next call with the same people, so one connection pays for itself twice. ## Several notetakers on one meeting A meeting's **Summary** tab shows the summary Zero holds for it, which notetaker it came from, who connected that notetaker, and a link to open the meeting there. Where the tool keeps your own notes separately (Wispr Flow's "My thoughts"), they appear below the summary. Either can be added to the meeting notes with one click, without replacing what you wrote. Two people on a call can each run their own notetaker, and they do not have to be the same product. The Summary tab then offers a source picker. The first notetaker to deliver a summary is the meeting's **primary** source: its summary is the one Zero uses for follow-ups, meeting prep and AI, and it is marked with a filled star. The star next to another source makes that one primary; the meeting notes you have written are never changed by a switch. The transcript comes from whichever notetaker delivered it first; the Transcript tab says which one. ## Managing a connection Click a connected integration on the Meeting notetakers page to expand it. You will see how many meetings were found and matched, and its `⋯` menu holds **Sync previous meetings** (plus **Sync last 7 days** for most), the API key or token, and the **Turn action items into tasks** toggle. **Disconnect** stops new syncs; what has already synced stays. --- # 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.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.