Six hours before a call appears, and the transcript never does.
A Gong contract, a HubSpot tech admin, and a dedicated integration user
Activities, Deals, Contacts, Companies, two-way sync.
Gong reads your HubSpot accounts, contacts and deals, and writes call and meeting activity back onto the record, which is the point: the deal review happens where the deal lives. Three documented facts decide whether people trust it: the transcript is never exported, so HubSpot holds a summary and a link rather than the conversation; export can take up to six hours, so same-day reporting is always short; and if anything else already writes meetings, calls or emails to HubSpot, this will duplicate them unless you pick the object type deliberately.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Companies, contacts and deals | One way, out | Read out of HubSpot into Gong. Required fields include company domain, contact email and title, and deal name, stage, amount and close date. |
| Meetings and web conference calls | One way, in | As meetings, calls or notes. You choose one type and both use it. A meeting invite needs at least one external participant matching a HubSpot record. |
| Telephony calls | One way, in | As HubSpot call objects, carrying the Gong link, the spotlight brief, highlights, outline, action items and call metadata. |
| Emails | One way, in | Associated with HubSpot contacts, and only from the export date forward. Nothing is backfilled. |
| Engage activity | One way, in | Engage tasks and LinkedIn messages and connection requests, exported once the to-do is completed. |
| The transcript | Event only | Never. Gong documents that the call transcript is not exported, so the link back to Gong is the only route to it. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
This pair has a genuine field contract in both directions, and the interesting half is which HubSpot field types Gong refuses. Three types are unsupported outright and two are quietly truncated, which matters because a field that displays as empty in Gong is indistinguishable from a field nobody filled in.
| In HubSpot | In Gong | What to know about the match |
|---|---|---|
| Company | Domain, Name, Last Modified Date | The required minimum Gong accesses. Domain is the matching key, which is why an account with no domain never associates with anything Gong recorded. |
| Contact | Name, Title, Phone number, Email address, Associated Company Id | Email is what matches a meeting participant to a record, and the associated company ID is what rolls an activity up to the account. |
| Deal | Deal Name, Deal Stage, Amount, Close Date, Owner ID, Account ID, Last Modified Date | The forecasting set. Everything Gong says about a deal rests on these six fields being populated and current in HubSpot. |
| Custom fields, any object | Imported if a tech admin selects them | Fully supported fields are two-way: a value changed in Gong is written back to HubSpot. That is worth knowing before you let Gong edit a field your reps own. |
| Single-line text and dropdown select | Supported, truncated at 120 characters | Gong displays a maximum of 120 characters and trims longer picklist options. A long option reads as a different value rather than as a truncated one. |
| Date fields | Supported, epoch in milliseconds | Gong states the format requirement outright. A date arriving in any other format is the first thing to check when one field in an otherwise working import is empty. |
| Rich text | Limited support, formatting dropped | Viewable and editable in Gong, and an edit saves back to HubSpot without the formatting. So a round trip through Gong flattens the field permanently. |
| Multiple checkboxes, File, HubSpot user | No support | Three types Gong will not import at all. An owner-style HubSpot user field is on that list, which surprises teams who assumed owner data crosses as a user rather than as the deal's Owner ID. |
Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.
| The action | How it reads on the record |
|---|---|
| Meeting invites | As meetings, calls or notes, and only if one external participant matches a HubSpot record |
| Web conference calls | Added to the meeting invite's activity if invites are exported, otherwise created as their own |
| Telephony calls | Always as HubSpot call objects, including short calls under five minutes, unanswered attempts and answered but unrecorded calls |
| Emails | Against the matching contact, from the date export is enabled, never retroactively |
| Engage tasks and LinkedIn activity | Only when the to-do is marked complete, not skipped, and not imported from an external source |
| Engage flow data | Only into HubSpot custom fields you create first and add to the right layouts |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six action rows and three documented exclusions, each one's note, and the three vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The two tables disagree in a way worth noticing: HubSpot to Gong is a field contract that includes custom fields and writes back, while Gong to HubSpot is a set of activity streams with a condition on every one. That asymmetry is the integration. It is also why the install feels finished long before anybody can tell whether the conditions were met.
Gong puts this integration on any Gong plan, so there is no edition grid to draw and the real question is different. Three of the four export streams have a wide setting and a narrow one, and choosing the wide one while another tool writes the same activity is the documented way to fill a timeline with duplicates. Pick one on each side and the grid marks the answer.
Pick one on each side.
| The Gong export stream | No | Yes |
|---|---|---|
| Meeting invites and conference calls | the wide setting is safe | narrow it or get duplicates |
| Telephony calls | the wide setting is safe | narrow it or get duplicates |
| Emails | the wide setting is safe | narrow it or get duplicates |
| Engage tasks and LinkedIn | the wide setting is safe | the wide setting is safe |
Counted off that grid, of eight pairings: five give you the wide setting is safe, three give you narrow it or get duplicates. Read down the right-hand column and the pattern is that Gong has already written the answer for each stream; what it cannot do is know what else is installed in your portal. One practitioner in the threads below reached the same conclusion the slow way and now pushes everything as notes, which is the one object type nothing else in a normal HubSpot stack competes for.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
HubSpot: Settings, Users and Teams
Gong can access exactly what the connecting user can access, and it recommends a dedicated user for that reason. The permissions on that account are the boundary of the integration, and deactivating a normal employee account later disconnects it.
HubSpot: Settings, Integrations, Connected Apps
A calendar sync, a dialler or an email tool already filling the timeline is what turns this install into duplicates. Write down which activity types each one creates before you choose Gong's, because the grid below is the decision and it does not undo cleanly.
Gong: Admin center, Settings, CRM settings
Gong imports from Account, Contact and Opportunity, and a tech admin picks the fields per object including custom ones. The required set is fixed: company domain, name and last modified date; contact name, title, phone, email and associated company ID; deal name, stage, amount, close date, owner ID and account ID.
Gong: the Export tab
Meetings, Calls or Notes, and both streams must use the same type because a meeting invite is updated with the call details afterwards. Gong documents that exporting as meetings alongside a HubSpot and Google Calendar setup may duplicate them, and names calls or notes as the alternative.
Gong: the Export tab
All calls covers telephony calls imported into Gong plus Gong Dialer calls, and Gong says another application sending calls makes that option duplicate them. Gong Dialer calls only is the narrow setting. Emails have the same pair: All emails, or Gong composer emails only.
Gong: HubSpot activity update period
This is how many months after an activity Gong keeps updating the HubSpot record as new information arrives. Gong's own example: with three months set, a January activity is still updated in February and not in April. A long period keeps records fresher and consumes CRM resources doing it.
Gong: Enable update of opt out field in HubSpot
Prospects marked Do not contact in Gong Engage only reach HubSpot if you click Give permission and sign in again as the integration user. Gong states this is in addition to the regular integration permissions, so it is a second consent screen rather than a checkbox.
Gong: CRM export status report
It shows which activities exported, which failed and which were never set to export. With a six hour delay on the pipeline, this is the only way to tell a misconfiguration from a wait.
Step two is the one teams skip and the one that decides whether this install is remembered as a success. Everything else is reversible; the object type is not, because Gong leaves already-exported records as they are and recreates re-exported ones as the new type. The same ordering logic runs through the revenue intelligence layer, where every tool is writing to a timeline somebody else also writes to.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/hubspot-gong/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-gong.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyCalls are being exported as HubSpot meetings while HubSpot is also syncing Google Calendar. Gong documents this combination as producing duplicate meetings.
Export as calls or notes instead. Note that changing the type does not convert the records already there, so you will be cleaning up the first batch by hand.
WhyAll calls was selected while another application also exports calls to HubSpot. All calls covers telephony calls imported into Gong as well as Gong Dialer ones.
Switch to Gong Dialer calls only. This narrows what Gong claims rather than disabling the other tool, which is usually the easier conversation.
WhyNothing is wrong. Gong documents that exporting its data to HubSpot can take up to six hours.
Wait, then read the CRM export status report rather than the timeline. It distinguishes failed from not yet exported, which the record cannot.
WhyNo external participant matched a HubSpot record. Gong requires at least one match before it creates an activity from a meeting invite.
Check whether the attendee exists in HubSpot with that email. This is also why Gong distinguishes participants, who joined, from attendees, who joined and have a contact record.
WhyThe field type is unsupported or the format is wrong. Multiple checkboxes, file fields and HubSpot user fields are not imported at all, and date fields have to be epoch in milliseconds.
Check the type before the mapping. A long single-line text or dropdown value is a different case: those import and display only the first 120 characters.
WhyRich text has limited support. It displays without formatting, and an edit made in Gong writes back to HubSpot without it.
Keep rich text fields out of the imported set if anybody edits in Gong. The flattening is not recoverable from the HubSpot side.
WhyThe connecting HubSpot user was deactivated, which is what the dedicated integration user recommendation exists to prevent.
Reconnect with a service account rather than reactivating the person who left. Remember Gong sees exactly what that account sees, so check its permissions rather than assuming parity.
WhyThe opt-out permission is a separate authorisation, in addition to the regular integration permissions.
Click Give permission under Enable update of opt out field in HubSpot and sign in as the integration user again. Only relevant if you have Gong Engage, and a compliance problem rather than a cosmetic one if you do.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
Gong's HS Integration is awful because we also use Google Workspace, and Gong hates it if you use Google Calendar & HubSpot, so we have to push all our Gong stuff as Notes, not Meetings.
r/hubspot·December 2025·1 points
One point, and the most valuable comment in the set. Gong documents exactly this: exporting as meetings while HubSpot syncs Google Calendar may duplicate them, and calls or notes is the alternative. The quote is what the grid above looks like after somebody has lived in it, and the same team is planning to leave for HubSpot's own note taker.
If you're looking for conversational intelligence tools that integrate well with HubSpot, Gong and Chorus are top-tier options, but they can be expensive. For more affordable alternatives, consider tools like CallRail [...] Another option is Aircall
r/hubspot·November 2024·1 points
Representative of the whole thread rather than remarkable in itself. The accepted answer in that thread was Fathom, chosen over Fireflies after trying most of them, on the strength of the HubSpot integration working at the free level. Gong is quoted rather than listed, which this directory says on every page about it.
Not sure what hubs or levels you have, but HubSpot has its own CI in Sales/Service Enterprise. Also a good chunk of the AI note takers like Firefly and Fathom integrate pretty well
r/hubspot·November 2024·3 points
Corrected in the same thread by somebody saying it is available in Sales Professional, which is the kind of disagreement about a tier that this directory exists to settle from the vendor's own page rather than from a thread. What is not in dispute is that the comparison is in-product, which changes the case for buying this pair at all.
We tested it in October. It's in beta, so it's very buggy. But we are very excited to switch from Gong to HS Notetaker sometime in the several several months. We're just waiting for it to be bake a little longer.
r/hubspot·December 2025·1 points
The same comment as the first insight, read for a different thing. Two other replies in that thread rate the native note taker as awful and very bad, and a fourth calls it mid but adequate for dumping notes onto deal records. A tool in beta is not a reason to delay a decision, and it is a reason to check again before a renewal.
We've got the transcripts as we're on enterprise. What I'm looking to do is parse through all Call transcripts for specific insights, like identifying which services the prospect discussed with our sales team, what their availability is, etc... and then be able to store those as properties in the Contact or Call
r/hubspot·February 2025·1 points
A precise description of the gap this pair does not close. Gong exports the brief, the highlights, the outline and the action items as activity, and no transcript at all, so turning a conversation into a filterable property is a job for a workflow reading the Gong API rather than for the export settings.
The striking thing about searching this pair in the words a HubSpot customer would use is how rarely Gong is the answer. Threads asking which conversational intelligence tool works with HubSpot return Fathom, Fireflies, HubSpot's own feature and a long tail, with Gong named as the expensive option. The one comment in fourteen threads that describes running both in production is about a duplicate problem, and the fix it reports is the one Gong documents. Read the set as a statement about who buys this pair rather than about whether it works.
Only the first of those five describes the integration itself, and it corroborates a limit Gong documents, which is the standard this section is held to. The other four are about the decision rather than the mechanism, and they are worth reading before a renewal rather than before an install.
The most useful thing to settle before the install is which object type Gong writes, because it is the decision that both prevents duplicates and cannot be undone cleanly. HubSpot can receive meetings, calls or notes, and whatever is already writing to your timeline, a calendar sync, a dialler, an email tool, is competing for the same objects. Pick the type nothing else uses, confirm it against what your other integrations do, and only then switch it on. Changing it later leaves the old records as they were and recreates the new ones, which is how a timeline ends up with both.
The transcript limit is worth reading as a design decision rather than a gap. A CRM record is a place to see that a call happened, who was on it and what was agreed, not a place to read forty minutes of conversation. Gong exports the brief, the highlights, the outline and the action items, and links back for the rest. The practical consequence is that Gong stays the system of record for conversations and HubSpot stays the system of record for the deal, which is the correct split and the one the revenue intelligence layer assumes throughout.
What this pair costs is a Gong contract, which is quoted rather than listed, and the honest comparison is against the Salesforce version if you are choosing a CRM rather than an integration. The HubSpot side is lighter: no managed package, no permission-set licences, no sharing model to reason about. In exchange you get a HubSpot tech admin requirement and the same dedicated-integration-user advice, and the same six hour delay on everything.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, Gong and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Meeting invites and web conference calls as meetings, calls or notes, and you pick one type for both. Telephony calls land as call objects. Emails export as emails, and only from the date you switch it on rather than retroactively. Engage tasks and LinkedIn messages and connection requests export when the to-do is completed. Each call object carries the call name, participants, a link to the call in Gong, the spotlight brief, highlights and outline, the action items Gong identified, and metadata such as duration and call resolution.
No. Gong states plainly that the call transcript is not exported. You get the summary, the highlights, the action items and a link back to Gong, which is the right amount of information for a CRM record and means HubSpot is not where anybody reads a call. Treat the link as the integration's main deliverable rather than a convenience.
Gong documents that it can take up to six hours to export Gong data to HubSpot. That is a reporting fact rather than a defect: a dashboard built on today's activity is incomplete until the evening, and anybody checking whether the integration works ten minutes after a call will conclude it does not.
Because something else is already writing them. Gong lists three cases. Exporting calls as HubSpot meetings while Google Calendar also syncs them duplicates the meeting, and the fix is to export as calls or notes instead. Exporting all telephony calls when another application also sends calls duplicates those, and the fix is Gong Dialer calls only. Emails duplicate the same way when a second tool exports them.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.