Setting up Fathom as a Source

👥

Access Required

Guru Access: You need to be an Admin, Source Creator, or relevant custom role to set up Sources.

Fathom Access: You'll need a Fathom API key generated from your Fathom account. A Team Edition account is recommended, recordings visible to the authenticated user will be synced.

Setting up Fathom as a Source

1. In Guru, go to Apps and Integrations.
2. Select Sources, then click Add Source.
3. Choose Fathom from the list of integrations.
4. Enter your Fathom API key to authenticate.
5. Filter data to start pulling content in from a specific start date (optional).
6. Add a display name for the Source (optional) and click Connect Source.
7. Assign which Guru Groups should have access to this content.

✍

Note:

Your API key is scoped to the Fathom user who generated it. Guru will only sync meetings that user has access to - including their own recordings and any recordings shared with them. To control what gets ingested, generate the API key from an account with the appropriate level of access.

Objects synced from Fathom

Guru syncs meeting data from Fathom to power Answers. This content does not appear as Cards in Guru and is not directly searchable, but will be cited in generated Answers.

You can filter synced content in Guru using these facets: Created At, Recorded By, and Transcript Language.

Understanding how Fathom permissions work in Guru

Fathom's API does not expose per-recording sharing or visibility settings. While Fathom has sharing controls in its product (Private, Team-only, All Teams, etc.), none of that data is available through the API — so Guru has no way to read or enforce it.

Which recordings Guru can access is determined entirely by the API key you use during setup. The key inherits the generating user's access scope: if that user can see a meeting in Fathom, it gets synced into Guru.

Controlling which recordings are available

There are two approaches to manage the scope of synced content:

Use separate API keys and Sources. Create distinct Fathom API keys from different user accounts (e.g., one for the support team, one for leadership) and add each as its own Source in Guru. Then assign each Source to the appropriate Guru Groups. This is the recommended approach when you need to keep sensitive recordings — like executive calls — separate from the rest of your team.

Filter by team using Knowledge Agents. Each meeting includes the recorder's team name (e.g., "Sales" or "Engineering"), and you can use this as a filter when configuring a Knowledge Agent. However, this approach has limitations:

• The team name reflects who recorded the meeting, not who it was shared with. A sales rep who records an executive strategy session would tag that meeting as "Sales" even if only leadership was meant to see it.
• Meetings shared across multiple teams in Fathom still only show the recorder's single team.
• There's no way to distinguish a private recording from a team-shared one through the API.

❗

Important:

If your organization has confidential or executive-level recordings, the separate API keys and Sources approach is strongly recommended over team-based filtering alone.