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

# Slack and Gong

> Generated from https://www.reversecontact.com/integrations-hub/slack-integrations/slack-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 Slack admin to install the app, and a Gong admin to connect it

**What moves:** messages, activities, events only.
**How it is built:** native, marketplace app. **Effort:** minutes.

## The short version

The cheapest useful thing you can do with a Gong contract, and the one most likely to be configured into noise. Personal alerts about comments and mentions need no thought and work well. Channel alerts are the part worth designing, because they come from streams rather than from a notification rule, which means the question is not "what should we be alerted about" but "which calls belong in a collection somebody is accountable for". A stream per team with a strict filter is the version that is still on in six months.

## Which channels Gong can reach, and what it needs first

Rows: The Slack channel. Columns: What Gong can do with it. There is no edition grid on this pair: Gong documents the Slack integration as available on any Gong plan, and the Slack app is free. What decides whether a channel hears anything is the channel itself, and the rule is not symmetrical.

| The Slack channel | Show it in the channel picker | Post a stream notification to it |
|---|---|---|
| Public, Gong is a member | Works | Works |
| Public, Gong is not a member | Works | Works |
| Private, Gong has been added | Works | Works |
| Private, Gong has not been added | Invisible to Gong | Invisible to Gong |

- **Works.** channels:read lists every public channel and chat:write.public posts to public channels Gong has not joined, so public channels need no preparation at all. A private channel works identically once the app has been invited to it.
- **Invisible to Gong.** groups:read only covers private channels Gong has been added to, so an uninvited private channel is not merely unpostable, it is absent from the picker. That is why the symptom is a missing channel rather than a failed message.

Counted off that grid, of eight pairings: six give you works, two give you invisible to Gong.

Three identical rows and one that fails is the shape worth remembering: the only configuration this integration needs on the Slack side is inviting the app to private channels. Everything else that goes wrong on this pair is a stream, not a permission.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Comment and mention alerts | One way, in | To a user's own Gong app in Slack when somebody comments on a followed call, replies to their comment, or mentions them. |
| New calls in a stream | One way, in | A stream collects calls as they happen and notifies a chosen channel. The stream has to be the Standard type for the channel selector to appear. |
| A shared call | One way, in | Posted to a channel by hand, which is how a specific moment reaches people who do not follow the stream. |
| Replies to comments | One way, out | Answer a Gong comment from inside Slack and it reaches Gong, which is the only thing that travels in this direction. |
| CRM records or call data | Events only | Nothing. This is a notification surface, not a sync. The records live in Gong and in whichever CRM Gong is connected to. |

## Which field lands where

Nothing syncs here. What there is instead is a set of Slack permissions Gong asks for and a routing rule about where each kind of notification is allowed to go, and the second one is what people get wrong.

| In Slack | In Gong | What to know about the match |
|---|---|---|
| channels:read | Display Slack channels | Basic name and ID of public channels, which is how the channel picker is populated. |
| chat:write | Post to channels Gong is a member of | The ordinary posting permission, and the one that covers private channels once Gong has been invited. |
| chat:write.public | Post to public channels Gong is not in | The asymmetry that explains the whole setup: a public channel needs no invitation and a private one does. |
| groups:read | Display private channels Gong has been added to | Only the ones it has been added to, which is why a private channel is missing from the picker until somebody invites the app. |
| groups:write | Nothing, at the moment | Gong says so outright: not used at the moment, reserved for a future where people name a private channel for Gong to post to. |
| im:history | Read direct messages | Used to carry comments made in Slack back into Gong on the call they belong to. The one piece of this integration that travels in the other direction. |
| users:read, users:read.email | View people | The pair of scopes behind matching a Slack person to a Gong user, which is what makes a mention resolve. |
| Call sharing | The Share call tab on the call page | Calls and call snippets go to public or private channels from Gong's own interface rather than from a notification rule. |

### Where each kind of Gong notification is allowed to go

| The action | How it reads on the record |
|---|---|
| Somebody comments on a call you follow | Your personal Gong app in Slack. Not a channel |
| Somebody replies to a comment you made | Your personal Gong app in Slack. Not a channel |
| Somebody mentions you in a comment | Your personal Gong app in Slack. Not a channel |
| New calls matching a set of filters | A Slack channel, and only through a stream set to Standard |
| A call or a snippet you want to show people | Any channel, shared by hand from the Share call tab |
| A comment made in Slack | Back into Gong on the call, which is what im:history is for |

**What does not cross:**

- A channel version of the three personal notifications. Following a call, replying to a comment and being mentioned are all personal events, and no setting routes them to a channel.
- A private channel Gong has not been added to. It will not appear in the picker, because groups:read only covers channels the app is in.
- Calls matching an inactive AI tracker, or any tracker at all when the company is short of credits. Gong documents those as not collected.

## Connect it, in this order

**Who has to do it:** A Slack admin to install the app, then a Gong tech or business admin to connect it. Gong names both roles, and they are rarely the same person.
**How long:** Ten minutes for the connection. The streams are the real work and they are never finished.

### 1. Have a Slack admin install the Gong app first

*Where:* Slack

Gong states the order plainly: a Slack admin must install the Gong app in Slack, and then both business and tech admins can connect Slack to a Gong workspace. A Gong admin alone cannot complete this.

### 2. Connect from Gong, not from Slack

*Where:* Gong: Admin center, Settings, Ecosystem, Slack

Click CONNECT, choose the Slack workspace, sign in, then Allow to give Gong access to Slack. You are returned to the Slack integration settings page, which is where the connection lives afterwards.

### 3. Decide the company-wide notification question at the prompt

*Where:* Gong: the Turn on Slack notifications message

Immediately after connecting, Gong offers to turn notifications on for all recorded users. Saying yes is a decision about everybody's Slack, so it is worth knowing it is coming rather than clicking through it.

### 4. Understand what the personal notifications cover

*Where:* Gong: Notifications settings

Three events reach a user's personal Gong app in Slack: somebody comments on a call they follow, somebody replies to a comment they made, and somebody mentions them in a comment. None of those can go to a channel.

### 5. Build a stream for anything a channel should hear

*Where:* Gong: Conversations, Your library or Company library

Channel notifications are a stream feature. Click + New, then Stream, name it, and choose whether it lives in Your library, private to you, or Company library, visible to everyone. At least one filter is required.

### 6. Add Gong to the channel if it is private

*Where:* Slack: the private channel

Gong's scopes explain why: chat:write.public lets it post to public channels it is not a member of, while groups:read only shows private channels Gong has been added to. A private channel without the app is invisible in the picker.

### 7. Set the stream type to Standard

*Where:* Gong: the stream form, step 5

Gong notes that Slack notifications require the company to be connected to Slack and the stream type to be Standard. A stream of any other type will not offer the Slack channel.

### 8. Check the tracker behind the filter is alive

*Where:* Gong: the stream filters

If you filter on an AI tracker that is inactive, or your company has insufficient credits, Gong documents that matching calls will not be collected. The stream looks configured and quietly gathers nothing.

The split that matters is in steps four and five: three personal notification types that cannot reach a channel, and one channel route that is a stream. Teams that miss it conclude the integration is broken when it is doing exactly what Gong documents, which is the same misreading the [revenue intelligence layer](layer:intel) produces everywhere.

## How to check it worked

- Comment on a call somebody else follows and confirm it reaches their personal Gong app in Slack. That is the half that needs no configuration.
- Create a stream with one broad filter, point it at a test channel, and watch what arrives for a day. Volume is the failure mode on this pair and a day of real traffic is the only honest measurement of it.
- Point a stream at a private channel before adding Gong to it. The channel should not appear in the picker, which tells you the scope model is working rather than the integration failing.
- If a stream filters on an AI tracker, confirm the tracker is active and the credits are there. A stream collecting nothing looks identical to a stream nobody is posting to.

## 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 |
|---|---|---|
| A channel is missing from the Slack channel picker | It is a private channel and Gong has not been added to it. groups:read only shows private channels the app is in. | Invite the Gong app to that channel in Slack. Public channels never need this, which is why the problem only ever appears on private ones. |
| The Slack channel option is not offered on a stream | Either the company is not connected to Slack, or the stream type is not Standard. Gong requires both. | Check the connection in Admin center, Settings, Ecosystem, Slack, then set the stream type to Standard in step 5 of the stream form. |
| Notifications arrive as direct messages and never in a channel | Those three notification types are personal by design: a comment on a followed call, a reply to your comment, and a mention. Channel alerting is a stream feature. | Build a stream with filters and point it at the channel. There is no setting that redirects a personal notification. |
| A stream is collecting nothing | If the filter uses an AI tracker that is inactive, or the company has insufficient credits, Gong documents that matching calls are not collected. | Check the tracker is active and the credits are available. A filter on participants or account name is a useful control test because it depends on neither. |
| The channel is unusable because of the volume | A stream needs at least one filter and a broad one matches most calls. This is the failure mode on this pair and it is a configuration decision rather than a defect. | Narrow the filters and choose the brief type deliberately. Highlights is the default and works for most teams; a noisier brief in a busy channel is what gets the integration muted. |
| A stream nobody else can see | It was saved to Your library, which is private, rather than Company library. | Choose the library location when creating the stream. It is a field on the same form and easy to leave at its default. |
| The connection stopped working after an app update | Gong updates the Gong for Slack app from time to time and the new version needs re-authorising. | Click Authorize when prompted. Gong notes this on the connection article, and it is a permissions prompt rather than a reinstall. |
| A Gong admin cannot complete the setup | The Slack half has to come first. A Slack admin installs the Gong app, and only then can business and tech admins connect it from Gong. | Get the Slack install done as a separate task. Two admins on two teams is the real cost of this ten-minute integration. |

## What breaks, from the vendors' own docs

- **Channel alerts are a stream feature, not a notification setting.** Slack notifications on a channel are configured inside a stream, at the step where you set up notifications, and the stream must be set to Standard or the Slack channel selector does not appear at all. Teams looking for a notifications screen that routes call events to channels do not find one, because the routing is the stream.
- **A private channel needs Gong invited first.** Gong has to be added to a private channel before anything arrives. Anyone in the channel can do it, and until somebody does the channel can be selected and stays silent. That combination, a valid configuration with no output, is the hardest failure to attribute on this pair.
- **Two admins, on two different teams.** A Slack admin installs the Gong app and a Gong business or tech admin connects the workspace. In most companies those are different people, so the setup is a scheduling problem rather than a technical one, and it is worth starting the conversation before anybody promises a date.
- **Volume is the only real failure mode.** Everything here works. The integration fails when a stream is defined loosely enough that the channel fires dozens of times a day, the team mutes it, and the alerting looks healthy in every admin screen while nobody reads it. A muted channel is worse than no integration, because everyone still believes it works.

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

### Slack

- **Base:** `https://slack.com/api`
- **Auth:** `Authorization: Bearer xoxb-...` (bot token). Scope `chat:write`, plus `chat:write.public` to post to a channel the bot has not joined.

| Call | Request | What it does |
|---|---|---|
| `POST /api/chat.postMessage` | `{ "channel": "C0123", "text": "...", "blocks": [...] }` | The only call most of these workflows need. Use this when you need to choose the channel at runtime. |

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

- **HubSpot's Slack workflow action cannot route to the channel associated with the record.** It sends to a channel chosen at design time. If you need per-record routing, look the association up yourself and call `chat.postMessage` directly.
- Creating a Slack channel from a HubSpot workflow requires HubSpot Professional or Enterprise.
- Route only events a named human must act on within minutes. A channel that fires forty times a day gets muted, and a muted channel is indistinguishable from a working one in the admin screen.

Docs: https://api.slack.com/methods/chat.postMessage

## 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: about the Slack integration: https://help.gong.io/docs/about-the-slack-integration
- Gong help centre: connect to Slack: https://help.gong.io/docs/connect-to-slack
- Gong help centre: Slack scopes used by Gong: https://help.gong.io/docs/slack-scopes-used-by-gong
- Gong help centre: create a stream: https://help.gong.io/docs/create-a-stream
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-gong-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-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.*
