How to Connect Fathom to OpenClaw

Log in to your Fathom account at fathom.video and navigate to your account settings. Go to Settings > Integrations > API. If you do not see an API section, ensure you are on a plan that includes API access — Fathom includes API access for personal use on the free tier, with higher rate limits on paid plans. Click 'Generate API Key' or 'Create New Key'. Give it a descriptive name like 'OpenClaw Integration'. Fathom will display the key value — copy it immediately, as some implementations only show it once. The API key authenticates all requests to Fathom's REST API. It is tied to your Fathom account and provides access to all meetings recorded by your Fathom instance — both meetings you hosted and meetings where Fathom joined as a notetaker on your behalf. Keep the key secure: it provides read access to all your meeting transcripts and recordings. Do not commit it to version control or share it in public channels.

1# Test your Fathom API key (run in terminal)
2curl -H "Authorization: Bearer YOUR_FATHOM_API_KEY" \
3     -H "Accept: application/json" \
4     https://api.fathom.video/v1/meetings
5
6# Expected: a JSON array of your recent meetings
7# If you see 401: the key is wrong or inactive
8# If you see 200 with an empty array: no meetings recorded yet

Open your OpenClaw configuration file at `~/.openclaw/config.yaml` and add the Fathom integration block under the `integrations` key. This is a direct API integration, configured separately from ClawHub skills. The `api_key` field is your Fathom Personal API Key. The `base_url` is Fathom's API endpoint — do not change this unless Fathom updates their API domain. The `poll_interval` controls how often OpenClaw checks for new meetings when using polling-based workflows (in seconds). The `auto_fetch_transcripts` option tells OpenClaw to automatically retrieve full transcript text when querying meetings — set to true if your workflows need the detailed transcript, or false if you only need meeting summaries (faster and lower on API calls). After saving the config, reload OpenClaw. It will make a test call to the Fathom API to validate the key. Check the OpenClaw log for the connection confirmation.

1# ~/.openclaw/config.yaml
2integrations:
3  fathom:
4    api_key: "YOUR_FATHOM_API_KEY"
5    base_url: "https://api.fathom.video/v1"
6    poll_interval: 600            # Check for new meetings every 10 minutes (default: 600)
7    auto_fetch_transcripts: false # Set true if workflows need full transcript text
8    lookback_hours: 24            # How far back to look for new meetings on each poll
9    include_bot_meetings: true    # Include meetings where Fathom joined as a bot participant

With the integration configured, test retrieval of recent Fathom meetings. The Fathom API provides endpoints for listing meetings, retrieving transcript text, and fetching the AI-generated summary for each meeting. The `/meetings` endpoint returns a paginated list of all recorded meetings. Each meeting object includes the title, start time, duration, attendees, and links to the recording and transcript. The `/meetings/{id}/summary` endpoint returns Fathom's AI-generated summary including key points, decisions, and action items. For workflows that need the full transcript — for example, a workflow that searches meeting content for specific topics — use the `/meetings/{id}/transcript` endpoint. Transcripts are returned as time-coded text segments. Test both endpoints with a recent meeting ID from the initial listing to confirm the integration can retrieve all the data types your workflows will need.

1# List recent meetings
2curl -H "Authorization: Bearer YOUR_FATHOM_API_KEY" \
3     "https://api.fathom.video/v1/meetings?limit=10&sort=created_at:desc"
4
5# Get AI summary for a specific meeting
6curl -H "Authorization: Bearer YOUR_FATHOM_API_KEY" \
7     "https://api.fathom.video/v1/meetings/MEETING_ID/summary"
8
9# Get full transcript for a meeting
10curl -H "Authorization: Bearer YOUR_FATHOM_API_KEY" \
11     "https://api.fathom.video/v1/meetings/MEETING_ID/transcript"
12
13# Example meeting summary response structure:
14# {
15#   "meeting_id": "...",
16#   "title": "Weekly Team Sync",
17#   "summary": "The team discussed Q2 priorities...",
18#   "action_items": [
19#     { "text": "Follow up with design team by Friday", "assignee": "Alice" }
20#   ],
21#   "key_points": ["...", "..."]
22# }

Configure an OpenClaw workflow that polls for new Fathom meetings and processes each new meeting's summary automatically. The workflow trigger is time-based (runs every `poll_interval` seconds) and checks for meetings with a creation timestamp newer than the last processed meeting. For each new meeting found, the workflow fetches the AI summary and extracts action items. These can then be passed to downstream actions: logging to a file, sending a notification, posting to a tool, or updating a task list. The config example below shows a basic polling workflow that logs new meeting summaries. Extend the `actions` block with additional steps to push data to other tools in your OpenClaw configuration — for example, appending to an Obsidian note, updating an Airtable row, or sending a Telegram message. RapidDev's team recommends starting with the logging action first to verify the workflow fires correctly, then adding downstream integrations one at a time.

1# ~/.openclaw/config.yaml — post-meeting automation workflow
2workflows:
3  fathom-new-meeting:
4    trigger:
5      integration: fathom
6      event: new-meeting
7    actions:
8      - type: log
9        message: "New Fathom meeting: {{meeting.title}} ({{meeting.start_time}})"
10      - type: log
11        message: "Summary: {{meeting.summary}}"
12      - type: log
13        message: "Action items: {{meeting.action_items | join(', ')}}"
14
15  fathom-weekly-digest:
16    trigger:
17      type: schedule
18      cron: "0 8 * * MON"     # Every Monday at 8 AM
19    actions:
20      - type: integration-query
21        integration: fathom
22        query: meetings
23        params:
24          min_date: "{{date.minus_days(7)}}"
25          max_date: "{{date.today}}"
26      - type: log
27        message: "Weekly Fathom digest: {{result.count}} meetings recorded"