Channel alerts come from streams, and a stream has to be the standard kind.
A Gong contract, a Slack admin to install the app, and a Gong admin to connect it
Messages, Activities, events only.
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.
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 |
|---|---|---|
| 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 | Event only | Nothing. This is a notification surface, not a sync. The records live in Gong and in whichever CRM Gong is connected to. |
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.
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. |
Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.
| The action | How it reads on the record |
|---|---|
| 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 |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six action rows and three documented exclusions, each one's note, and the four 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 second table is the page in one screen. Three of the six rows end in a personal app and one ends in a channel, and the one that ends in a channel is the one that takes configuration. Anybody who sets up this integration expecting channel alerts and finds only direct messages has met that distinction rather than a fault.
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. Pick one on each side and the grid marks the answer.
Pick one on each side.
| 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 |
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 produces everywhere.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/slack-gong/SKILL.md https://www.reversecontact.com/integrations-hub/skills/slack-gong.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyIt 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.
WhyEither 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.
WhyThose 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.
WhyIf 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.
WhyA 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.
WhyIt 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.
WhyGong 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.
WhyThe 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.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
We use Gong and ProductBoard (for feature requests and customer feedback on product). There's a way for us to highlight the portion of the call in Gong, click a button, and send it immediately to ProductBoard for our dev team to see. It's awesome.
r/CustomerSuccess·March 2024·12 points
The highest-scoring comment in the set, and it describes the Share call pattern rather than the notification one: a person selects the moment and sends it somewhere. The Slack equivalent is the Share call tab, which needs no stream and no filters and is the half of this integration nobody writes about.
In meantime would use their "ask anything" functionality on the call to say "please write a summary with xyz parameters". For example you could ask it to summarize a JIRA ticket summary, a feature request, a project plan with steps, an internal email to xyz recipient etc
r/CustomerSuccess·March 2024·5 points
Relevant because the brief type on a stream is the same decision in miniature. Gong picks what summary appears in the notification, Highlights is the default, and a brief that is wrong for the channel is what makes a stream feel like noise rather than signal.
If you are over gong cost and complexity a few excellent alternatives come up consistently as Avoma, Meetgeek and Fireflies are all worth testing. If you want something more sales focused with strong Hubspot + Google Meetings integration Attention could be a game changer
r/SalesOperations·September 2025·5 points
From a thread titled Gong replacement, which is where most discussion of Gong lives. The Slack integration is free with the contract, so it never appears in these comparisons, and that is worth saying: nobody buys Gong for this and nobody leaves Gong over it.
The inability to disable threaded messages, or at least a toggle that forces them to post to the channel by default instead of requiring a user to check a box each time. Too many people miss too many threaded (hidden) messages.
r/Slack·May 2025·5 points
Not about Gong and directly relevant to every stream you point at a channel. The thing a stream produces is a message somebody has to notice, and Slack's own defaults hide replies. Choosing a quiet channel matters more than choosing the brief.
Paste transcript into chat gpt and ask it to pull out the action points
r/CustomerSuccess·March 2024·5 points
Short and worth including because of what it implies about expectations. The people asking for this integration are not asking for more messages; they are asking for fewer, carrying more. That is an argument for narrow stream filters rather than for turning everything on.
Almost nobody discusses this integration directly, so the search was for the job: getting what happens on a call in front of people who were not on it. The threads are about Gong's price and about turning transcripts into actions, and the most useful ones are from people who solved the second problem with something other than a notification. Read as a group they suggest the channel alert is the easy half and the hard half is deciding what deserves one.
Not one of the five describes this integration failing, which is what a job search returns for a pair nobody names. The failure mode the documentation and the threads agree on is volume, and volume is the only thing on this page that no setting fixes for you.
The design decision on this pair is the stream, and it is better than the alternative most teams expect. A notification rule would let you route any call event anywhere, which sounds flexible and produces a channel nobody reads. A stream forces you to answer a more useful question first: which calls belong in a collection, who curates it, and who is accountable for acting on what lands there. The channel alert is then a consequence of a decision somebody already made rather than a filter built in a hurry.
What travels is deliberately thin, and that is right. This is a notification surface, not a sync: no CRM records move, no call data is stored in Slack, and the only thing going the other way is a reply to a comment. Everything a reader needs is one click away in Gong. That keeps the integration out of the governance conversations that the CRM pairs need, and it means the only thing to get wrong is volume.
Volume is the thing to get right, and the rule is the same one every pairing on this hub reaches: route the events a named human must act on within minutes, and leave the rest in Gong where they are already organised. A channel firing forty times a day gets muted, and a muted channel is indistinguishable from a working one in every screen an admin can open. If you want the call evidence attached to the deal rather than announced, that is the CRM integration rather than this one.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Slack, Gong and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Two different things. Personal alerts reach a user's own Gong app in Slack when somebody comments on a call they follow, replies to their comment, or mentions them. Channel alerts come from streams: a stream collects relevant calls as they happen, and the stream can notify a Slack channel when a new call is added. People can also share a call to a channel by hand and reply to Gong comments without leaving Slack.
Almost always because the stream is not the standard type. Gong documents that Slack notifications require a stream set to Standard. The channel selector is simply absent otherwise, which reads like a missing permission and is a stream setting.
Two people. A Slack admin installs the Gong app in Slack, and then a Gong business or tech admin connects the workspace from Admin center, Settings, Ecosystem, Slack. After that, notifications can be switched on for all recorded users at once from the company-wide notifications settings, and individuals can still manage their own from their personal notifications page.
Yes, once Gong has been added to the channel. Anyone in the channel can do it by opening the channel and typing the command to add apps, then adding Gong. Until that happens the channel is selectable and nothing arrives, which is the most common silent failure on this pair.
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.