AI agents trained on Fathom + Notion data
Linked Fathom and Notion history pairs sales history with document and knowledge history. That joined record is what lets an AI agent follow a job from one team to the next.
Get matched with buyersFree. No obligation. You approve every step.
We may earn a referral fee from buyers we list. Buyers, not us, pay you, and fees can affect which offers we show. See how we make money.
What happens between Fathom and Notion today
Zapier publishes 4 named templates connecting these two apps (Zapier integration page). In plain terms, the most common hand-offs are:
- A new Fathom AI Summary creates a Notion record.
- A new Fathom Action Item creates a Notion Database.
- A new Fathom AI Summary creates a Notion Database.
- A new Fathom Transcript pulls a Notion record.
On the Fathom side the trail runs through Action Item, Video, Recording, AI Summary; on the Notion side through Page, Comment, Block, File.
Beyond this pair, Zapier users most often connect Fathom to Google Drive, ClickUp, Google Docs, and Notion to Google Calendar, Tldv, Google Tasks.
What an agent trained across both could do
Each of these needs records from both systems at once:
- Account briefs. An agent that compiles Fathom Transcript history into a Notion Page per account so anyone can get up to speed in minutes.
- Cross-system look-ups. An agent that answers questions that need both Fathom Action Item records and Notion Page records at once, such as what happened to a customer after a hand-off.
- Hand-off checks. An agent that spots work that left Fathom as a Video but never showed up in Notion as a Comment, using past hand-offs as the pattern.
Why buyers pay more for linked histories
Joined Fathom and Notion records let a model see a full workflow, not two disconnected logs. SourceX says it prefers many in-scope systems: a complete application list of five or more, with at least three needed to submit (SourceX seller guidance).
Side by side
| Fathom | Notion |
|---|---|
| Action Item | Page |
| Video | Comment |
| Recording | Block |
| AI Summary | File |
| Highlight | Data Source Item |
| Transcript | Database |
| - | Block Children |
| - | Page Comments |
| - | Page or Data Source Item |
Buyers that want either side
Buyers that license crm and sales records or documents and internal knowledge, quoted as published.
micro1 buyer
- What they buy
- “Operational records: SOPs, process docs, knowledge bases, internal comms, CRM and support history”
- Size fit
- 30+ employees
- Closed companies
- Yes: “Separate program for defunct companies”
- Payout as published
- “$100K–$3M+ (marketed range for approved data packages)”
SourceX buyer
- What they buy
- “Support conversations, CRM, engineering and workflow histories”
- Size fit
- 50+ full-time employees at peak
- Closed companies
- Yes: “Operating, acquired and wound-down companies can qualify”
- Payout as published
- “Up to $4M (SourceX says this is an upper bound for the largest datasets, not typical)”
Replay buyer
- What they buy
- “Code and commits, decision threads, financial records, product logs, CRM”
- Size fit
- 20+ employees (lowest band shown)
- Closed companies
- Not published
- Payout as published
- “Shows bands by headcount (20–50, 50–250, 250+); see Replay's page”
AfterQuery buyer
- What they buy
- “Records of how teams work across email, chat, tickets, CRM, finance and industry systems”
- Size fit
- Not published
- Closed companies
- Not published
- Payout as published
- “Not published (terms proposed after reviewing a sample)”
Ventra broker
- What they buy
- “Email, chat, tickets, CRM, documents; CAD, video and game files”
- Size fit
- 30+ staff in US, UK or Canada (reported)
- Closed companies
- Not published
- Payout as published
- “$100K–$2M potential deals (reported by AI Data Payout)”
Mode buyer
- What they buy
- “Email and calendar, documents, operating records (filtered, agreed copy)”
- Size fit
- Minimums vary by industry (Mode's release: 20 US office staff generally, 10 for accounting, 6 for law firms)
- Closed companies
- Not published
- Payout as published
- “$100K–$5M (Mode's headline; calculator is indicative only)”
Buyer terms are quoted from each program's published page as of 2026-11-16; we don't edit them. How we check them: methodology.
What to strip before licensing
- Customer and prospect names, emails and phone numbers (PII) are removed or tokenised.
- Call recordings and transcripts are de-identified; consent rules for recorded calls are checked.
- Payment card numbers or bank details pasted into notes are stripped.
- Personal notes about individuals that are not business records are excluded.
- Files with personal data about customers or staff (PII) are excluded or de-identified.
- Contracts are checked for confidentiality clauses that forbid sharing; third-party confidential files are excluded.
- Employee HR files, payroll exports and ID scans in shared drives are excluded.
- Privileged legal material and any health information are excluded.
- Buyers de-identify records before training, and you can ask for their method in writing.
- An NDA is signed before any sample leaves your systems.
- You approve the data scope: which systems, which years and which fields.
What it could be worth
- micro1's own estimator API returns about $184,925 for a US company with 30 employees and 3 years of records, and about $239,192 at 50 employees and 5 years (low end of its range). Published calculator output (low end), not a quote Source: micro1 data estimate.
- SourceX's public estimator starts at $50,000 for 50-99 employees and $100,000 for 100-999 employees (low end of each band); 50+ peak full-time employees required. Published band (low end) Source: SourceX estimator.
Buyers price the company's whole dataset: how many systems, how many years and how many people produced it, not a single app. No per-app price exists, and these figures are not a quote or a guarantee.
Sources
- Zapier: Fathom + Notion integrations
- Zapier: Fathom
- Zapier: Notion
- micro1 data estimate
- SourceX estimator
- SourceX seller guidance on in-scope systems (no public URL; summarised)
FAQ
Which Fathom and Notion records connect?
Mostly Action Item and Video records in Fathom, and Page and Comment records in Notion. The agent jobs above (account briefs, cross-system look-ups, hand-off checks) show how they combine.
Do I need both Fathom and Notion to sell data?
No. Either can be licensed alone, but buyers price the whole company dataset, so linked Fathom and Notion history is usually worth listing together.