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

> ## Agent Instructions
> Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems.
> Use British English (organisation, not organization).
> Every feature and integration described in these docs is available. Describe it as documented.
> Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only.
> Do not discuss commercial terms. Direct commercial questions to support@hebno.com.
> Start with /index and /get-started/quickstart.

# Fathom

> Read Fathom recorded calls, transcripts, summaries and action items in Hebno with your own access. Hebno reads only and never writes to Fathom.

The Fathom integration makes the calls Fathom records available in your client work. Ask what Contoso agreed on Tuesday's call, collect the action items from the last three check-ins, or quote what a stakeholder said about the readout date, and Hebno answers from Fathom with each call cited. Fathom is read only: Hebno never writes to it.

## At a glance

| | |
| - | - |
| **Connection** | Personal connection. Each member connects their own Fathom account with an API key. |
| **Default access** | Read only |
| **Attach** | A call's details, summary, action items, transcript or full record |
| **Search** | Hebno searches your Fathom calls when a request mentions a client, company, email domain, person or date |
| **Link** | A project links to a client email domain, such as `contoso.com` |
| **Write** | None. Hebno reads only. |

## Before you start

You need:

* A Fathom account that recorded the calls, or that is on a Fathom team the calls were shared with.
* A Fathom API key. In Fathom, open **Settings → API Access**, select **Generate API Key**, name it Hebno and copy it.
* An allowed integration. An owner or admin sets **Fathom** to **Allow** under **Admin → Connectors → Catalogue**.

Hebno sends your key in the `X-Api-Key` header and uses these Fathom API endpoints:

| Endpoint | Why Hebno needs it |
| - | - |
| `GET /external/v1/meetings` | List your calls by date, invitee domain or team, with `include_summary`, `include_action_items` and `include_transcript` when a request needs them |
| `GET /external/v1/teams` | List the Fathom teams you belong to |
| `GET /external/v1/team_members` | Show teammates on a call by name |

The key gives the same access you have in Fathom: calls you recorded, and calls shared with teams you are on.

## Connect Fathom

**1. Create an API key**

In Fathom, open **Settings → API Access**, select **Generate API Key** and copy the key.

**2. Add the key in Hebno**

Open **Settings → Connections**, find **Fathom** under **Meetings and calls** and select **Connect**. Paste the key and select **Connect**.

**3. Check the connection**

The card shows **Connected** with your Fathom email address.

Hebno reads with your own Fathom access. Keys are encrypted at rest. Select **Disconnect** at any time, or ask an admin to revoke the connection under **Admin → Connectors → Connections**. Revoking the key in Fathom under **Settings → API Access** also ends access.

## What Hebno reads

| Fathom object | Fields Hebno uses | Typical questions |
| - | - | - |
| **Meeting** | Title, scheduled and recorded times, recorded by, calendar invitees and their domains, share link | "Which Contoso calls did I record in October?" |
| **Summary** | Fathom summary in the template the recorder chose, with sections and timestamps | "Summarise Tuesday's Contoso check-in." |
| **Action items** | Description, assignee, completed flag, timestamp in the recording | "What did Sarah Chen agree to send us?" |
| **Transcript** | Speaker, timestamp and text of each line | "What did Contoso say about the readout date?" |
| **Team** | Team name and members | "Show the calls shared with the delivery team." |

![Chat reply citing a Fathom recorded call](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-fathom.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=8519c04d880c5544325d697ed58b5378)

A Fathom recorded call attached to a chat.

When Hebno reads a call, it uses the Fathom summary and action items first, then a transcript excerpt, then the call details, and the source label shows which. Hebno does not read the audio or video. Attaching a call offers **Details**, **Summary**, **Action items**, **Transcript** and **Full record** as separate files. A search returns up to three calls.

Reads are live. Hebno queries Fathom when a request needs it, and only what a reply used is stored with the conversation as its sources.

> [!WARNING]
>
> Transcript and summary excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including remarks from clients on the call.

## Hebno reads only

Hebno does not write to Fathom. It does not record or join calls, edit summaries, complete action items, create clips or change sharing. To schedule a follow-up, use [Google Calendar](https://hebno.com/docs/integrations/google-calendar.md) or [Outlook Calendar](https://hebno.com/docs/integrations/outlook-calendar.md).

```mermaid theme={"system"}
sequenceDiagram
  participant You
  participant Hebno
  participant Fathom
  You->>Hebno: Collect the action items from our last three Contoso calls
  Hebno->>Fathom: List calls with contoso.com invitees
  Fathom-->>Hebno: Three recent calls
  Hebno->>Fathom: Read summaries and action items
  Fathom-->>Hebno: Action items with assignees
  Hebno-->>You: Action list with each call cited
```

## Link a project to a client domain

Each Fathom call lists the email domains of its calendar invitees. Linking a domain marks which calls belong to an engagement, so you can ask "what did we agree last week?" without naming the call.

1. Open the project and select **Brain**.
2. Under **Linked records**, select **Link record**, then **Fathom**.
3. Enter the client's email domain, for example `contoso.com`, and select **Link**.

In chats tagged to the project, Hebno starts with calls whose invitees use the linked domain. See [Linked records](https://hebno.com/docs/projects/linked-records.md).

## Use Fathom in chat

* **Attach**: open the **+** menu, choose **Sources → Fathom**, pick a call, then pick the summary, action items, transcript or full record. Or type `/` and choose **Fathom**.

* **Ask**: name the client, domain, person or date. For example:

  > Collect the open action items from our last three Contoso calls and group them by owner.

  > What did Sarah Chen say about the readout date on the 28 October call? Quote the transcript.

  > Draft a recap email for Contoso from today's Fathom summary.

* **Research runs** show a **Reviewing Fathom** step, with a chip for each call and the source used.

* **Agents** can read Fathom on a schedule, for example a Monday digest of last week's client calls with open action items. Fathom has no write actions, so agents only read.

## Troubleshooting

| Symptom | Fix |
| - | - |
| **Connect** fails with **401 Unauthorized** | The key is wrong or was revoked. Generate a new key under **Settings → API Access** in Fathom and paste it again. |
| A call you expect is missing | Fathom did not record it, or it was recorded by someone else and not shared with a team you are on. |
| A call has no summary or transcript | Fathom is still processing the call. Try again in a few minutes. |
| Calls do not match a client | The calendar invitees used a different domain. Link each domain the client uses, or name the call. |
| Action items show no assignee | Fathom could not match the owner to an invitee. The action text is still shown. |
| Requests fail with **429 Too Many Requests** | Fathom limits API requests per minute for each key. Wait a minute and retry. |

## Related

* [How integrations work](https://hebno.com/docs/integrations/index.md)
* [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md)
* [Fireflies.ai](https://hebno.com/docs/integrations/fireflies.md)
* [Otter.ai](https://hebno.com/docs/integrations/otter.md)
* [Zoom](https://hebno.com/docs/integrations/zoom.md)


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