Key Takeaways
- As at 14 November 2026, Fathom's native HubSpot and Salesforce integrations put meeting summaries and action items into matched CRM records, subject to each integration's matching rules.
- As at 14 November 2026, Fathom's HubSpot help centre requires Business or Enterprise for summary sections to update deal fields, and field mapping supports text properties.
- Fathom's Salesforce integration excludes Leads and closed Opportunities, so businesses using those records need another way to handle meeting updates.
- Other CRMs need a connected workflow, such as Zapier or a custom connection using Fathom webhooks and its API, with explicit rules for matching the correct record.
- Fathom stores all customer data in the United States and uses de-identified customer data to improve its own AI models unless users opt out.
Start with Fathom's native connection if you want summaries on HubSpot or Salesforce records. For stage changes, checked next steps or draft follow-up emails, I'd design a separate approval step around the proposed changes. That is the part of CRM automation I would scope before connecting anything.
What Does Fathom's Native CRM Integration Actually Write?
A summary on the timeline gives the next person context. Updating the next-step field, assigning a task and changing a deal stage require rules about what the call actually established.
The native behaviour below is documented as at 14 November 2026.
| Connection | What Fathom writes | What to check |
|---|---|---|
| HubSpot | A summary note under the Meeting event. Action items added after the call create tasks in Fathom and HubSpot. | Editing the summary or adding action items causes the call to re-sync (HubSpot guide). |
| Salesforce | The AI summary becomes a Task, logged as a call, on the matched Contact. | Leads are excluded. Only open Opportunities receive new activity (Salesforce guide). |
| Mapped fields | Defined summary sections can populate selected CRM fields. | HubSpot supports text properties. Salesforce mapping availability needs checking in your account (HubSpot field rules; Salesforce rollout status). |
In Salesforce, a mapped summary section overwrites the existing field value. I'd check that behaviour against your team's use of the field before enabling it (Salesforce overwrite rule).
Which Fathom Plan Do You Need for CRM Sync and Field Mapping?
Fathom's published plan descriptions overlap. As at 14 November 2026, the CRM overview says core sync starts on paid individual plans, while the HubSpot guide also lists limited connections for Free and Team users. Confirm your account's entitlement before buying (CRM plan overview; HubSpot plan details).
| Feature | Published requirement as at 14 November 2026 |
|---|---|
| HubSpot summary-to-deal-field sync | Business or Enterprise, according to the help centre. Use this requirement when planning field updates. |
| HubSpot card | Business, with HubSpot connected at organisation level. The card shows the last five meetings with summaries and recording links (card requirements). |
| Salesforce team connection | A Business-plan admin can connect under organisation settings (admin guide). |
| Salesforce field mapping | The admin guide documents mapping, but the CRM overview says rollout is underway. Check availability in your account (rollout wording). |
The overview mentions field mapping on Team and Business; the HubSpot help article specifies Business and Enterprise for deal fields. I'd resolve that with Fathom before committing. Check the pricing page and confirm currency, billing period and tax at checkout.
How Do You Connect Fathom to HubSpot or Salesforce?
- Connect with the right permissions. HubSpot connection requires a HubSpot Admin. Organisation-level field mapping requires someone who is both a Fathom Account Admin and HubSpot Super Admin (HubSpot setup).
- Check Salesforce access. The connecting user needs object-level edit permissions on Contact, Account, Opportunity and Task (Salesforce permissions).
- Test a scheduled external call. Use an invited attendee whose primary email matches the CRM Contact. Inspect the resulting summary and record association (HubSpot matching; Salesforce matching).
- Test field mapping separately. Check the destination property and existing value before allowing automatic writes.
For the surrounding HubSpot setup, see HubSpot integrations worth setting up for SMEs.
Why Do Some Fathom Calls Fail to Sync to the CRM?
I'd check the attendee and record before changing the automation.
- HubSpot: the intended external contact must be invited to the scheduled meeting. Matching uses the primary email, so a secondary email will not match. Only scheduled calls on the main calendar sync; internal-contact calls are excluded (HubSpot matching rules).
- Salesforce: matching starts with the attendee's primary email and Contact, then follows the Account and linked open Opportunities. Leads, closed Opportunities and internal-only meetings are excluded (matching sequence; exclusions).
- Older calls: connection does not automatically backfill history. HubSpot calls from a disconnected period need individual syncing; Salesforce offers a manual Sync to CRM button for older calls (HubSpot history; Salesforce manual sync).
How Do You Connect Fathom to Pipedrive or Another CRM?
For Pipedrive or a job management system, plan a separate connection and verify that the destination exposes the actions you need.
- Zapier: Fathom supplies triggers for new summaries, action items, transcripts and recordings. Your workflow must find the correct contact or deal and choose the destination action (available triggers).
- Webhooks: Fathom can send events after meetings, optionally including summaries, transcripts and action items. Requests include a signature that the receiving system should verify (webhook documentation).
- API: keys belong to the creating user and access meetings that user recorded or that were shared with the user or team (API access rules).
I'd check plan access inside Fathom before choosing a route. Then test matching, duplicate handling and the destination's write permissions.
How Do You Turn a Synced Summary into a Checked CRM Update?
For a builder's sales call, I'd propose this workflow:
- Trigger: receive Fathom's meeting content through a webhook or Zapier trigger.
- Gather context: retrieve the summary, action items, matched deal, current stage, last follow-up and open tasks.
- Prepare changes: draft a next step, any supported stage or close-date change, follow-up tasks and an email in the business's voice.
- Get approval: show the current and proposed values to the responsible person. Send missing matches, competing deals and closed records to review.
- Record the outcome: write approved changes, retain a recording link and log what changed.
If approval must happen before a field changes, leave native automatic mapping off for that field.
For an Australian service business that wants a checked workflow built and then run around Fathom and its existing CRM, Truespeak is built for exactly that. I've built CRM reactivation systems such as Agent Helper, which scores contacts in a real estate CRM and produces ranked call cards with the reason to call. Truespeak designs, builds and runs CRM automation, monitors failures and reviews exceptions. Where no usable connection exists, the step stays manual. Start with a discovery call to scope the proposed workflow.
Where Is Fathom Data Stored, and What Should Australian Businesses Check?
As at 14 November 2026, Fathom says all data is stored in the United States. Fathom also uses de-identified customer data to improve its proprietary models, with individual and organisation-level opt-outs (data and training policy).
Before connecting customer records, check recording permissions, access, retention, offshore storage and the opt-out settings. Get advice on recording consent for your circumstances. My guide to AI access to your inbox and CRM covers access decisions; the Australian AI note-taker comparison helps if you are still choosing a tool.
Frequently Asked Questions
What does Fathom write into HubSpot and Salesforce?
Fathom puts a summary note under the HubSpot Meeting event and logs a Salesforce summary as a Task on the matched Contact. Action items can become HubSpot tasks. Separate field mapping can populate selected fields, subject to plan and availability.
Which Fathom plan supports HubSpot deal field updates?
As at 14 November 2026, Fathom's HubSpot help centre specifies Business or Enterprise for summary-to-deal-field sync. Mapping supports text properties. Confirm the entitlement in your account because the CRM overview uses different plan wording.
Why are some Fathom calls missing from the CRM?
Check the invited external attendee, primary email and supported record type. HubSpot requires scheduled calls on the main calendar. Salesforce excludes Leads, closed Opportunities and internal-only meetings. Connecting does not automatically backfill older calls.
Can Fathom update Pipedrive or a job management system?
A separate workflow can use Zapier, webhooks or the API, provided the destination supports the required connection and actions. The workflow needs rules to identify the correct contact, deal or job and handle uncertain matches.
Can a person approve CRM changes before they are written?
A proposed custom workflow can hold field changes, tasks and follow-up emails for review before writing or sending them. Leave native automatic mapping off for any field that requires prior approval.
Is Fathom data stored in Australia?
As at 14 November 2026, Fathom says all data is stored in the United States. Fathom uses de-identified customer data to improve its proprietary models unless users opt out. Australian businesses should review access, retention, recording permissions and offshore storage.
Sources
Checked 13 Nov 2026.
