> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fathom Webhook Setup Guide

> Configure Fathom to deliver events to StackOne.

## Prerequisites

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

<Steps>
  <Step title="Configure the Connector">
    Enable the connector and set up its connector profile in your project. See <a href="/guides/explore-connectors">Managing Connectors</a>.

    <Columns cols={2}>
      <Card title="Connector Profile" href="/connectors/fathom/guides/connector-profile/api-key" icon="https://stackone-logos.com/api/fathom/filled/png" horizontal>
        Fathom - API Key
      </Card>
    </Columns>
  </Step>

  <Step title="Link an Account">
    Connect an account using <a href="/guides/embedding-stackone-hub">StackOne Hub</a> or <a href="/guides/auth-link">Auth Link</a>.

    <Columns cols={2}>
      <Card title="Link Account" href="/connectors/fathom/guides/link-account/api-key" icon="https://stackone-logos.com/api/fathom/filled/png" horizontal>
        Fathom - API Key
      </Card>
    </Columns>
  </Step>
</Steps>

<section data-guide-section data-guide-scopes="">
  <h2>How Fathom Webhooks Work</h2>

  <p>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.</p>

  <Steps>
    <Step title="Automatic webhook registration">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>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).</p>

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

    <Step title="Verify in Fathom settings">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>You can verify the webhook was created by checking your Fathom account settings.</p>

        <ul>
          <li>Sign in to your <a href="https://fathom.video" target="_blank" rel="noopener noreferrer">Fathom account</a>.</li>
          <li>Click <strong>Settings</strong> in the navigation bar.</li>
          <li>Scroll to the <strong>API Access</strong> section and click <strong>Manage</strong> next to your API key.</li>
          <li>Under <strong>WEBHOOKS</strong>, you should see a StackOne webhook URL listed with all scopes and events enabled.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available Webhook Events</h2>

  <p>Fathom sends a single event type with rich meeting data.</p>

  <Steps>
    <Step title="New Meeting">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Fired when a new meeting recording is processed and content is ready.</p>

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

## 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.