Fathom Notion integration

Fathom to Notion without Zapier

Fathom already writes the notes. The missing piece is putting that row in the Notion database you actually use—not a Zapier basket, and not a Make scenario you have to babysit.

Updated 16 Sep 2026 · About 5 minutes to first row

Why the official path still goes through Zapier

Fathom’s Notion integration page tells you to connect through Zapier or Make. That is the native answer today: there is no Fathom UI where you pick a Notion database and map Title, Date, Attendees, Summary, Action items, and Recording URL. See the official page: fathom.ai/integrations/notion.

Zapier Professional is $19.99/month on annual billing for 750 tasks, and the free tier is two-step only. Pricing: zapier.com/pricing. If you already pay Fathom, that second platform exists only to write a row you could have written yourself.

Webhooks themselves are documented for every Fathom plan, including Free. Confirm on Fathom workflow automation and developers.fathom.ai/webhooks before you start—if Fathom later gates webhooks behind a paid plan, this path changes.

What “Fathom to Notion database” should mean

Consultants and researchers do not want every call in one dump. They want the discovery call under Client A’s Sessions database, the interview under a Quotes database, the support call under CS. A Zapier template usually lands in one hard-coded database. Sessary asks you to pick the database and map the fields. The next Fathom recording writes one Notion page. Retries do not create a second row.

Bind it once: token, database, webhook

Follow this order. Do not start in Fathom. If Notion cannot see the database, the webhook will fail after the meeting and you will think Fathom is broken.

1. Create a Notion connection. Open app.notion.com/developers/connections, new connection, Access token, Read + Insert. Paste the token into Sessary and tap Test. You should see your workspace name.
2. Share the database with that connection. In Notion: database → ••• → Connections → invite the connection you just named. If the Sessary list is empty, this step is missing.
3. Map fields. Title is required and must be a title property. Date only maps to date. Recording URL only maps to url; if you have no URL property, Sessary puts the link in the page body. Skip any slot you do not use.
4. Copy your webhook URL (https://sessary.com/h/<id>) into Fathom User Settings → API Access → Add Webhook. Enable include_summary and include_action_items. Leave include_transcript off. Set triggered_for to your recordings.
5. Record a 2-minute test call. Fathom fires new-meeting-content-ready after the notes are ready. Payload fields: webhook payload docs. Sessary’s dashboard shows a green delivery and a Notion deep link. That is first success.

No live meeting? The dashboard can send sample JSON into your database, titled with [test]. Delete that row anytime.

What gets written

• Title from meeting_title, else title
• Date from scheduled_start_time
• Attendees from calendar_invitees names
• Summary from default_summary.markdown_formatted
• Action items as description + assignee name, one line each
• Recording URL from share_url, else url

The same recording_id posted three times still creates one Notion page. A bad signature or a timestamp older than five minutes is rejected and never written.

Related

Sources

• Fathom Notion integration (Zapier / Make)
• Fathom webhook docs
• Zapier pricing