Fathom webhook Notion

Fathom notes not showing up in Notion

If your Fathom meeting notes are not appearing in Notion, check the Sessary delivery log before recording another test call. The usual causes are an unshared Notion database, an incorrect webhook URL or signing secret, missing summary fields, or an expired trial.

Updated 21 Sep 2026 · Start with the delivery log, not the transcript

Read the dashboard before changing anything

Open Sessary → Dashboard. The last ten deliveries show time, title, success or failure, and the Notion link. They never show the meeting body. That status line tells you which problem you have before you touch Fathom or Notion again. If you have not connected Sessary 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 enabled.
Red: signature failed — the whsec_ secret or destination URL does not match.
Red: Notion 401 — the connection token is wrong, expired, 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. Search Notion before retrying.
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.

Why does my Fathom webhook not trigger in Notion?

Copy the destination from the Sessary dashboard. It must look like https://sessary.com/h/ plus your account id. A homepage URL, a Zapier hook, or a Notion share link will never write through Sessary.

Open Fathom User Settings → API Access.
Choose Add Webhook and paste the full Sessary URL.
Set triggered_for to your recordings.
Enable include_summary and include_action_items. Leave include_transcript off.
Save the Fathom whsec_ secret into Sessary. Without it, the webhook is rejected.
Wait until Fathom has finished generating the notes. The correct event is new-meeting-content-ready, not the moment the call ends.

Docs: developers.fathom.ai/webhooks.

Why does Fathom webhook signature fail?

Sessary rejects unsigned or incorrectly signed requests. Copy the full Fathom secret into the Sessary setup or dashboard. Do not paste an extra space, a truncated value, or a secret from a different webhook.

If Fathom rotated the secret, update it in Sessary. If the webhook URL was changed, update both sides. A valid URL paired with a secret from another webhook still fails verification.

Why is my Notion database list empty?

The connection cannot see the library. In Notion open the database → ••• → Connections → invite the connection you named in Sessary. Then return to Sessary and refresh the database list.

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

Why does Notion return 403 or 404?

The database is usually not shared with the connection, or the mapped property was deleted after setup. Share the database with the same connection used in Sessary and review the mapping.

If the database is visible but the write still fails, send sample JSON. A mapped Date property must still be a Date field, and a mapped Recording URL must still be a URL field. Remap deleted or changed properties before testing again.

Why is my summary or action items missing from the row?

The webhook ran, but Fathom did not include the fields. Edit the webhook and enable include_summary and include_action_items. Sessary will not reconstruct the summary from a transcript.

Leave include_transcript unchecked for the normal workflow. Sessary is a narrow delivery pipe, not a transcript archive.

Why is the same Fathom meeting not creating another Notion row?

This is expected. Sessary deduplicates by Fathom recording_id, so retries of the same event create one Notion page. A green duplicate, ignored line means the original page already exists.

Use the Notion link in the successful delivery to find the row. Do not create a second webhook just to force a second page.

Why did my Fathom meeting stop writing after the trial ended?

After the 30-day trial, Sessary returns HTTP 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 instead of a green success.

Choose a plan, then record a short test call or send sample JSON from the dashboard. Existing rows stay where they are; Sessary does not replay a payload later.

What should I do when a mapped property disappeared?

If you deleted the Date, URL, or another mapped field, new meetings fail on purpose instead of writing a partial row. Remap the slots, then send sample JSON.

Existing Notion rows are not rewritten when the mapping changes. Only future deliveries use the new mapping.

What if Notion rate-limits the write?

If Notion asks Sessary to wait, try again after a minute and use Fathom’s retry or sample JSON. Sessary does not queue payloads, but it does reject duplicate recording_id writes.

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 for setup, billing, and delivery issues.

Open setup