Fathom webhook Notion

Fathom notes not showing up in Notion

Sessary only writes after a signed Fathom webhook. If the dashboard has no green row, the meeting never reached a successful Notion page create. Do not start by recording another long call.

Updated 20 Sep 2026 · First check the delivery log, not Fathom’s transcript

Read the dashboard before you change anything

Open Sessary → Dashboard. The last ten deliveries show time, title, success or failure, and a Notion link. They never show the meeting body. Use that line to pick a branch below. If you have not connected yet, start with the setup guide instead of this page.

No delivery at all — Fathom never reached /h/<id>. Fix the URL, wait for notes to be ready, or confirm API Access is on.
Red: signature failed — the whsec_ secret or destination URL does not match.
Red: Notion 401 — the connection token is wrong or revoked.
Red: Notion 403/404 — the database is not shared with that connection, or a mapped property was deleted.
Green: duplicate, ignored — the same recording_id already wrote a page. Look in Notion, not in Fathom retries.
Red: trial_expired — Fathom still gets HTTP 200 so it stops retrying, but Sessary skipped the Notion write. Subscribe, then record a short test call.

Empty database list, or Notion 403/404

The connection cannot see the library. In Notion open the database → ••• → Connections → invite the connection you named in Sessary. Come back and click Refresh databases. You do not need a new Fathom meeting for this.

If Test connection fails, create a new Notion connection (Access token, Read + Insert), paste the new token, and test again. Do not paste a page URL or a Notion share link.

Webhook never arrives

Copy the destination from the dashboard. It must look like https://sessary.com/h/ plus your id. A homepage URL or a Zapier hook will never write through Sessary.
In Fathom User Settings → API Access → Add Webhook, paste that URL. Enable include_summary and include_action_items. Leave include_transcript off. Set triggered_for to your recordings.
Paste Fathom’s whsec_ signing secret into Sessary. Real meetings are rejected without it.
Wait until Fathom has finished the notes. The event is new-meeting-content-ready, not the moment you hang up. Docs: developers.fathom.ai/webhooks.

No live meeting? Send sample JSON from the dashboard. It writes a [test] row into your database. If sample JSON works and Fathom does not, the break is on the Fathom webhook, not Notion.

Row appears with an empty summary

The webhook ran, but Fathom did not include the summary. Edit the webhook and turn include_summary on. Action items need include_action_items. Sessary will not invent a second AI summary.

Trial ended, Fathom still says 200

After the 30-day trial, Sessary returns 200 so Fathom stops retrying, and it does not create a new Notion page. The dashboard logs that delivery as a red trial_expired line, not a green success. Rows already in Notion stay. Open the dashboard, choose $9/month or the early-bird lifetime plan, then record a two-minute test call.

Mapped property disappeared

If you deleted the Date or URL property Sessary was mapping, new meetings fail on purpose instead of writing a half-row. Remap the slots, then send sample JSON. Old Notion pages are not rewritten.

Notion asked you to wait

If Notion rate-limits the write, wait a minute and use Fathom’s retry or sample JSON. Sessary does not queue meetings, and it still de-duplicates by recording_id.

Still stuck?

Email support@sessary.com with the delivery timestamp and the error code from the dashboard — not the meeting transcript. We reply within 3 business days.

Open setup