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.
Book a demo
See how teams govern agents that use Fathom.
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 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 for scoping options and Security architecture 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. 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 isguildai~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.
Usage
Selecting specific tools
Tools are named with thefathom_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~fathom:
Frequently asked questions
Can an agent get a transcript without sending it to an external URL?
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.
Does the integration receive webhook events automatically?
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.
Can I limit an agent to only listing meetings and reading transcripts?
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.
Can I give one agent its own Fathom credential separate from the rest of the organization?
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.
Put a governed agent on Fathom this week
Book a demo
See how teams govern agents that use Fathom.
Talk to sales
Get access to Guild, then connect Fathom to your first agent.