Skip to main content

​
Prerequisites

Before continuing, you should have already completed the following for this connector:
1

Configure the Connector

Enable the connector and set up its connector profile in your project. See Managing Connectors.

Connector Profile

Fathom - API Key
2

Link an Account

Connect an account using StackOne Hub or Auth Link.

Link Account

Fathom - API Key

​
How Fathom Webhooks Work

Fathom webhooks are configured automatically when you enable events for this connection. StackOne registers a webhook with Fathom via the API and begins receiving meeting data as soon as recordings are processed.

1

Automatic webhook registration

When you enable events for this Fathom connection, StackOne automatically creates a webhook subscription in your Fathom account using your API key. The webhook is configured to receive all recording types and all available content (transcript, summary, action items, and CRM matches).

  • Webhooks are created via the Fathom API using your API key credentials.
  • The webhook subscribes to all recording scopes — My Recordings, My Team-Shared Recordings, Team Recordings, and External Recordings.
  • All content types are enabled — Transcript, Summary, Action Items, and CRM Matches.
  • When you disable events, the webhook is automatically deleted from Fathom.
2

Verify in Fathom settings

You can verify the webhook was created by checking your Fathom account settings.

  • Sign in to your Fathom account.
  • Click Settings in the navigation bar.
  • Scroll to the API Access section and click Manage next to your API key.
  • Under WEBHOOKS, you should see a StackOne webhook URL listed with all scopes and events enabled.

​
Available Webhook Events

Fathom sends a single event type with rich meeting data.

1

New Meeting

Fired when a new meeting recording is processed and content is ready.

  • Event type — new_meeting
  • Meeting metadata — title, recording ID, URL, share URL, meeting type
  • Timing — scheduled start/end time, actual recording start/end time, created timestamp
  • Participants — calendar invitees with name, email, domain, and internal/external classification
  • Recorded by — name, email, domain, and team of the recorder
  • Transcript — full transcript with speaker names, matched emails, and timestamps
  • Summary — AI-generated meeting summary in markdown format with template name
  • Action items — extracted action items with assignee name and email
  • Highlights — notable moments with text and timestamps
  • CRM matches — matched contacts, accounts, opportunities, and leads from linked CRM

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.