Fathom

Integrate Fathom AI meeting recorder into your workflows. List recorded meetings, pull full transcripts and AI-generated summaries for a specific recording, and browse team and member data — all without leaving your workflow canvas.

Overview

Operations

Configuration

Outputs

fathom_list_meetings

fathom_get_summary

fathom_get_transcript

fathom_list_team_members

fathom_list_teams

Example

[Starter] → [Fathom: List Meetings] → [Agent: summarize and route]

A scheduled Starter fires daily and triggers the Fathom block with {{FATHOM_API_KEY}} to call fathom_list_meetings, filtering to meetings from the past 24 hours using createdAfter set to {{starter.yesterdayISO}} and includeSummary set to "true". The downstream Agent block reads {{fathom.meetings}}, extracts action items from each meeting's default_summary, and posts a consolidated digest to your team's Slack channel.

Tips

• Get the recording_id first. Both fathom_get_summary and fathom_get_transcript require a recordingId. Use fathom_list_meetings in an upstream block and reference {{fathomList.meetings[0].recording_id}} to feed it downstream.
• Embed vs. dedicated fetch. For one-off meetings, set includeSummary or includeTranscript to "true" on fathom_list_meetings to avoid an extra block. For deeper processing or large transcripts, use the dedicated fathom_get_summary / fathom_get_transcript operations instead.
• Paginate large result sets. All list operations return a next_cursor field. Wire it into a Loop block and pass {{fathomList.next_cursor}} as the cursor param on each iteration to page through all results.
• API Key security. Store your Fathom API Key as a workflow secret and reference it as {{FATHOM_API_KEY}} rather than pasting it directly into the block. The apiKey param has user-only visibility and is never exposed in outputs.