Conversational Intelligence · Beta
Fathom
API integration
Ship Conversational Intelligence features without building the integration. Full Fathom API access via Proxy and 10+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with Fathom
Common scenarios for SaaS companies building Fathom integrations for their customers.
Auto-attach meeting summaries to candidate or customer records
SaaS platforms like ATS or CRM tools can use Fathom webhooks to automatically capture post-meeting summaries and transcripts, then match them to the right record using calendar invitee emails. This eliminates manual note entry and ensures every conversation is documented.
Generate tasks and follow-ups from meeting action items
Project management and productivity platforms can ingest Fathom meeting data to extract action items and automatically create tickets, tasks, or reminders assigned to the right team members — turning conversations into accountable work items.
Power conversation intelligence and sales coaching features
Sales enablement platforms can pull diarized, timestamped transcripts from Fathom to run proprietary analysis — talk-to-listen ratios, keyword detection, objection handling scoring — without building their own recording infrastructure.
Monitor account health from customer call content
Customer success platforms can ingest meeting summaries and transcripts to detect churn signals, sentiment shifts, or unresolved issues across all client-facing calls, feeding automated health scores and internal alerts.
Centralize team meeting intelligence across an organization
Collaboration and knowledge management tools can list all teams, team members, and their meetings via Fathom to build a searchable, org-wide repository of meeting artifacts — making institutional knowledge accessible beyond the person who attended.
What You Can Build
Ship these features with Truto + Fathom
Concrete product features your team can ship faster by leveraging Truto’s Fathom integration instead of building from scratch.
Real-time meeting artifact ingestion via webhooks
Register Fathom webhooks programmatically so your platform receives transcripts, summaries, and action items the moment a meeting ends — no polling required.
Speaker-attributed transcript viewer
Use diarized transcript data with speaker names, emails, and timestamps to build an in-app playback timeline that shows exactly who said what and when.
Automatic record matching from calendar invitees
Map Fathom meeting metadata and calendar invitee emails to contacts, deals, or candidate records in your platform to auto-link meeting content to the right entity.
Markdown-native summary embedding
Ingest Fathom's structured markdown-formatted summaries and render them directly in your product's UI — wikis, timelines, or dashboards — without custom parsing.
Team-level meeting analytics dashboard
Pull team rosters and their associated meetings to surface aggregate metrics like meeting volume, coverage per account, and summary keyword trends across an entire team.
Webhook lifecycle management for end users
Let your users create and delete Fathom webhooks from within your product, giving them control over which meeting events flow into your platform.
SuperAI
Fathom AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_fathom_teams
List the teams in your fathom account. Returns team records including their id and team-specific attributes; the team names returned here are the values accepted by the teams[] filter on other endpoints.
list_all_fathom_team_members
List Fathom team members. Returns a paginated list of member records, each with an id and attributes containing the upstream-defined team-member fields.
list_all_fathom_meetings
List Fathom meetings recorded across your org, filterable by company domain, meeting type, recorder, and team. Returns each meeting with its id, recording_id, and created_at, plus optional action_items, highlights, summary, and transcript sections when the matching include flags are set.
delete_a_fathom_webhook_by_id
Delete a Fathom webhook by id. Returns an empty 204 response on success. Required: id.
create_a_fathom_webhook
Create a Fathom webhook to receive new meeting content. Returns the created webhook object including its id, destination_url, triggered_for, and include flags. Required: destination_url, triggered_for. At least one of include_transcript, include_crm_matches, include_summary, or include_action_items must be true.
list_all_fathom_recording_summary
Get the call summary for a Fathom meeting recording. Returns: template_name, markdown_formatted. Required: recording_id. Passing destination_url makes the request asynchronous — the summary is POSTed to that URL instead of returned directly. One summary per recording.
list_all_fathom_recording_transcript
Get the transcript for a Fathom meeting recording. Returns the transcript as an array of items with speaker (display_name, matched_calendar_invitee_email), text, and timestamp. Required: recording_id. Transcripts are only available after post-call processing completes.
list_all_fathom_meeting_types
List your org's meeting types in Fathom, including both active and inactive types. Returns items with their id and name, which can be passed as the meeting_type filter on the meetings list endpoint.
create_a_fathom_recording_download
Request a downloadable file for a Fathom recording. Returns a RecordingDownload including its download_id and status; video generation runs async (poll the status endpoint until status is completed), while audio-only recordings may complete immediately. Required: recording_id. Generated file URLs expire after ~24 hours.
list_all_fathom_recording_downloads
Get the status of a Fathom recording download. Returns the download's download_id and status; when completed, the payload carries a short-lived signed URL for the generated file that expires ~24 hours after generation. Required: recording_id, download_id.
list_all_fathom_users
List all fathom users in the account with their permissions. Returns each user's id, status, settings_access, permissions, and created_at; invited (pending) users have no permissions object yet and their created_at is the invite date. Note: status=`invited` cannot be combined with `settings_access`.
Why Truto
Why use Truto’s MCP server for Fathom
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 850+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
For your product
Ship Fathom tools in your product
Give the AI in your product access to each customer’s own Fathom account, with one MCP server per connected account.
Rather talk it through? Book a demo
For your own team
Use Fathom in ChatGPT or Claude yourself
Connect your company’s Fathom once, then ask in the AI you already use, with exactly your own access.
From the team behind Truto · 14-day free trial
How It Works
From zero to integrated
Go live with Fathom in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Fathom account
Use Truto’s frontend SDK to connect your customer’s Fathom account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Fathom
Truto’s Proxy API is a 1-to-1 mapping of the Fathom API. You call us, we call Fathom, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Fathom’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Fathom on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
What operations does Truto support for the Fathom integration?
Truto supports listing teams, team members, meetings, recording summaries, and recording transcripts. You can also create and delete webhooks programmatically. These cover the core read operations for meeting data and the webhook lifecycle for real-time event delivery.
Can I receive meeting data in real time instead of polling?
Yes. You can use the create_a_fathom_webhook endpoint to register a webhook that fires when new meeting content is available. This is the recommended pattern — it eliminates polling and delivers transcripts, summaries, and action items as soon as a meeting ends.
What data is available in Fathom meeting transcripts?
The recording transcript endpoint returns diarized transcript items including speaker display name, matched calendar invitee email, spoken text, and precise timestamps. This lets you attribute every statement to a specific participant.
Are Fathom summaries returned as plain text or structured content?
Fathom summaries are returned as markdown-formatted content along with the template name used to generate them. You can render the markdown directly in your UI or parse it for specific sections like action items or key decisions.
How does authentication work for end users connecting their Fathom accounts?
Truto handles the authentication flow for your end users. They connect their Fathom account through Truto's managed auth experience, so you don't need to build or maintain OAuth flows, token refresh logic, or credential storage yourself.
Is there a Unified API available for Fathom?
There is no Unified API category for Fathom yet. The integration is available through Truto's native API proxy, giving you direct access to Fathom-specific endpoints for teams, meetings, transcripts, summaries, and webhooks.
From the Blog
Fathom integration guides
Deep dives, architecture guides, and practical tutorials for building Fathom integrations.
Fathom
Get Fathom integrated into your app
Our team understands what it takes to make a Fathom integration successful. A short, crisp 30 minute call with folks who understand the problem.