Connect Fathom to Rig

    Rig syncs your Fathom meetings with their transcripts, summaries and action items, plus your teams and team members, into your warehouse. You connect with an API key from your Fathom user settings.

    Before you start

    • You need a Fathom account. An API key is scoped to the user who creates it.
    • Decide whose account to use. The key reads meetings that user recorded or that were shared with them or their team.

    Step 1: Generate a Fathom API key

    1. In Fathom, open your user settings and go to the API Access section.
    2. Generate an API key and copy it.

    What the key can see
    A key never grants access to other people's private meetings. Fathom admins can see all users' shared meetings by configuring View permissions in Fathom.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Fathom, open the card and click Connect.
    3. Fathom API key: The key you generated.
    4. Webhook signing secret (optional): Leave it blank. Syncing does not use it.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Fathom lands in its own fathom schema in your warehouse:

    • Meetings: Each recording with its metadata, the transcript by speaker, the default AI summary and the action items.
    • Teams: Your Fathom teams.
    • Team members: The people on each team.

    Good to know

    • Fathom allows 60 requests a minute, so a large first sync takes a while.
    • Transcript lines land in a child table of meetings, one row per spoken line with speaker and timestamp.
    • A meeting synced before Fathom finishes processing it can arrive with an empty transcript.
    • To disconnect Fathom, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Analyse what is said across every call
    • Connect conversations to outcomes
    • Track action items to completion

    More ideas for using Fathom

    Fathom documentation

    Was this guide helpful?