---
title: "Salesforce and Gong integration: what syncs, and what it needs"
description: "Salesforce and Gong: what moves, in which direction, which plan carries it, and the limits that bite. Verified October 2026."
url: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-gong-integration
format: markdown twin of the page above, generated at build time
---

New Unlimited plans are here. Fetch, search and enrich without counting credits. [See plans →](https://www.reversecontact.com/integrations-hub//pricing#plans)

Reverse Contact

### Products

Data

People Data

Company Data

Our Data Quality Standard

Delivery methods

API

Webhooks

CSV Enrichment

MCP

CLI

Integrations

### Use cases

[Sales Product](https://www.reversecontact.com/integrations-hub//use-case/sales-products)[Recruiting Product](https://www.reversecontact.com/integrations-hub//use-case/recruiting-products)[Internal Data Teams](https://www.reversecontact.com/integrations-hub//use-case/internal-data-teams)[AI Products](https://www.reversecontact.com/integrations-hub//use-case/data-for-ai)[CRM Enrichment](https://www.reversecontact.com/integrations-hub//use-case/crm-enrichment)

### Features

[Email Finder API](https://www.reversecontact.com/integrations-hub//feature/email-finder-api)[Phone Number Enrichment](https://www.reversecontact.com/integrations-hub//feature/phone-number-enrichment)[People Search API](https://www.reversecontact.com/integrations-hub//feature/people-search-api)[Agentic Search API](https://www.reversecontact.com/integrations-hub//feature/agentic-search-api)[People Lookalike API](https://www.reversecontact.com/integrations-hub//feature/people-lookalike-api)[Company Search API](https://www.reversecontact.com/integrations-hub//feature/company-search-api)[Person Enrichment API](https://www.reversecontact.com/integrations-hub//feature/person-enrichment-api)[Company Enrichment API](https://www.reversecontact.com/integrations-hub//feature/company-enrichment-api)[Person Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-person-api)[Company Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-company-api)

Security

Pricing

Docs

[Log in](https://app.reversecontact.com/auth/login) [Book a demo](https://www.reversecontact.com/contact?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header) [Start for free](https://app.reversecontact.com/auth/signup?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header)

# Salesforce and Gong

Take a field off the integration user and Gong deletes what it already imported.

Checked by **Reverse Contact** · Verified 2026-10-11 · No paid placement

## 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, two-way sync.

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

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

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.

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

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.

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

Every row above travels as a file: five field mappings 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 destructive one is worth reading twice: field configuration here is not a view setting, and removing a field is a deletion.

## What each licence actually carries

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. Pick one on each side and the grid marks the answer.

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

## How to connect Salesforce to Gong

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.

- **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 it takes** — An afternoon, most of it spent deciding which fields the integration user may see.

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.

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.

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.

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.

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.

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.

Hand it to an agent instead

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](https://www.reversecontact.com/integrations-hub/skills/salesforce-gong.md) and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/salesforce-gong/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-gong.md

## What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

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

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.

## The 6 failures people actually hit

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.

### Activities are missing and nothing errored

WhyThe 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

WhyThe 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

WhyThe 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

WhyThe 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

WhyThat 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

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

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](https://www.reversecontact.com/integrations-hub/errors) is often the same cause, so the directory indexes all of them by the message rather than by the integration.

## When this is the right integration

### Set it up when

- The forecast conversation needs call evidence on the opportunity
- Reps dial through Gong and none of it reaches the activity timeline
- Somebody is asking which deals have gone quiet, with proof

### Do not bother when

- There is no appetite for a dedicated Salesforce integration user
- Task and Event visibility in your org is Private and unchangeable
- You want Gong to be the system of record for anything

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.

## What practitioners say about it

Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2020 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.

### The common complaint is under-use, not malfunction

> Gong is alright, but we are not using it anywhere near its capabilities. The cost is too much for our liking, and no one has the bandwidth on our team to manage it.

[r/SalesOperations](https://www.reddit.com/r/SalesOperations/comments/1iruhko/gong_replacement/) · February 2025 · 5 points

Worth reading before a renewal rather than after one. The integration configuration above is where most of the unrealised capability lives: CRM context inside Gong and Gong objects reportable in Salesforce both need somebody to have finished the setup.

### Gong objects are reportable in Salesforce, and few people know

> Yes I have used gong. You can access the other gong objects like Conversations. Just depends on what kinds of KPIs you want.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/10kf8ku/sfdc_gong_integration/) · January 2023 · 3 points

This is the answer to the previous quote. If the team is not getting value, the gap is usually that nobody has built a Salesforce report on the Gong objects, which is where the conversation data stops being a recording archive and starts being a metric.

### There is an economic reason some integrations are deep and others are not

> We are exploring the ISV partner route for a new Salesforce-native app and trying to get clarity on how the revenue

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1ovwwj0/do_big_players_like_gong_or_zoominfo_really_pay/) · November 2025 · 18 points

Useful context for reading any integration in this directory. Building a Salesforce-native app carries a revenue share and a floor fee, which is why some vendors ship a managed package with permission set licences and others ship a Zapier connector and call it an integration.

### Integration quality varies wildly within a category

> Aircall is great. Avoid Five9, RingCentral, and TalkDesk. All have pretty poorly thought out salesforce integrations/support teams

[r/salesforce](https://www.reddit.com/r/salesforce/comments/j5sri9/which_telephony_system_would_you_recommend_to/) · October 2020 · 7 points

Said about telephony rather than about Gong, and the general point holds: in a category where everyone claims a Salesforce integration, the depth varies from a managed package with its own permission model to a webhook. Gong is at the deep end, which is why its setup has two licences in it.

### When three tools touch the same record, somebody should ask why

> why the vendor spread? Sounds like there are too many cooks, so my first instinct is to simplify the stack

[r/CustomerSuccess](https://www.reddit.com/r/CustomerSuccess/comments/1ow9zck/gong_salesforce_custify/) · November 2025 · 3 points

Fair, and this pair is usually not the one to cut. Gong writes activity nobody else produces, and the integration user's permissions are the right lever for narrowing what it touches without removing it.

What the threads add up to

Almost nobody posts about configuring this integration, which fits a native package that works. What people post about is whether Gong is worth what it costs, and the answer that recurs is not about the product: teams buy it, use a fraction of it, and have nobody with the bandwidth to own it. There is also a useful thread about why vendors build deep Salesforce integrations at all.

The threads point at the same conclusion from two directions: this integration is not where Gong deployments fail, and the configuration above is where most of the value people say they are missing actually sits.

## The longer answer

This pair is unusual in the directory for being almost entirely a permissions project. There is no tier to buy on the Salesforce side beyond an edition with API access, no field mapping exercise in the ZoomInfo sense, and no polling schedule to tune. What there is instead is a list of objects, fields and system permissions that has to be exactly right, and a set of consequences for getting it wrong that look like sync failures. Gong says this plainly: connecting with read and write access does not guarantee that entities will be imported and exported.

The rule about removing a field deserves to be read twice, because it inverts the usual mental model. In most integrations, taking away a permission stops new data arriving and leaves what you already have; here, Gong removes the previously imported data for that field. So the ordinary hygiene task of trimming an over-permissioned profile is a destructive operation on your call history, performed by somebody who thinks they are reducing risk. The mitigation is documentation rather than configuration: write down what the integration user holds, and why, where the next admin will find it.

The visibility questions are worth settling in the same session, because they produce the most convincing false negative on this page. Activities that never appear look exactly like an export that is not working, and the cause is usually that Tasks and Events are Controlled by Parent without Edit or Modify All on the parent objects, or Private without the integration user sitting at the top of the role hierarchy. Check the sharing model before you open a support ticket. The same discipline applies to the [Outreach pairing](https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-outreach-integration) and to every other tool writing activity into this org, which is the argument for deciding it once at the [CRM layer](https://www.reversecontact.com/integrations-hub/stack/crm) rather than per vendor.

## If this is not the one

The integrations people compare this against, or set up alongside it.

Split a stack into layers and this pair sits on two of them: the [CRM layer](https://www.reversecontact.com/integrations-hub/stack/crm), which 33 of the 68 integrations here touch, and the [revenue intelligence layer](https://www.reversecontact.com/integrations-hub/stack/revenue-intelligence), which 4 do.

[**HubSpot and Salesforce**Two CRMs, one connector, and an edition requirement on both sides. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-salesforce-integration)[**HubSpot and Gong**Six hours before a call appears, and the transcript never does. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-gong-integration)[**Salesforce and LinkedIn**The original CRM Sync target, with the same Advanced Plus gate. Two-way sync](https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-linkedin-integration)

## [Reverse Contact](https://www.reversecontact.com)

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. [What has changed since](https://www.reversecontact.com/integrations-hub/changes) · [How we checked](https://www.reversecontact.com/integrations-hub/methodology), and what we will not claim

[Eugene Suslov](https://www.linkedin.com/in/eysuslov/)

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

- **Verified** — 2026-10-11
- **Sources** — 3 vendor documents
- **Paid placement** — None

### Read from

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

## Salesforce and Gong, asked and answered

### What does Gong write into Salesforce?

Activities, as Tasks or Events depending on how your tech admin configured it, covering meeting invites, conference calls, telephony calls including those placed through Gong Engage, emails sent from the Gong composer, Engage tasks and Engage LinkedIn connection requests and messages. With the Gong for Salesforce package installed, completed calls also land in a Gong Conversation object holding the recording, the metadata and the transcript. You choose between one task per activity carrying every participant, or separate tasks on each matched contact, the account and the opportunity.

### What permissions does the Gong integration user need?

Read access on Account, Account Team, Contact, Lead, Opportunity, Opportunity Contact Role, Opportunity History, Opportunity Split, Opportunity Team Member, Record Type and User, plus API Enabled so Gong can monitor your API limits. Writing activities additionally needs write access to Task and Event with Access Activities, Edit Tasks, Edit Events and View All Users. The permission sets have to carry both the Salesforce API Integration licence, which provides the system permissions, and the Salesforce Integration licence, which provides field-level permissions.

### Do I need a dedicated Salesforce user for Gong?

Gong recommends one, and the reason is blunt: a regular user who is deactivated takes the integration down with them. Deactivating a departing employee is routine and nobody checks whether an integration was authenticated as them, so this is the kind of outage that happens months later and takes a day to diagnose. Create the integration user before the install rather than migrating to one afterwards.

### Why are activities missing from some records?

Usually visibility rather than the sync. If the default internal access on Tasks and Events is Controlled by Parent, the integration user needs Edit or Modify All on Account, Contact, Lead and Opportunity. If it is Private, the integration user has to sit at the top of the role hierarchy to see those records at all. Gong warns that overly limited permissions mean activities go missing until the setup is adjusted, and that connecting with read and write access is not by itself a guarantee that anything will be imported or exported.

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.

Ask an assistant
