Setting Up Fathom Archiving

Connect Fathom to archive accessible meeting transcripts and details in Comma. AI summaries, action items and available recordings are optional.

Before you start

• You need Comma team administrator access. Ask Comma support to enable Fathom for your team. Then open Settings, Channels & capture and enable the Fathom channel. The Fathom Connection card appears under Workspace Integrations after that.
• Choose the Fathom account whose meetings your organization intends to archive. Comma has one Fathom connection per team.
• Generate a key in the API Access section of Fathom User Settings. Fathom’s key guide explains that keys see meetings the owner recorded or can access through sharing. They do not grant access to other users’ private meetings.
• Confirm the account can see a representative meeting and its transcript before connecting. A team-level connection in Comma does not expand the key’s access in Fathom.

Connect Fathom

1. Sign in to the Comma dashboard as a team administrator and select the correct team.
2. Open Integrations and find Fathom Connection under Workspace Integrations.
3. Click Connect, then paste the key into Workspace API key.
4. Click Connect Fathom. Comma verifies the key with Fathom before saving it. The stored key is encrypted and is not displayed again.
5. Comma requests the Fathom webhook subscription when you connect. Open the connection’s Manage page to see its status. A webhook is a notification that a meeting’s content is ready to retrieve.

Do not send your API key to support or include it in screenshots.

Choose what to capture

Under What to capture, review these settings and click Save capture settings:

Content	Default	Setting
Available transcripts and meeting details	Included	No separate transcript toggle.
AI summaries and action items	On	Turn AI summaries and action items off if they are outside your archival scope.
Available recording media	Off	Turn Meeting recordings on if you need the recording as well as the transcript.

Demo Data.

The transcript is searchable and used for policy checks. AI summaries and action items are separate, AI-generated attachments; their text is not scanned for policy matches or indexed as the transcript. Transcripts themselves are machine-generated and can contain errors.

Fathom’s recording links expire, and media may still be processing when the meeting first appears. Turning on recordings does not guarantee a media file exists or remains available to download.

Verify a meeting

1. Complete a short meeting in Fathom and wait for its transcript to be ready. Use the connected account, or confirm that the meeting is shared with it.
2. In Comma, open Fathom Connection and inspect Last meeting delivered, Last successful sweep and any open coverage gaps. Periodic sweeps run on a 30-minute schedule; this is not a delivery-time guarantee.
3. Find the meeting in the archive. Check its source, title, transcript and available participant details.
4. If you enabled AI-written files or recordings, open the attachments and confirm that the expected files arrived.

Key healthy means the credential is usable. It does not prove that a meeting was captured. The connection also explains that its webhook subscription cannot be checked independently at Fathom; use actual delivery history and the archived test meeting to verify setup.

Troubleshooting and maintenance

What you see	What to check
Key rejected	Copy the correct key from Fathom and confirm it is still active.
No meeting arrives	Check the key owner’s access, whether Fathom finished processing, and the last successful sweep. Open coverage gaps may identify an access or retrieval issue.
Transcript present, recording missing	Check Meeting recordings, source media availability and any expired-download gap.
A new key is refused as a different workspace	Use a key with access to the meetings this connection already archives. Contact support before changing the source account.

Use Rotate API key to replace a key. Comma verifies the replacement before switching; afterwards, delete the old key in Fathom. Use Reconnect after repairing an authorization problem.

To stop capture, choose Disconnect Fathom, then delete the API key in Fathom. Disconnecting stops new capture and does not itself erase the meetings already archived; existing records remain subject to your organization’s retention settings.

Scope to know

• Recorder meetings are treated as business records. This is an administrator-managed team connection, not a per-member personal-account connection.
• Initial retrieval is bounded by source access and retention. Files deleted before retrieval may be unavailable. Agree the required date range with Comma first.
• A meeting captured by both Fathom and a native meeting platform currently appears as separate records. A hold on one does not automatically cover the other.

See Fireflies setup or meeting recording archiving for the other capture paths.