What Four Sales Tools Send to HubSpot and Salesforce

What do Apollo and Wiza send to your CRM?

Apollo can move contact, company and deal information between its app and your CRM. Wiza's Two-Way CRM Sync Beta finds and updates selected details for entries from a CRM list. Choose the information you need to move before comparing either connection. Apollo connection modes, Wiza Beta documentation

A record is one saved entry; a field is one detail inside it, such as a phone number. Finding information to fill or update those details is called enrichment. In the tables, Contacts and Leads identify people or prospects, Companies and Accounts identify businesses, and Deals and Opportunities track potential sales.

Both tables reflect official documentation checked on November 1, 2026. Ask your CRM administrator to check the access column; the plan section explains the unresolved subscription questions.

Apollo's HubSpot Data Enrichment connection is a different mode from HubSpot CRM. It enriches existing HubSpot records but doesn't offer two-way record sync or push new records and activities. Pick the mode that matches the job; our Apollo and HubSpot comparison covers the broader product decision. Apollo's mode definitions

Suppose an existing contact has a missing phone number. Wiza's Beta workflow can take that contact from your selected CRM list, look for the requested information and return it to the same record. Don't assume this workflow can create new CRM records. Wiza's separate Auto-Sync sends a completed list once; Beta keeps watching a CRM list for new members. Wiza workflow and Auto-Sync distinction

What do Fireflies and Gong save after a meeting?

Fireflies can add notes and transcript links to your CRM, with separate follow-up Tasks if enabled. Gong uses your CRM's customer and deal details to organize calls and sends activity entries back. A note, a transcript link, a Task and a changed field are different results. Fireflies outputs, Gong CRM overview

Suppose a buyer asks for a proposal on Friday. Saving that request in a summary preserves context; creating a Task gives the team a separate follow-up record. Fireflies documents optional Tasks from action items, while Gong's HubSpot Meeting entry lists action-item text. Action-item text alone doesn't show that a separate Task was created. Fireflies task option, Gong Meeting contents

Fireflies can also pull HubSpot Dialer recordings into Fireflies. That inbound action is separate from sending notes back to HubSpot. If you need a deal field changed, ask for that action specifically; a saved note isn't evidence of a field update. Who attended the meeting and your record-creation settings determine which CRM entries receive it. Fireflies configuration

Gong can read selected CRM fields and send back changes you make to those fields in Gong. Its custom objects, extra types of Salesforce records for Gong data, need a separate Salesforce app. Your administrator still needs to choose what information to send each way. Our Gong overview provides broader product context. Gong CRM behavior, Salesforce permissions

If you're considering native meeting capture instead, the HubSpot note taker guide covers that separate choice.

What happens to past, changed or deleted records?

Old meetings, changed contact details and deleted calls don't all follow the same rules. Sending earlier information into a new connection is often called historical sync or backfill.

Apollo can pull supported existing HubSpot records, and its contact/account writing rules can fill empty fields or overwrite existing values. Its Salesforce setup pulls eligible records according to your settings; on paid Apollo plans, automatic syncing starts after a six-hour configuration window. Before using Apollo for a migration or cleanup, ask which older activities will transfer, which Salesforce values can be replaced and what deletions will do. Apollo HubSpot controls, Salesforce setup

Wiza Beta checks for new list members about hourly. Leaving the CRM list doesn't remove the Wiza row, and a processed record that rejoins isn't imported again. Use the separate List Automation to refresh existing rows instead of removing and re-adding them. The guide doesn't describe deleting the CRM record itself, so don't use list-removal behavior as a deletion policy. Wiza membership rules

Fireflies documents Push Past Meetings for both CRMs, using selected dates and meeting types with an existing push configuration. Gong's HubSpot FAQ says only newly processed calls are pushed after exports are enabled, yet another answer mentions initial historical-call traffic. If you need old Gong calls in HubSpot, get that coverage agreed before connecting. Fireflies HubSpot history, Salesforce history, Gong FAQ

The deletion event matters as much as the product. Deleting a Fireflies HubSpot configuration stops new writes but preserves entries already logged. Deleting a Gong call, including through a retention policy, deletes its linked HubSpot Meeting. Before deleting recordings, ask about the exact action: these HubSpot rules don't answer what deleting a Fireflies recording does, or how Gong deletion affects Salesforce. Fireflies configuration deletion, Gong call deletion

Disconnecting Fireflies from Salesforce stops future notes and tasks. For a cleanup, ask what happens to previous Salesforce entries and whether existing field values can be replaced; the setup page leaves those questions open. Fireflies Salesforce disconnection

If your team uses both CRMs, Apollo and Gong each document one connected CRM at a time. Apollo allows one HubSpot integration mode per team and can't connect a live Salesforce account and its separate testing environment (sandbox) simultaneously. Wiza's one-list rule doesn't say how many CRMs an account can connect. The cited pages don't confirm simultaneous HubSpot/Salesforce use for Wiza or Fireflies. Apollo limits, Salesforce environments, Gong limit, Wiza configuration

Which plan details need checking before you buy?

Ask the vendor whether your tool plan, CRM plan and connecting user's permissions cover the action you need. For example: “Will this plan create a follow-up Task in our CRM, or only add action-item text?”

Apollo's HubSpot connection needs a paid Apollo plan; check the tier for any advanced feature you need. For Apollo with Salesforce, the cited setup pages don't name a minimum plan on either side. Wiza's Beta plan and CRM-plan requirements are also unspecified; use our Wiza overview for context, then ask about Beta access for your chosen list rather than a general export feature. Apollo HubSpot access, Salesforce setup, Wiza requirements

Gong labels the basic connection available on any Gong plan, but features depend on the subscription and each user's assigned access, called a seat. Salesforce must allow Gong to read data through the REST API and write it back for exports. Ask which CRM plan meets those requirements: the guides don't name a minimum Salesforce subscription or say whether HubSpot needs a paid edition. Gong plan distinctions, Salesforce requirements, HubSpot permissions

Check the Fireflies action you need. Both setup pages label “Save meeting transcripts” Pro or higher and Integration Rules Business or higher. Those labels don't make every basic CRM action paid. The Free help page says all integrations are available, Pro pricing advertises unlimited integrations, and setup pages describe Free/Pro workspace controls. Confirm the particular note, link or task action your team needs. HubSpot setup, Salesforce setup, Free help, pricing

The Free plan also has conflicting allowances: Free help states 20 AI credits monthly, while the credits overview describes a one-time 20-credit allocation shared by the team. Pricing lists 400 storage minutes per team, while Free help says 400 per seat. Before relying on Free for regular work, ask when credits reset and whether storage is shared. AI credits measure advanced AI use, not a number of meetings; retained storage isn't a fresh monthly transcription quota. Don't multiply either disputed allowance by team size. Free allowances, credit definitions, storage pricing

Ask for a quote covering the chosen action and both subscriptions, with any extra usage charges listed separately.

Common questions about these HubSpot and Salesforce integrations

These questions help you decide whether the connection fits how your team works, including access to older meetings and continued use after a trial.

Can both CRMs stay connected to one tool?

Apollo and Gong allow one connected CRM at a time, so choose the destination before planning work across both CRMs. For Wiza and Fireflies, ask explicitly whether HubSpot and Salesforce can stay connected simultaneously; support for both brands doesn't answer that question. Apollo restriction, Gong restriction, Wiza list scope

Does a transcript-saving option copy the full text?

Fireflies' Pro-or-higher option wording says it saves transcripts, but its HubSpot instructions and deal guide explicitly describe a link instead of an attached transcript. Salesforce's resulting-record description also lists a link. If your team needs full text inside the CRM, ask to see that exact output; opening a link in Fireflies wouldn't demonstrate a copy. HubSpot wording, deal output, Salesforce output

Can I rely on free access for ongoing use?

Check the action after any trial ends, then confirm what happens when credits or storage run out. Fireflies' official pages disagree about Free access and allowances, so a working connection alone isn't enough to budget ongoing use. Free help, credits, pricing

Will old meetings appear as soon as I connect?

Fireflies provides a selected past-meeting push, while Gong's HubSpot history wording is contradictory. For a migration, agree on the date range before enabling the connection, and ask about Gong's Salesforce history separately from HubSpot. Fireflies history, Gong history

Check one record before expanding the connection

Pick one outcome, such as adding a missing phone number or creating a follow-up Task, and agree with your CRM administrator on a test contact or meeting. This is a proposed check that we haven't performed.

• Note both plans, trial status and connection permissions
• Use the agreed test contact or meeting
• Inspect the saved text, link, Task or field
• Compare usage and record corrections or failed steps

Open any transcript link and check where it leads. If you expect a Task, check its owner and due date. For a contact update, compare the chosen field before and after, including any value that should stay unchanged. Record usage changes and any work you had to do manually; one successful check still won't resolve a disputed monthly allowance.

Use the Fireflies product overview if meeting notes are your next evaluation. Start with the one action your team needs, then expand only after its output and access conditions are clear.