Bring Fathom meeting transcripts into Discovery so teams can work from what customers actually said, with transcript-backed evidence tied to the insights and bets that follow.
Fathom connects with a workspace API key an admin saves once. After that, the workspace can import selected meetings once or keep a reviewed meeting scope current on a schedule.
Fathom API keys are user-scoped. That means the key only sees meetings recorded by that user, or meetings shared to that user’s team.
Connect Fathom
Create the integration in Settings → Integrations → Fathom and paste the API key from Fathom’s API Access settings.
API key
- In Fathom, open User Settings → API Access.
- Generate an API key for the user whose meeting scope you want to import from.
- In Zentrik → Settings → Integrations → Fathom, paste the key and save.
- Use Test connection or a Discovery import preview to confirm the workspace can reach Fathom.
Zentrik does not show the key again after save.
How to use it
Open Discovery and choose Fathom from the import options. Pick a date range, set the reusable meeting rules, review the bounded result, and choose the meetings to import. Existing meetings can be selected again to check for changed source content without creating another Signal.
Import meetings
- Start a Fathom import from Discovery.
- Choose the date range for this run.
- Optionally limit meetings by recorder, Fathom team, attendee company domain, or audience.
- Choose the destination Product, whether to save reliably external attendees as People, and whether company domains may create missing Accounts.
- Review the meetings and select the records to import or refresh.
- Choose Import for this selection or Save for reuse to keep the same rules.
Use this when the transcript itself is the evidence you want PMs and leaders to trace back to.
Keep meetings current
Workspace owners and admins manage repeatable Fathom imports in Settings → Integrations → Imports.
- Save the reviewed setup from Discovery or create a Fathom import in Settings.
- Test the exact draft. A test reads a bounded meeting window and creates no Signals.
- Activate it, choose a cadence, and run it now or let the schedule run.
- Use run history to see created, updated, unchanged, skipped, or failed meetings.
Zentrik rereads each recording before writing. A recording keeps one Signal identity across reruns and reconnections. Changed transcript, summary, attendee, or routing data updates import-owned fields and queues analysis again. A recurring run rescans a short overlap so recently completed transcripts are not lost.
Live arrival
Live arrival brings each meeting into Discovery as soon as Fathom finishes it, instead of waiting for the next scheduled run. Any schedule on the import stays on as the catch-up sweep.
An owner or admin turns it on in Settings → Integrations → Fathom:
- Turn on Live arrival. Zentrik registers the webhook with Fathom for you, so there is nothing to set up there.
- Open each saved import that should arrive live and turn on Arrive live in its run policy.
The connection shows when the last meeting arrived. Turning live arrival off removes the webhook from Fathom again.
For workspace admins
- Fathom API keys are not tenant-wide admin keys. Even admins only see what the key’s user can access through Fathom sharing and team visibility.
- A saved import always uses its selected connection. Replacing the key does not change recording identity.
- When attendee organization is enabled, Zentrik uses recorder and invitee data to exclude internal attendees, then matches or creates reliably external attendees as People. Missing Account creation remains a separate opt-in; ambiguous or public domains stay unassigned.
- Rotate the key in Fathom and update Zentrik whenever your security policy requires it.
Troubleshooting
Check credentials and permissions on both sides first. If you have verified everything and it still fails, contact us with your workspace name and what you tried.
Credentials not working
Generate a new API key in Fathom, paste it into Settings → Integrations → Fathom in Zentrik, and save again. Watch for extra spaces when copying.
Meeting not available
Confirm the meeting is visible to the same Fathom user or team that owns the API key. If it is not visible there, Zentrik cannot import it from that key.
Transcript is not ready
Wait for Fathom to finish processing the recording, then retry the run. Zentrik stops before writing any meeting in that batch and does not advance the cursor, so the recording remains eligible.
Still failing
Contact us with your workspace name and what you tried—we will troubleshoot with you.
Continue from here
Related guides
Did this guide answer your question?
Your response helps us prioritize missing or unclear documentation.
Still stuck?
Send your question to Zentrik support. This guide will be included automatically.