Files and knowledge
Fathom for AI agents.
Managed auth, ready-made tools.
Find recorded meetings and read their transcripts and summaries in Fathom on behalf of each of your users.
About Fathom
With the Fathom connector, your agent works with the meetings Fathom recorded for each user. It can list past meetings, read a meeting’s transcript and summary, and see the user’s teams, using only the tools your project allows.
Fathom is an AI notetaker that records, transcribes and summarizes video meetings.
Tools
What your agent can do in Fathom.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Fathom connection.
-
List meetings
Readfathom_list_meetingsList the user's recorded meetings with their dates and attendees.
-
Get a transcript
Readfathom_get_transcriptGet the full transcript of a recorded meeting.
-
Get a summary
Readfathom_get_summaryGet the summary Fathom wrote for a meeting.
-
List teams
Readfathom_list_teamsList the teams in the user's Fathom account.
-
List team members
Readfathom_list_team_membersList the members of the user's teams.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Fathom, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent list meetings and read summaries, and switch off
fathom_get_transcriptif it should never see full transcripts. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example summaries but not full transcripts. A call outside them is refused.
Get started
Connect Fathom
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Fathom
Each end user authorizes their own Fathom account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Fathom account, once. const connection = await agent200 .user("user_123") .connect("fathom"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Fathom tools
Name the user, the model and the tools. The model decides which Fathom tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Summarize my sales call with Northwind from yesterday", tools: ["fathom"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, by connecting their own Fathom account. Each connection is their own.
-
What access is requested
The connection acts with that user's access in Fathom, such as reading meetings, transcripts and summaries. Users can revoke it later from their Fathom account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Fathom connector and how to use it.
Connector: Fathom, through Agent200. In code: "fathom". What it does: Find recorded meetings and read their transcripts and summaries in Fathom on behalf of each of your users. Page: https://www.agent200.com/connectors/fathom/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Fathom's own page, through the authorization link Agent200 returns. Never ask a user for a Fathom password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: fathom_list_meetings, fathom_get_transcript, fathom_get_summary, fathom_list_teams, fathom_list_team_members. Name "fathom" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/fathom/framework/claude/ https://www.agent200.com/connectors/fathom/framework/chatgpt/ https://www.agent200.com/connectors/fathom/framework/claude-code/ https://www.agent200.com/connectors/fathom/framework/muse/ https://www.agent200.com/connectors/fathom/framework/grok-bot/ https://www.agent200.com/connectors/fathom/framework/openai-dots/ https://www.agent200.com/connectors/fathom/framework/claude-duet/ https://www.agent200.com/connectors/fathom/framework/hermes-agent/ https://www.agent200.com/connectors/fathom/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/fathom.md
Guides
Use Fathom with the AI you build on.
Step-by-step setup for Fathom with a specific model, assistant or agent framework.
-
Fathom + Claude
How to connect Fathom to Claude
-
Fathom + ChatGPT
How to connect Fathom to ChatGPT
-
Fathom + Claude Code
How to connect Fathom to Claude Code
-
Fathom + Muse
How to connect Fathom to Muse
-
Fathom + Grok Bot
How to connect Fathom to Grok Bot
-
Fathom + OpenAI Dots
How to connect Fathom to OpenAI Dots
-
Fathom + Claude Duet
How to connect Fathom to Claude Duet
-
Fathom + Hermes Agent
How to connect Fathom to Hermes Agent
-
Fathom + OpenClaw
How to connect Fathom to OpenClaw
FAQ
Fathom and Agent200, answered.
Who handles the Fathom OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Fathom.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Fathom connection, never another user's. It cannot reach anything the user or Fathom has not authorized.
Can I limit what my agent can do in Fathom?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.