Skip to main content
Fathom uses OAuth. After you authorize, Yuzu provisions a webhook in Fathom’s system automatically — there’s no URL to copy and paste. Auth method: OAuth 2.0 (public_api scope).

​
Prerequisites

  • A Fathom account with API access enabled.
  • Permission to authorize third-party integrations on your Fathom workspace.
  • Fathom must be set to record and transcribe the meetings you care about (Zoom, Google Meet, or Microsoft Teams).

​
Setup

1

Open Yuzu Settings → Integrations

Go to Settings → Integrations and click Connect Notetaker, then choose Fathom.
2

Authorize Yuzu in Fathom

Yuzu redirects you to Fathom’s OAuth page. Sign in if you aren’t already, then approve the public_api scope.
3

Wait for the webhook to provision

Once you authorize, Yuzu creates a webhook in Fathom on your behalf and stores the webhook ID. You return to Yuzu’s settings page with Fathom marked as connected.
4

Optionally sync recent meetings

From the connected state, click Sync Meetings and pick Last 7 days, Last 2 weeks, or Last 4 weeks to backfill transcripts. Yuzu also auto-starts a 7-day sync right after you connect.
If you ever need to rotate the connection, click Regenerate in the Fathom row of the integrations page. Yuzu deletes the old webhook in Fathom and provisions a new one — no manual reconfiguration needed.

​
What gets pulled

For each completed meeting, Yuzu imports:
  • The full transcript with diarized segments (segments[] with speaker, text, start_time, end_time).
  • Title, call date, participants, and duration.
  • Fathom’s summary and action items.
  • The recording URL.
Sales calls flow into your automation rules and can trigger a recap video.

​
Webhook signature verification

Yuzu verifies every Fathom webhook using the webhook-id, webhook-timestamp, and webhook-signature headers Fathom sends. The HMAC secret is generated by Fathom when the webhook is created and stored on the integration record — you don’t need to manage it.

​
Troubleshooting

Make sure your Fathom plan includes API access. If it does, try clearing cookies for fathom.video and reauthorizing. The error response Fathom sends back is also surfaced in your Yuzu activity log.
Disconnecting in Yuzu deletes the webhook and revokes the integration locally. To remove the Yuzu OAuth grant entirely, go to your Fathom account settings and revoke Yuzu under connected apps.
Check Settings → Automations → Activity log. If no entries appear after a recorded meeting completes, click Regenerate in the Fathom row of Yuzu Integrations — this re-provisions the webhook.
Fathom labels speakers based on the meeting host’s account. External attendees often appear as a single speaker. If pristine diarization matters, prefer Fireflies or HubSpot.