Skip to main content
The Fathom integration captures transcripts and AI summaries from your recorded Fathom meetings and feeds them into Modem for analysis. Each meeting becomes a conversation that’s grouped into topics, classified by type (bug, feature request, praise, complaint), and linked to the people and companies who spoke in it.
Fathom is capture-only and read-only. Modem ingests meeting transcripts (as speaker turns), Fathom’s meeting summaries, participant identities, and meeting metadata. It does not access audio or video recordings or your Fathom account settings, and it never writes anything back to Fathom. There’s no way to talk to the Modem Agent from inside Fathom; you query captured Fathom data from the Modem Agent on the web.

​
How it works

Modem connects to your Fathom account with OAuth, authorized by an individual Fathom user signing in and approving access. During setup, Modem registers a webhook on that account, so capture is push-based: as soon as Fathom finishes processing a recording, it sends the meeting’s transcript and summary to Modem. There’s no polling delay. A meeting shows up in Modem shortly after Fathom publishes it. When you first connect, Modem also imports your recent history: a one-time backfill of meetings from the last 30 days, up to 100 meetings. Meetings older than that window aren’t imported. The backfill runs once per connection. Reconnecting later (for example to repair the connection) doesn’t re-import history. A background job refreshes the connection’s access token before it expires, so the webhook and API access normally stay authenticated without any action from you.
Both delivery paths land in the same place: a backfilled meeting and a webhook-delivered meeting are transformed identically, and redelivered meetings are de-duplicated, so the same meeting isn’t stored twice.

​
Prerequisites

  • Owner or admin role in your Modem organization, to connect and manage the integration
  • A Fathom account to authorize. The person connecting signs into their own Fathom account, and Modem’s capture follows what that account can see. Connect with the account whose meetings (and team-shared meetings) you want captured.

​
Setup

1

Start the connection

Go to Settings → Integrations → Fathom in your Modem dashboard and click Connect. Only organization owners and admins can connect.
2

Authorize Modem in Fathom

You’ll be redirected to Fathom to sign in and approve the access Modem requests. See Permissions below.
3

Capture starts immediately

Modem registers a webhook on your Fathom account and requests the 30-day history import. New meetings arrive as Fathom finishes processing them; recent past meetings fill in as the backfill runs.

​
Permissions

During authorization you approve Fathom’s single OAuth scope. Modem reads meeting content and participant identities; it does not send or modify anything in Fathom. With that grant, Modem asks Fathom to include the transcript, summary, and action items with each meeting delivery. It deliberately does not request Fathom’s CRM matches. Modem resolves people and companies from its own data instead.
Fathom authorization is per user, not account-wide: Modem acts as the Fathom user who clicked Connect. What Modem can capture is bounded by that user’s Fathom access.

​
Meeting Access and Permissions

Fathom’s per-user sharing and visibility do not carry over into Modem. Modem captures the connecting user’s recordings, recordings shared with them, and recordings shared with their team. Every captured meeting then becomes visible to everyone in your Modem organization, even people who couldn’t open that recording in Fathom. Connect with an account whose visibility you’re comfortable sharing organization-wide.
Yes. Fathom’s OAuth grant is per user: Modem holds one credential, tied to the Fathom account of the person who clicked Connect. It does not hold account-wide or per-teammate tokens.
The meetings the connecting user’s grant can reach: their own recordings, recordings shared with them externally, their recordings shared with the team, and the team’s shared recordings. Modem asks Fathom for all of these deliberately: customer signal usually lives across the whole team, and a narrower default would silently drop meetings. Meetings outside that visibility never reach Modem.
No. Once a meeting is captured, it is stored against your Modem organization and is readable by every member of that organization through search, topics, and the Modem Agent, regardless of who it was shared with in Fathom. If a recording is private in Fathom, treat capturing it in Modem as widening who can read it.
Two, both set on the Modem side:
  • Which account connects: the primary control. Capture follows the connecting user’s Fathom visibility, so connect with an account that sees the meetings you want captured and nothing you don’t.
  • Disconnecting: stops all future capture immediately and removes Modem’s webhook from your Fathom account.
There are no per-meeting or per-team capture filters in Modem today.
Only Modem organization owners and admins. Regular Modem members can view the integration’s status but cannot change it.
Transcripts as speaker turns, Fathom’s meeting summary, participant identities, meeting metadata, and links back to the recording in Fathom. No audio or video. See What Gets Captured. Disconnecting stops future capture but leaves already-captured data in Modem; contact support@modem.dev to have it deleted.

​
Historical Import

Connecting triggers a one-time import of your recent Fathom history, so the integration is useful before your next meeting happens:
  • Window: meetings from the last 30 days before you connected
  • Limit: up to 100 meetings
  • Once per connection: reconnecting the same organization later does not re-run the import
Each imported meeting’s transcript and summary are fetched individually from Fathom, so a large history takes a little while to fill in. Meetings Fathom has no transcript for are skipped: a summary alone isn’t a conversation.

​
What Gets Captured

For each captured meeting, Modem captures:

​
Transcript

The meeting transcript as ordered speaker turns, threaded into a single conversation per meeting so it groups into topics like any other source. Each turn keeps its offset from the recording start, so the conversation’s timeline is preserved.

​
Summary

Fathom’s AI-generated meeting summary, stored as the meeting’s description alongside the transcript.

​
Participants

Each speaker’s name, and their email where Fathom has matched the speaker to a calendar invitee. Calendar invitees who never spoke and the person who recorded the meeting are included in the participant roster too. Where Fathom marks an invitee internal or external, that tag is carried through; participants Fathom doesn’t tag are recorded as unknown rather than guessed. Participants are resolved into people and companies.

​
Meeting metadata

The meeting title, start time, duration, transcript language, and links back to the recording in Fathom.
Modem does not capture audio or video recordings, Fathom’s CRM matches (they’re explicitly excluded from what Modem requests), your Fathom account credentials, or billing information. Only the transcript, summary, participants, and metadata above are ingested.

​
Analyzing Fathom Conversations

Once meetings are flowing, ask the Modem Agent about them from the web dashboard like any other source.

​
Troubleshooting

The integration is in beta and enabled per organization. Email support@modem.dev to request access. Once enabled, the Fathom card appears under Settings → Integrations.
A meeting is delivered when Fathom finishes processing its recording, so allow a few minutes after the meeting ends. Modem can only capture meetings the connecting user’s Fathom account can see, so a teammate’s unshared recording won’t arrive. If nothing is arriving at all, try disconnecting and reconnecting, which re-registers the webhook on your Fathom account.
Modem skips meetings Fathom delivers or lists without any transcribed content. There’s nothing to analyze without the conversation itself. If Fathom shows a transcript for the recording but it never appeared in Modem, contact support@modem.dev.
The one-time history import covers the 30 days before you connected, up to 100 meetings, and runs once per connection. Reconnecting doesn’t re-run it. Meetings outside that window aren’t imported.
Open Settings → Integrations → Fathom to see the connection status. Access tokens are refreshed automatically, but if the grant itself is revoked (for example the connecting user leaves Fathom), you’ll need to reconnect. If the error persists, contact support@modem.dev.

​
Disconnecting

To disconnect Fathom:
  1. Go to Settings → Integrations → Fathom
  2. Click Disconnect and confirm
Disconnecting stops new meeting deliveries immediately and removes the webhook Modem registered on your Fathom account. Historical data remains in Modem after disconnecting.

The Modem Agent

Query and act on your captured Fathom meetings from the web.

Topics

See how meetings are grouped into themes and classified.

Companies & People

Understand how Modem links meeting participants into unified profiles.

All Integrations

Browse every data source and agent tool.