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

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Retrieve Fathom transcripts and manage meetings from Guild agents

> Connect Guild agents to Fathom to list meetings, pull transcripts and summaries, download recordings, manage teams, and configure webhooks.

Integrations · Fathom

A Guild agent reads Fathom meeting transcripts, pulls summaries, and manages teams without handling credentials directly. Guild stores the Fathom API key server-side and injects it at request time, so it never enters agent code or prompts. Credential policies let you restrict which operations each agent can call, and every request is logged for audit.

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Fathom.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Fathom to your first agent.

## What the Fathom integration exposes

The tools cover meetings, recordings, teams, users, and webhooks. Agents can list meetings and meeting types, start and poll recording downloads, retrieve transcripts and summaries, list teams and team members, list users with their permissions, and create or delete webhooks. Transcript and summary tools support both synchronous responses and async delivery to a destination URL.

## How it works

**1. Get your Fathom API key**

In Fathom, go to User Settings > API Access and copy your API key.

**2. Connect the credential in Guild**

In Guild, go to Access & setup > Credentials, click Connect, select fathom, and paste the key into the API Key field. See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped options.

**3. Import and use the tools**

Import FathomTools from the guildai\~fathom package and spread it into your agent's tools object. Use pick() to include only the tools your agent needs.

## Why Fathom access needs governing

Fathom holds recorded meetings, transcripts, and summaries that may contain sensitive conversations. Guild stores the API key server-side and injects it through the credential proxy, so agent code never sees it. You can scope a credential to one workspace, one member, or a single agent rather than sharing it across the organization. See [Credentials](https://docs.guild.ai/platform/credentials.md) for scoping options and [Security architecture](https://docs.guild.ai/platform/security-architecture.md) for how the proxy works.

Credential policies let you write ALLOW and DENY rules that the proxy enforces before any request leaves Guild. You can restrict an agent to read-only listing operations with a pattern like fathom\_list\_\*, block webhook creation with a DENY rule on fathom\_create\_webhook, or scope a rule to one agent while giving another broader access. See [Credential policies](https://docs.guild.ai/platform/credential-policies.md). Without any scoped rules, the default posture is allow-all; delete that default once your rules cover everything agents should reach.

## About the Fathom integration

Agents can list meetings and meeting types, download recordings, and retrieve transcripts or summaries from Fathom. They can also manage teams and team members, list users, and create or delete webhooks to receive new meeting content. The integration is `guildai~fathom`.

## Authentication

* **Type:** API key
* **Header:** Guild sends the key as `X-Api-Key: <key>`

### Setup

**1. Connect Fathom**

In Guild, go to **Access & setup > Credentials**, click **Connect**, select **fathom**, and paste the key into **API Key**.

See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped credentials.

## Usage

```typescript theme={null}
import { FathomTools } from "@guildai-services/guildai~fathom"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  systemPrompt: "You work with Fathom.",
  tools: { ...FathomTools },
})
```

### Selecting specific tools

Tools are named with the `fathom_` prefix. Use [`pick()`](https://docs.guild.ai/sdk/tools#selecting-specific-tools) to include only what your agent needs.

## Tools

Tools in the latest published version of `guildai~fathom`:

| Tool | What it does |
| - | - |
| `fathom_create_recording_download` | Starts async generation of a downloadable file and returns a 'download\_id' to poll. |
| `fathom_create_webhook` | Create a webhook to receive new meeting content. |
| `fathom_delete_webhook` | Delete a webhook. |
| `fathom_get_recording_download` | Returns the status of a download created with the request-a-download endpoint. |
| `fathom_get_recording_summary` | This endpoint has two behaviors depending on your request payload: - If you send 'destination\_url', the endpoint will behave in an asynchronous manner. - If you do not send 'destination\_url', the… |
| `fathom_get_recording_transcript` | This endpoint has two behaviors depending on your request payload: - If you send 'destination\_url', the endpoint will behave in an asynchronous manner. - If you do not send 'destination\_url', the… |
| `fathom_list_meetings` | List meetings. |
| `fathom_list_meeting_types` | List your org's meeting types, including both 'active' and 'inactive'. |
| `fathom_list_team_members` | List team members. |
| `fathom_list_teams` | List teams. |
| `fathom_list_users` | List all users in the account with their permissions. |

## Frequently asked questions

> [accordion] Can an agent get a transcript without sending it to an external URL?
>
> Yes. The fathom\_get\_recording\_transcript tool has two behaviors: if you omit destination\_url, it returns the transcript synchronously in the response. If you include destination\_url, it delivers the result asynchronously to that address.

> [accordion] Does the integration receive webhook events automatically?
>
> No. The catalog entry lists no webhook events for this integration. Agents can create and delete webhooks using fathom\_create\_webhook and fathom\_delete\_webhook, but Guild does not process inbound Fathom webhook events through event triggers.

> [accordion] Can I limit an agent to only listing meetings and reading transcripts?
>
> Yes. Write a credential policy that allows only fathom\_list\_\* and fathom\_get\_recording\_\* operations and denies everything else. The Guild credential proxy enforces the policy before any request reaches Fathom. See [Credential policies](https://docs.guild.ai/platform/credential-policies.md).

> [accordion] Can I give one agent its own Fathom credential separate from the rest of the organization?
>
> Yes. From the installed agent's page, connect a credential scoped as Dedicated to this agent. That credential serves only that agent and is never offered to other agents or workspaces. See [Credentials](https://docs.guild.ai/platform/credentials.md).

## Put a governed agent on Fathom this week

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Fathom.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Fathom to your first agent.

## Related

**Also runs on Guild:** [Calendly](https://docs.guild.ai/integrations/calendly.md) · [Coda](https://docs.guild.ai/integrations/coda-openapi.md) · [Confluence](https://docs.guild.ai/integrations/confluence.md) · [Fireflies](https://docs.guild.ai/integrations/fireflies.md)

**Read:** Docs: [Credential policies](https://docs.guild.ai/platform/credential-policies.md) · [Credentials](https://docs.guild.ai/platform/credentials.md) · [Tools in agents](https://docs.guild.ai/sdk/tools.md)