Gong HubSpot Integration: What Syncs, Setup, and Why Updates Stop

Through Gong, not through HubSpot's app marketplace. The connection is made from Gong's Admin center under CRM settings, in four steps: connect the HubSpot account, choose which HubSpot fields Gong should import, configure how Gong uses that imported data internally, and choose which of Gong's own activities export back out to HubSpot. Gong's own setup guidance recommends connecting with a dedicated integration user rather than a personal login, specifically because that user's HubSpot permissions are what determine which records and fields Gong can actually reach.

Per Gong's own export documentation, the activity types that flow back to HubSpot include meeting invites, web conference calls, telephony calls, emails, and, for teams using Gong Engage, tasks, LinkedIn messages and connection requests, and flow data. Gong flags that specific export page as something worth checking against your own admin screens rather than treating as permanently current, which is a reasonable caution to carry into any integration: confirm the exact list your account is set to export before relying on it for reporting.

Because the export is forward-looking by default. When the integration is first set up, Gong exports new activity going forward rather than backfilling everything that happened before the connection existed. Whether earlier calls and emails also make it across depends on the order in which the CRM integration and Gong's email or telephony integrations were connected, which is exactly the kind of setup detail that produces a confusing gap for a RevOps admin auditing coverage months later and finding calls from before a certain date simply missing.

Gong can keep refining an activity it already exported, for instance after a new call tracker fires on a trend it catches retroactively, but only inside a configured update window. Once that window closes, further changes Gong makes to its own record of the call no longer propagate to the HubSpot copy, which now sits frozen at whatever state it was in when the window ended. That is worth knowing before treating a HubSpot activity as a live mirror of what Gong currently shows for the same call.

Gong's export settings decide what reaches HubSpot's activity timeline, but nothing about that export is reviewed before it lands, and none of it updates a deal's stage, amount, or next step. Mindlyft sits on the same call content and drafts the specific field changes those activities imply, holding anything that touches a system of record for a one-click approval before it writes, with every approved change logged and reversible. See which A.S.T.R.A. actions need approval for exactly where that line sits.