---
name: hubspot-gong-integration
description: Connect HubSpot and Gong: what syncs, which editions carry it, the setup order, and the failures to expect. Covers activities, deals, contacts, companies. Use when the user wants to set up, audit or troubleshoot HubSpot and Gong together, or asks why data is not moving between them.
---

# HubSpot and Gong

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-gong-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A Gong contract, a HubSpot tech admin, and a dedicated integration user

**What moves:** activities, deals, contacts, companies, both ways.
**How it is built:** native, marketplace app. **Effort:** hours.

## The short version

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.

## Which export settings duplicate what you already have

Rows: The Gong export stream. Columns: Is something else already logging this in HubSpot?. 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.

| 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 |

- **the wide setting is safe.** Nothing else is writing that activity type, so All calls, All emails and exporting as meetings are all fine. Engage activity is in this row twice, because tasks and LinkedIn messages completed in Gong Engage have no second source by definition.
- **narrow it or get duplicates.** Gong names the narrow setting in each case. For meetings it is exporting as calls or notes rather than meetings, which is the documented answer when HubSpot is also syncing Google Calendar. For telephony it is Gong Dialer calls only. For email it is Gong composer emails only.

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.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| 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 | Events only | Never. Gong documents that the call transcript is not exported, so the link back to Gong is the only route to it. |

## Which field lands where

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. |

### What Gong writes back, and the condition on each

| 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 |

**What does not cross:**

- The transcript. Gong states it is not exported, so the Gong link on the record is the only route to the conversation and HubSpot is not where anybody reads a call.
- Seven kinds of calendar email. Anything tagged MEETING_ACCEPTED, MEETING_DECLINED, MEETING_TENTATIVE, MEETING_INVITATION, MEETING_INVITATION_CANCEL, MEETING_NEEDS_ACTION or SCHEDULING is excluded.
- History, in most cases. If the email or telephony integration was connected before the CRM one, those calls and emails count as existing activities and are not exported unless they fall inside the update period and change.

## Connect it, in this order

**Who has to do it:** A Gong tech admin, and somebody in HubSpot who can create the integration user and sign in as it. Gong names the tech admin role explicitly for every step.
**How long:** An afternoon of settings, then up to six hours before you can tell whether it worked.

### 1. Create a dedicated HubSpot integration user first

*Where:* 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.

### 2. Audit what already writes activity to HubSpot

*Where:* 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.

### 3. Connect HubSpot and choose which fields Gong imports

*Where:* 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.

### 4. Pick one object type for meetings and conference calls

*Where:* 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.

### 5. Narrow the telephony and email exports if anything else sends them

*Where:* 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.

### 6. Set the activity update period deliberately

*Where:* 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.

### 7. Grant the opt-out permission separately if you run Engage

*Where:* 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.

### 8. Read the export status report rather than the timeline

*Where:* 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](layer:intel), where every tool is writing to a timeline somebody else also writes to.

## How to check it worked

- Wait six hours before concluding anything. Gong documents up to six hours to export, and the most common false alarm on this pair is somebody checking ten minutes after a call.
- Take a call with one external participant who is not in HubSpot and confirm nothing is created. Gong needs at least one external participant matching a HubSpot record before it will create an activity from a meeting invite.
- Open one exported call object and check what is on it: the call name, participants, the Gong link, the spotlight brief, highlights and outline, the action items and the metadata. If you expected the transcript, it is not coming.
- Generate the CRM export status report after the first full day and read the failures. A failure there is a permission on the integration user far more often than it is a Gong problem.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| Every meeting appears twice in HubSpot | Calls 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. |
| Telephony calls appear twice | All 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. |
| A call happened and nothing is on the record after an hour | Nothing 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. |
| A meeting created no HubSpot activity at all | No 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. |
| One imported field is permanently empty in Gong | The 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. |
| A rich text field lost its formatting after somebody edited it in Gong | Rich 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. |
| The integration stopped working and nobody changed anything | The 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. |
| Do not contact in Gong Engage never reaches the HubSpot contact | The 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. |

## What breaks, from the vendors' own docs

- **Up to six hours before anything appears.** Gong documents that exporting its data to HubSpot can take up to six hours. Any dashboard built on today's activity is therefore incomplete all day, and the usual first report that the integration is broken comes from somebody who checked a few minutes after a call. Say the number out loud when you launch it.
- **Duplicates are the default if anything else writes activity.** Exporting as HubSpot meetings while Google Calendar also syncs them creates duplicates; export as calls or notes instead. Exporting all telephony calls when another application also sends them duplicates those; choose Gong Dialer calls only. Emails behave the same way. Changing the object type later does not convert what is already there, and re-exporting recreates records as the new type.
- **Some HubSpot field types will not come across.** Multiple checkboxes, file fields and HubSpot user fields are unsupported. Rich text arrives without formatting and edits made in Gong save back without it. Single-line text and dropdown fields display a maximum of 120 characters, so longer picklist options are trimmed. Date fields have to be epoch in milliseconds.
- **A deactivated user is an outage.** Gong recommends a dedicated integration user because deactivating a regular one disconnects the integration, and Gong can only access the HubSpot data that the connecting user can access. Both facts argue for a service account created before the install rather than migrated to afterwards, and for writing down what it can see.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Gong help centre: export data to HubSpot: https://help.gong.io/docs/export-data-to-hubspot
- Gong help centre: required HubSpot fields that Gong accesses: https://help.gong.io/docs/required-hubspot-fields-that-gong-accesses
- Gong help centre: about the HubSpot integration: https://help.gong.io/docs/the-benefits-of-integrating-hubspot-and-gong
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-gong-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-gong-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
