# 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 `pages` call. Do not start by recording another hour-long call.

HTML: https://sessary.com/guides/fathom-notion-troubleshooting/

Happy-path setup: https://sessary.com/guides/fathom-to-notion-without-zapier/index.md

## Empty database list, or Notion 403/404

The connection cannot see the library. In Notion: database → ••• → Connections → invite the connection you named in Sessary. Then refresh the list. Token errors need a new connection token, not a new meeting.

## Webhook signed, but no Notion row

Paste the full `/h/<id>` URL. Save Fathom’s `whsec_` secret in Sessary. Enable `include_summary` and `include_action_items`. Leave `include_transcript` off. Wait until Fathom marks the notes ready; the event is `new-meeting-content-ready`, not hang-up.

A red “signature failed” line means the secret or URL does not match. A green “duplicate, ignored” line means the same `recording_id` already wrote a page. A red `trial_expired` line means Fathom still got HTTP 200, but Sessary skipped the Notion write.

## Trial ended

Expired trials still return 200 to Fathom so it stops retrying, but Sessary does not write a new page. The dashboard shows that delivery in red with `trial_expired`, not as a green success. Rows already in Notion stay. Subscribe from the dashboard to resume.

## Property missing

If you deleted a mapped Date or URL property, new meetings fail on purpose instead of writing a half-row. Remap, then record a short test call or send sample JSON.