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

# Salesforce and Gong

> Generated from https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-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 Salesforce edition with API access, and a dedicated integration user

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

## The short version

Gong reads your CRM and writes call intelligence back onto the opportunity, which is the whole argument for it: the forecast conversation happens where the deal lives rather than in a second dashboard. The setup is a permissions exercise and almost nothing else, and it has one rule that no other integration in this directory shares. Remove a field from the integration user and Gong removes the data it had already imported for that field. That makes the permission set a live dependency rather than a one-off install step, and it is the single thing to document before anybody tidies up a profile.

## What each licence actually carries

Rows: Licences on the integration user. Columns: What you get. Gong prices by seat and quotes rather than publishes, so the useful grid is not editions. It is the two Salesforce permission set licences this integration needs, because each carries a different half and teams routinely assign one.

| Licences on the integration user | Importing Salesforce data to Gong | Creating tasks and events |
|---|---|---|
| Neither | Does not work | Does not work |
| Salesforce API Integration only | Does not work | Works |
| Both licences | Works | Works |

- **Does not work.** The permission the other licence carries is missing. Gong documents field-level permissions for importing Salesforce data and system permissions for creating tasks and events as coming from two different licences.
- **Works.** That half of the integration has what it needs. The grid has a working row and two broken ones, which is the point of drawing it.

Counted off that grid, of six pairings: three give you does not work, three give you works.

A half-licensed integration is the failure this grid exists to name: Gong keeps recording, calls keep logging, and the CRM context inside Gong quietly never arrives.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Accounts, contacts, leads and opportunities | One way, out | Read out of Salesforce into Gong, with the fields chosen by an admin. Required fields are documented per object and recommended ones improve deal boards and call filters. |
| Calls and meetings | One way, in | Written back into Salesforce as Tasks or Events. Either one task carrying every participant and association, or separate tasks on each matched contact, the account and the opportunity. |
| Recordings and transcripts | One way, in | Into the Gong Conversation object in Salesforce, which arrives with the Gong for Salesforce package rather than with the base integration. |
| Engage activity | One way, in | Engage tasks, LinkedIn connection requests and messages, and flow activity, where you run Engage and have an Engage licence. |
| Opportunity stages and amounts | One way, out | Read out of Salesforce for the deal board and the forecast. Whether a team member can edit a Salesforce field from inside Gong is a separate question from the integration user's permissions. |

## Which field lands where

Direction here is written from Salesforce's point of view: out means out of Salesforce into Gong. Most of what people describe out loud runs the other way from how it is configured.

| In Salesforce | In Gong | What to know about the match |
|---|---|---|
| Accounts, contacts, leads and opportunities | Gong, as context on a call | Out of Salesforce. This is the half that needs the Salesforce Integration licence and field-level permissions. |
| Calls, meetings, recordings and transcripts | Salesforce activity on the record | Into Salesforce, which is the half everybody means when they say Gong exports to the CRM. |
| Gong objects such as Conversations | Reportable Salesforce objects | Available to report on, which is what makes Gong data usable in a Salesforce dashboard rather than only in Gong. |
| A picklist or string value | Gong, trimmed at 120 characters | Gong displays a maximum of 120 characters for both, so longer values are cut rather than wrapped. |
| A field removed from the configuration | Deleted imported data | Not merely stopped. The data Gong imported through that field goes with it. |

**What does not cross:**

- Anything the integration user cannot see. Gong warns that overly limited permissions leave activities missing rather than erroring.
- The tail of a value longer than 120 characters, on display.
- Anything at all, once the integration user is deactivated. Gong treats that as the outage it is.

## Connect it, in this order

**Who has to do it:** A Salesforce administrator who can create a user and assign two permission set licences, and a Gong admin.
**How long:** An afternoon, most of it spent deciding which fields the integration user may see.

### 1. Enable API access in Salesforce first

*Where:* Salesforce Setup

Gong states it plainly: without API access enabled you cannot connect Gong to Salesforce at all. This is an edition question before it is a configuration one.

### 2. Create a dedicated integration user

*Where:* Salesforce: Users

Gong supports Salesforce's dedicated integration user licence and recommends one per integration. A named person's account means that when they are deactivated the integration stops, which is a bad way to find out who owned it.

### 3. Assign both licences, because they do different jobs

*Where:* Salesforce: permission set licences

The Salesforce API Integration licence carries the system permissions needed to create tasks and events. The Salesforce Integration licence carries the field-level permissions needed to import Salesforce data into Gong. One without the other produces an integration that half works, and the half that fails is silent.

### 4. Tick API Enabled on that profile or permission set

*Where:* System permissions

Gong uses it to check your API limits and keep its own requests underneath them. Without it Gong cannot see the ceiling it is supposed to respect.

### 5. Give record access deliberately, object by object

*Where:* The integration user's permission set

View All Records on an object overrides whatever the role hierarchy would have allowed. Gong is explicit that permissions which are too limited leave activities missing until somebody adjusts the setup, so this is the setting that decides completeness.

### 6. Choose the fields Gong imports, and leave them alone afterwards

*Where:* Gong: Salesforce field configuration

Removing a field from the configuration deletes the data Gong already imported through it. Adding fields is cheap; removing one is destructive, and the time to decide is now.

Two permission set licences for one integration is unusual enough to be worth repeating, and it is the thing most likely to be half done when somebody reports that calls are logging but opportunities are not.

## How to check it worked

- Check a call recorded today appears on the right opportunity, not just in Gong.
- Check a task or event created by Gong exists in Salesforce. That tests the API Integration licence specifically.
- Open a record the integration user should not see and confirm Gong has no activity for it, so you know the access boundary is where you think.
- Look at a long picklist value in Gong. Anything over 120 characters is trimmed on display, which matters if your stage names are sentences.

## 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 |
|---|---|---|
| Activities are missing and nothing errored | The integration user's permissions are too limited. Gong says exactly this: activities may be missing until the setup is adjusted. | Widen record access on the objects concerned, using View All Records where the role hierarchy is the constraint. |
| Calls log but Gong has no CRM context | The Salesforce Integration licence, which carries field-level permissions for importing Salesforce data, is not assigned. | Assign both permission set licences. The symptom points at Gong and the cause is a Salesforce licence. |
| Gong cannot create tasks or events | The other licence. The Salesforce API Integration licence carries the system permissions for that. | Same fix from the other direction, which is why the grid above lists them separately. |
| The whole integration stopped on a Monday | The integration user was deactivated, most often in a routine leavers process. | Use a dedicated integration user on the licence Salesforce provides for the purpose, and add it to whatever list protects service accounts from deactivation. |
| Historic Gong data disappeared from a field | That field was removed from the Gong field configuration, which deletes the data imported through it. | There is no undo in the configuration screen. Treat field removal as a data decision requiring the same care as a Salesforce field delete. |
| Long picklist values look truncated | Gong displays a maximum of 120 characters for picklists and strings. | Shorten the values, or accept the trim. This is display rather than storage, so the data is intact in Salesforce. |

## What breaks, from the vendors' own docs

- **Removing a field deletes its imported data.** Gong documents that if a field is removed from the integration user, Gong also removes that field's previously imported data. A routine permission tidy-up therefore destroys history rather than pausing collection, and nothing about the change in Salesforce suggests that is about to happen. Record which fields the integration user holds and why, and treat that permission set as production configuration.
- **Private calls are not simply hidden.** A call marked private in the calendar is never visible to Gong and never imported. A call marked private in Gong can still be exported if a tech admin has set that up, and the exported task carries the subject "Private call" with comments saying so, while the Conversation object replaces the brief, highlights and key points with a privacy notice and ticks the Is Private field. That is three different behaviours for one word, and the one that catches people is the middle one.
- **Two licences, not one.** The integration user's permission sets need both the Salesforce API Integration licence, which carries the system permissions required to create tasks and events, and the Salesforce Integration licence, which carries the field-level permissions required to import. Teams that assign one of the two get a connection that authenticates and then half works, which reads like a sync fault rather than a licensing one.
- **A deactivated user is an outage.** Gong recommends a dedicated integration user because deactivating a regular user disconnects the integration. The failure arrives whenever somebody leaves, which is to say long after the install, and by then nobody remembers whose credentials the integration was set up with. The multi-currency case has a similar shape: if you run multiple currencies, the integration user's personal currency has to match the corporate currency.

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

### Salesforce

- **Base:** `https://{instance}.my.salesforce.com/services/data/v60.0`
- **Auth:** OAuth 2.0 through a connected app. **API access is an edition feature**: editions without it cannot run any of this.

| Call | Request | What it does |
|---|---|---|
| `PATCH /sobjects/Contact/{id}` | `{ "RC_Title__c": "VP Sales" }` | Update a record. Custom fields carry the __c suffix. |
| `POST /composite/sobjects` | `{ "allOrNone": false, "records": [...] }` | Batch up to 200. `allOrNone: false` so one bad row does not roll back the batch. |
| `GET /query?q=SELECT+Id,Email+FROM+Contact+WHERE+Title=null` | - | SOQL for the filtered slice. |

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

- **Validation rules, required fields, duplicate rules and Apex triggers all apply to your writes.** A completed run is not a successful write. Read the per-record errors.
- **The daily API allocation is shared across the whole org**, set by edition and licence count. A row-by-row job competes with every other integration; the symptom of exhausting it is other people's integrations failing.
- Test in a sandbox with ten records before production. The rules you will hit were written years ago by somebody who has left.
- Installing anything usually needs Modify Metadata, Download AppExchange Packages and Customize Application. That is an admin on their own schedule.

Docs: https://developer.salesforce.com/docs/apis

## 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: Salesforce objects and fields the integration user needs access to: https://help.gong.io/docs/salesforce-fields-the-integration-user-needs-access-to
- Gong help centre: setup requirements: https://help.gong.io/docs/set-up-requirements
- Gong help centre: view Gong activities in Salesforce: https://help.gong.io/docs/view-gong-activities-in-salesforce
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-gong-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-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.*
