Fetafeta
Book a demo

Connect Fathom

draft · 2 image slots

Connect Fathom so completed meetings can land in Feta with their details, participants, summary, transcript, and action items. When Feta matches a meeting to a company, it appears in that company's Activity tab.

Any workspace member can open Settings → Call recording. An org admin must save or change the Fathom connection.

Connect Fathom

An org admin should complete these steps:

  1. Go to Settings → Call recording.
  2. Select Set up Fathom. Feta creates a Destination URL for the workspace.
  3. Select Copy URL.
  4. In Fathom, open Settings → API Access → Manage → Add Webhook.
  5. Paste the destination URL and choose recordings plus the meeting data you want Fathom to send.
  6. Create the webhook and copy the signing secret Fathom shows you.
  7. Back in Feta, paste it into Webhook signing secret.
  8. Select Save secret and wait for test.
  9. Record a short meeting in Fathom to test delivery.
The Fathom setup panel with its destination URL, four setup steps, and signing secret field.
The destination URL goes into Fathom; the signing secret comes back into Feta.

The status changes to Waiting for a test meeting after the secret is saved, then to Receiving meetings after Feta successfully processes a delivery.

What syncs

Each completed meeting can bring over its title, owner, participants, recording link, summary, transcript, and action items. Feta uses attendee information to match the recording to the relevant company. Matched recordings appear under Companies → the company → Activity, where you can open the recording and its summary.

The Received meetings table on the settings page shows the newest deliveries first, with the call title, participant count, call owner, received time, and one of three states: Processing, Received, or Needs attention.

The connected Fathom panel with a Receiving meetings badge and a received meeting row.
A received test meeting confirms the full path from Fathom to the workspace.

If the connection breaks

Use the status at the top of the Fathom panel:

  • Finish setup — the destination exists, but the signing secret has not been saved. Complete the Fathom webhook and select Save secret and wait for test.
  • Waiting for a test meeting — record a short meeting after saving the secret.
  • Needs attention — a meeting arrived but could not be processed. Check that the secret belongs to this webhook, select Replace secret, then send another test meeting.
  • The page says setup could not be loaded — refresh the page. If you are not an org admin, ask one to complete or change the connection.

The Received meetings table keeps failed deliveries visible with Needs attention, which lets you distinguish a delivery problem from a meeting that never reached Feta.

Related articles