All integrations

Fathom

DOCS & KNOWLEDGE · FILES & DOCS

Recorded meetings, transcripts, summaries, and action items from their own account.

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

fathom_get_recording_downloadREAD

Check a Fathom recording download started with fathom_request_recording_download. status is processing, completed, failed or expired; on failure, failure_reason says whether generation failed or timed out. As above, the signed file URL is withheld by Agentic Fabriq - size, content type and expiry are returned so you can tell the user whether and when the file is ready. A download expires about 24 hours after it is generated; request a new one after that.

read_recordings
fathom_get_summaryREAD

Get one Fathom recording's AI summary as Markdown, with the name of the template that produced it. Fathom returns the account's DEFAULT template and publishes no way to ask for another; changing a call's template in the Fathom UI does not change what this returns, and there is one summary per recording. Heavy rate-limit bucket: 30 per minute, 5 under load. Numeric recording_id from fathom_list_meetings. This is NOT the id in a Fathom call URL - Fathom documents those as different identifiers that are not interchangeable, so an id copied from a browser will 404.

read_transcripts
fathom_get_transcriptREAD

Get one Fathom recording's full transcript: for every line, the speaker's display name, the matched calendar-invitee email address where Fathom could match one, the spoken text, and an HH:MM:SS timestamp relative to the start of the meeting. Use it for exact quotes and for questions the summary does not answer. This is verbatim private conversation - handle it accordingly. Transcripts exist only after post-call processing finishes; Fathom offers no live or real-time transcript. Heavy rate-limit bucket: 30 per minute, 5 under load. Numeric recording_id from fathom_list_meetings. This is NOT the id in a Fathom call URL - Fathom documents those as different identifiers that are not interchangeable, so an id copied from a browser will 404.

read_transcripts
fathom_list_meeting_contentREAD

List Fathom meetings WITH their AI summaries and/or full transcripts inline - one call instead of a listing plus one read per meeting. Requires include_summary, include_transcript, or both. Use it for questions spanning several meetings ('what did customers say about pricing in January'); use fathom_get_transcript for one known recording. NOT AVAILABLE on Fathom connections made through OAuth - Fathom forbids it, and this tool will say so and name the alternative. This is Fathom's heavy rate-limit bucket: 30 requests per minute, which Fathom reduces to 5 per minute under load, so ask for a narrow date range rather than paging an entire history. A Fathom credential is scoped to one user: it reaches meetings that user recorded plus meetings shared with them or their team, never another user's private unshared meetings, and Fathom sells no organisation-wide key. An empty result is normal and is not an error.

read_transcripts
fathom_list_meeting_typesREAD

List the organisation's Fathom meeting types - both active and inactive - so a meeting_type filter can be spelled correctly. Call this before filtering fathom_list_meetings by meeting_type: Fathom returns an empty list for an unrecognised type name instead of an error, so a guessed name looks like 'there were no such meetings'.

read_meetings
fathom_list_meetingsREAD

List Fathom meetings with their title, calendar title, type, recording_id, timestamps, invitees, who recorded them, and links to open them in Fathom. This is the entry point for every other Fathom tool: recording_id comes from here and nowhere else. Returns METADATA ONLY - it never returns what was said. For summaries or transcripts use fathom_list_meeting_content, fathom_get_summary or fathom_get_transcript, which sit behind a separate permission. A Fathom credential is scoped to one user: it reaches meetings that user recorded plus meetings shared with them or their team, never another user's private unshared meetings, and Fathom sells no organisation-wide key. An empty result is normal and is not an error. Each item's share_url opens the recording under a per-recording sharing setting the account holder chose, which may be 'anyone with the link'; Fathom exposes no field saying which, so treat a share_url as potentially world-readable before sending it outside the company.

read_meetings
fathom_list_team_membersREAD

List Fathom team members - name, email address and join date - optionally narrowed to one team. The email addresses are what the `recorded_by` filter on fathom_list_meetings takes, so this is how you answer 'show me Dana's customer calls' without guessing an address.

read_directory
fathom_list_teamsREAD

List the teams in the connected Fathom account with their names and creation dates. The names are what the `teams` filter on fathom_list_meetings takes, so call this before filtering by team rather than guessing a name.

read_directory
fathom_list_usersREAD

List every user in the Fathom account with their status (active, deactivated or invited) and their permissions: settings_access (none, team_admin, account_admin) and view_access, which is which teams' calls they can see. ADMIN ONLY - Fathom answers 403 unless the connected user's settings_access is account_admin, and that is a role requirement rather than a plan one. This is the tool that explains the commonest Fathom puzzle, 'why can't I see my colleague's calls': a user's API access sees exactly what that user sees in Fathom, so view_access here is the answer. Invited users have no permissions object yet and their created_at is the invite date. status='invited' cannot be combined with settings_access.

read_admin
fathom_request_recording_downloadREAD

Ask Fathom to generate a downloadable video or audio file for a recording, and report the result. Returns a download_id to poll with fathom_get_recording_download; an audio-only recording can come back completed immediately. Downloading needs more than view access - a limited-access share is refused with 403. AGENTIC FABRIQ WITHHOLDS THE GENERATED FILE'S URL: Fathom returns a signed link that hands the whole recording to anyone holding it with no sign-in and no audit record. What you get is whether the file can be made, its size, its content type and when it expires. To watch or download the recording, open the meeting's share_url or url from fathom_list_meetings. Numeric recording_id from fathom_list_meetings. This is NOT the id in a Fathom call URL - Fathom documents those as different identifiers that are not interchangeable, so an id copied from a browser will 404.

read_recordings

Put Fathom behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.