Linking Fathom as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
The Fathom connector syncs meetings, summaries, transcripts, and team data from the Fathom AI notetaker into the PostHog data warehouse, so you can analyze meeting data alongside your product data.
Prerequisites
A Fathom API key. Create one in Fathom under User settings > API access. The key reads meetings you recorded and meetings shared with you or your team. To sync the users table, you need a key that belongs to an account admin.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
You'll be asked for:
- API key – create an API key in Fathom under User settings > API access and paste it here.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Some Fathom tables support incremental sync. Each incremental sync uses the created_at field to fetch only rows created since the last sync. Full refresh is also available for these tables.
| Table | Sync methods | Incremental field | Notes |
|---|---|---|---|
meetings | Incremental sync, full refresh | created_at | Core meeting data with action items, highlights, and CRM matches |
meeting_summaries | Incremental sync, full refresh | created_at | AI-generated summaries using the account's default template |
meeting_transcripts | Incremental sync, full refresh | created_at | Full meeting transcripts |
meeting_types | Full refresh | – | Meeting type definitions |
teams | Full refresh | – | Organization teams |
team_members | Full refresh | – | Team member details |
users | Full refresh | – | User accounts and permissions (requires an admin API key) |
A full refresh sync replaces the contents of the table.
Note: Summaries and transcripts are separate tables because Fathom rate-limits those requests more strictly than other endpoints. Keeping them separate avoids hitting rate limits during syncs.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
meetings | A meeting that Fathom recorded, with its calendar details, attendees, action items, highlights and CRM matches. Only meetings the API key can view are included. | Incremental, Full refresh | created_at | — |
meeting_summaries | The summary of a Fathom meeting, made with the account's default summary template. | Incremental, Full refresh | created_at | — |
meeting_transcripts | The transcript of a Fathom meeting. | Incremental, Full refresh | created_at | — |
meeting_types | A meeting type of the organization. Inactive types can still be on older meetings. | Full refresh | — | — |
teams | A team in the Fathom organization. | Full refresh | — | — |
team_members | A member of a team in the Fathom organization. | Full refresh | — | — |
users | A user in the Fathom account, with their permissions. Only an account admin's API key can read users. | Full refresh | — | — |
Troubleshooting
If the connection fails with "Fathom rejected your API key", create a new key in Fathom under User settings > API access and try again.
If the
userstable returns a 403 error, the API key doesn't belong to an account admin. Use an admin's API key to sync users.If syncs fail with a rate-limit error, wait a minute and try again. Fathom enforces strict rate limits, especially on summary and transcript requests.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.