> 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/fathom.md).

# Fathom

Fathom connects over OAuth, with no API key to copy. Once authorized, your transcripts and notes land on the matching calendar events, and action items become Zero tasks.

{% stepper %}
{% step %}

### Go to Settings → Connections → Notetakers and select Fathom

On the **Meeting notetakers** page, click the Fathom tile under **Available notetakers**.
{% endstep %}

{% step %}

### Choose whether to turn action items into tasks

The **Turn Fathom action items into Zero tasks** toggle at the top of the setup screen is on by default.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/fathom-setup.png" alt="Fathom notetaker setup with a toggle turning action items into tasks and a Connect with OAuth button"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Click "Connect with OAuth"

Approve access in Fathom and you come back to the notetakers page with the integration **Connected**. Zero registers the webhook for you and starts syncing past meetings straight away.
{% endstep %}
{% endstepper %}

## What syncs

* **Meeting summaries** — added to the notes of the matching calendar event in Zero.
* **Transcripts** — the full per-speaker transcript is attached to the calendar event.
* **Action items** — if the toggle is on, action items from external meetings are turned into Zero tasks. Internal-only meetings and meetings older than 7 days are skipped, and tasks are not created twice for the same meeting.

Meetings match on title and start/end time. After the first sync, new recordings — yours and those shared with your team — arrive by webhook as meetings end, and Zero refreshes the OAuth token itself, so you should never have to reconnect.


---

# 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/fathom.md?ask=<question>&goal=<user_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.