TL;DR: Fathom’s native Salesforce integration writes the AI call summary as a logged-call Task on the matched Contact and can map summary sections onto Opportunity fields (“Deal View”) — but team-level connection and field mapping require Fathom’s Business plan ($25/user/mo annual), and the matching has hard edges: no Leads, no closed Opportunities, primary email only.
Fathom is many teams’ favorite recorder (deservedly — the free tier is the best in the category), and its Salesforce integration is more thoughtful than most. It’s also more opinionated than most, and the opinions are worth knowing before you turn it on. Verified against Fathom’s help docs (updated June 2026).
What it does
After each external call, Fathom writes the AI summary as a Task (logged call) on the matched Contact — created by the integration user but owned by the call’s host. Action items become separate Tasks. The clever part is Deal View: Fathom maps H3/H4 sections of its summary onto Opportunity fields you designate, so “Next Steps” or “Risks” from the call land in reportable CRM fields rather than a text blob.
Matching walks: participant’s primary email → Contact → Account → open Opportunity via OpportunityContactRole.
The gates
- Fathom Business plan ($25/user/mo annual, $34 monthly) for team-level connection and Deal View field mapping; below Business, CRM sync is capped at 3 users per domain.
- Salesforce REST API access — Enterprise, Performance, Unlimited, or Developer editions.
- OAuth as a connecting user with edit rights on Contact, Account, Opportunity, and Task, plus API Enabled.
The hard edges (all documented)
- No Leads support. If your pipeline lives in Leads before conversion, those calls don’t log.
- Closed Opportunities and internal-only meetings are excluded — post-sale teams take note: a renewal conversation after the opp closes doesn’t attach to it.
- Primary email matching only. A contact who joins from their other address doesn’t match. Secondary emails aren’t supported.
- Mapped fields are overwritten on each sync, and summaries truncate at 32,000 characters.
- Forward-only sync — historical calls need manual per-call “Sync to CRM.”
- Validation rules, record types, and territory management can silently block writes; Fathom’s docs include an error table worth bookmarking.
Reading the design
Every one of those edges points the same direction: the integration is built for an active-deal sales motion — open opportunities, known contacts, one CRM field per insight. Within that lane it’s excellent. Outside it — customer success, renewals after close, multi-threaded accounts, contacts who email from two addresses — the calls happen and Salesforce never hears about them.
That outside-the-lane data is precisely what Noded is for: Fathom is a first-class Noded integration, and calls flow into the Customer Context Graph matched to the account’s whole story — leads, closed opps, renewals, support tickets and all — rather than to a single open opportunity. Keep Fathom’s native sync for pipeline hygiene; it’s good at it. Use the graph when the question is bigger than the deal.
FAQ
What plan do I need for Fathom’s Salesforce integration?
Fathom Business ($25/user/mo annual) for team-level connection and Deal View field mapping; lower tiers cap CRM sync at 3 users per domain. Salesforce needs REST API access (Enterprise+).
Does Fathom log calls to Leads?
No — Contacts only. Leads-based pipelines don’t get call logging until conversion.
Does Fathom sync old calls?
Forward-only automatically; older calls can be pushed one at a time with “Sync to CRM.”