Avoma CRM Integration: Salesforce and HubSpot Setup, What Syncs

Avoma connects to one CRM per organization. Salesforce, HubSpot, Pipedrive and Zoho link through a single OAuth sign-in, while Copper and Zendesk Sell are assisted connections: an admin generates an API key in the CRM and sends it to Avoma Support ^[1]. Once the link is live, AI notes save automatically to account, opportunity and contact records on every paid plan. Updating CRM fields in both directions and logging Gmail or Outlook email are a separate layer. That layer is the Revenue Intelligence add-on. For HubSpot and Salesforce, only an Avoma Super Admin can configure the connection. One person sets it up once.

Which CRMs connect, and who clicks Connect

The self-serve path in Avoma's help runs through Settings → Integrations: find your CRM provider among Salesforce, HubSpot, Zoho and Pipedrive, click Connect and follow the provider's sign-in steps. The connection covers the whole Avoma organization. Reps never authenticate their own CRM accounts. The person doing it needs admin rights in both Avoma and the CRM, and for HubSpot and Salesforce the bar is higher: only Super Admins configure those two, while ordinary Admins manage billing, users, recording policies and lighter integrations such as Outreach and Aircall.

Copper and Zendesk Sell have no Connect button. Your admin generates an API access key inside the CRM and emails it to help@avoma.com or to the Customer Success Manager, and Avoma finishes the link. Only one CRM can be connected at a time. Disconnecting also goes through Support. Avoma's help warns that features differ by CRM because each platform's API differs, and the deepest tooling sits on two systems: forecasting works with Salesforce and HubSpot only, and the help pages on importing CRM fields and mapping pick-list fields cover those same two.

The lighter CRMs still do the core job. Pipedrive receives notes on Contact, Company or Deal records, and a note edited in Avoma updates the same note in Pipedrive rather than adding a copy. Copper matches participants to Leads, Accounts or Opportunities and re-syncs notes after later edits. Teams that plan to buy forecasting later should weigh that split before choosing a CRM path. Switching costs a Support ticket.

What saves to the CRM on every paid plan

Auto-saving AI notes to CRM records (Account, Opportunity, Contact) is listed on all three plans in Avoma's pricing matrix ^[2]. Avoma matches meeting participants to existing records and writes the summary there, so a discovery call lands on the right deal without copy and paste. AI follow-up emails sent through Gmail or Outlook are logged to the CRM too, and Automations can turn action items into HubSpot tasks. Paid plans start at $19 per recorder seat per month, billed annually (Startup).

Two rules decide whether a meeting syncs. The first is privacy: meetings set to Organization or Public sync automatically when a matching record exists, while Private meetings need a manual push. Avoma's defaults put internal meetings on Private and external ones on Organization. Customer calls flow; stand-ups stay out. The second is the seat. Avoma's Salesforce guide says CRM sync needs Recorder licenses because it requires a paid subscription. Viewers are free, but they create no CRM notes. Avoma has no free recording plan, and after the 14-day trial an unpaid account becomes a viewer; the Avoma pricing breakdown covers that rule and the seat math.

Field updates and email sync: where the add-on starts

The pricing page puts 2-way CRM field updates inside the Revenue Intelligence add-on. That add-on costs $29 per seat per month billed annually or $35 billed monthly, on top of a base plan, assigned only to the people who need it. By our arithmetic that is $348 per seat a year billed annually against $420 billed monthly. Some Avoma product pages advertise two-way sync without naming a plan. Pricing decides. Notes come with every plan; two-way field updates come with the add-on.

The same add-on gates native Gmail and Outlook email sync. Help says synced emails are logged only to Salesforce, as Tasks, or to HubSpot, as email records. One Salesforce quirk matters for clean data: when no Account matches the sender's email domain, Avoma creates a Lead instead of a Contact. Revenue Intelligence also writes back deal-level output. AI win-loss analysis records why a deal was won or lost when it closes, and the Deal Health Score needs the deal owner to hold the add-on.

How mapped fields behave

Field mapping ties a Smart Topic to a CRM field. Once mapped, data flows outbound from Avoma; read-only CRM fields flow inbound; editable fields you have not mapped stay bidirectional. Smart Topic field mapping works on Opportunity or Deal and Account or Company objects (plus Salesforce Event and Task fields since October 2026, where eligible), and custom objects are a request to Support. Single-line text fields cannot be mapped because of their 255-character limit ^[3]. Use multi-line text. One Smart Topic maps to one field, the types must match, and each new meeting appends to the field instead of overwriting it.

When you map a field, Avoma syncs back every open deal modified in the last 90 days. On the HubSpot side, changes made in HubSpot reach Avoma every 30 minutes, while deal-stage changes made in Avoma reach HubSpot immediately. Need it sooner? A refresh button in the meeting view pulls the latest record on demand, which helps right before a pipeline review when a rep has just moved a stage.

Salesforce set-up: three switches decide everything

Most failed Salesforce syncs trace back to one of three settings. Check them in this order before you touch field mapping or blame the connection itself:

• Permissions and seats: the person configuring must be both an Avoma admin (Super Admin) and a Salesforce admin, and the Avoma account must include Recorder licenses ^[4].
• Enhanced Notes: it must be enabled in Salesforce for Leads, Accounts and Opportunities, or synced notes will not display properly.
• The notes setting on both sides: after you turn on Auto sync notes in Avoma, a Salesforce admin also has to enable the notes setting in Salesforce, or the sync fails.

Next, choose where meeting notes land: a Salesforce Note, the Event description or Task comments, with call notes routed elsewhere if you want. The configurable objects are Opportunity, Lead, Contact, Account, Event and Task. Settings exist at organization, individual and member level, and a locked organization setting overrides every personal choice. Avoma can also create Salesforce Contacts for external participants, with rules by team and an option to skip public email domains.

Edits made in Avoma flow to Salesforce. The reverse never happens. Fix notes in Avoma first. When an account has several open opportunities and Avoma cannot pick one, a user can link the meeting to the right record by hand. Avoma's October 2026 update added mapping of Avoma Properties and Smart Topics to Salesforce Event and Task fields; Avoma says availability varies by use case and plan, and the Customer Success Manager explains the options.

HubSpot set-up: destinations, contacts and booking data

An Avoma Super Admin completes the first HubSpot connection, and field mapping needs HubSpot admin-level permissions to view, edit and create the properties involved. Meeting notes can go to a HubSpot Note attached to the related records or into the Internal Notes field of a HubSpot Meeting, and Avoma can auto-create the Meeting itself. Call notes can go to a Note, a Meeting or an existing Call. Smart Category mapping works at the Deal and Company levels only. The currency label setting is display-only. It converts nothing.

Contact creation comes in two flavors. From meetings, Avoma can create HubSpot contacts out of external participants by rule, excluding public domains such as Gmail or Yahoo; the same exists for Salesforce. From bookings, saving the contacts who book through a scheduling page into the CRM is a feature of the Lead Router add-on. That add-on costs $19 per seat per month billed annually or $25 billed monthly. The router also writes Booking Source, Booking Status, Meeting Creation Date and Meeting Outcome to HubSpot and Salesforce, once admins create those custom fields with the exact names. Inbound form routing reads HubSpot and Marketo forms only, even on Salesforce. The Avoma Scheduler guide covers the routing rules.

When notes do not reach the CRM

Avoma's help pages point to a short list of causes, and most of them take a minute to confirm. Work through the list below before you open a ticket with Avoma Support, because a disconnect and reconnect also needs Support:

• The meeting is Private. Change its privacy or sync it manually.
• You upgraded recently. Notes sync only for meetings after the upgrade; push older ones by hand.
• Internal calls attach to customer records. Since June 2026, Automations rules can switch CRM association off by team, meeting purpose, outcome or title.
• A field refuses to map. Check for a single-line text field or a type mismatch.
• HubSpot shows duplicate events. The router's meeting-engagement setting plus a rep's own HubSpot calendar sync creates two; keep one.
• Ask Avoma misses a fresh deal change. It searches CRM data already synced into Avoma, not the live CRM. Refresh first.

The bottom line

Connecting Avoma to a CRM is an admin task done once per organization, and on HubSpot or Salesforce it belongs to a Super Admin who is also a CRM admin. Every paid plan saves AI notes to accounts, opportunities and contacts; the Revenue Intelligence add-on turns that into two-way field updates, email logging and forecasting. Salesforce teams should verify Enhanced Notes and the notes setting first. Start with notes, use multi-line fields for any mapping, and buy Revenue Intelligence seats only for the people who need two-way field updates, email sync or forecasting.