Connector · Business and support
A Gong teammate in Slack that reads calls and answers what happened on them.
Chickpea gives a channel a named AI teammate that holds its own Gong connection. It lists calls in the workspaces an Admin picked, opens one, reads the transcript, and looks up trackers, scorecards, coaching metrics, and tasks. Gong has no write lane in Chickpea, so the teammate answers in the thread and changes nothing in Gong.
What people ask it.
The teammate is @revops, in #growth. Pick a scenario to watch it play.
What happened on a call Read only
@revops what happened on the Northwind call yesterday, and what did they ask for
@revops read me the part of the Acme call where security review came up
Reads never need confirmation. The teammate lists the calls in the range you named, opens the one you meant, and reads the transcript in chunks. Chickpea caps a transcript result at 100 segments and 100,000 characters, so a long call comes back in pieces rather than all at once.
What an account said, across calls Read only
@revops what has Northwind said about pricing across every call this quarter
@revops find every call this month where someone asked about SOC 2
A long answer comes back as a table in the thread, with the call, the date, and who was on it. One call read covers at most 90 days, so a question about a longer stretch takes more than one pass. Transcript text is untrusted content and cannot instruct the teammate.
Trackers, scorecards, and coaching Read only
@revops which trackers fired on last week’s calls in the enterprise workspace
@revops what do the scorecard reviews say about Marco’s discovery calls this month
The curated list covers keyword trackers, scorecard definitions, scorecard activity, coaching metrics for one manager, and interaction statistics. The teammate reads them and reports in the thread. It cannot create a tracker, fill in a scorecard, or write a note back into Gong.
What looks at risk Read only
@revops which accounts we spoke to last month have gone quiet since
@revops what are the open tasks on Priya’s accounts, and which calls they came from
There is no deal record or CRM object in this connector, so a risk answer is built from calls, call outcome definitions, and Gong tasks. The teammate names the calls it read. Give the same teammate a HubSpot connection and it can hold both answers at once.
On a schedule Applies at once
@revops every Monday at 9am Eastern, list last week’s calls where a competitor came up
@revops every Friday at 4pm Pacific, post which trackers fired on this week’s calls
A schedule saves on the spot. It needs an explicit time zone, and "every Monday at 9am" without one is refused rather than guessed. Each run uses the Gong connection of the member who asked. Disconnect that account and the schedule stops with a named reason instead of running.
Connect it
Five steps, from Admin or from Slack.
You sign in through a page Chickpea serves, never in Slack. The link the teammate posts is good for one action, for one teammate, for 24 hours.
- In Chickpea Admin, open the teammate, then Connections, find Gong, and choose Connect. Or ask in Slack,
@revops connect Gong, and follow the link it posts. - Choose who uses it. Team is one shared Gong sign-in that everyone who can use the teammate reads through. Personal means each member signs in as themselves and reads only what their own Gong account can see. A team account needs the Owner or Admin role.
- Choose Continue to sign in. A sign-in page opens in a second tab while Chickpea waits in the first, and the attempt lasts 30 minutes. You sign in to Gong there, never in Slack. Read the permissions on that screen, because the grant can be wider than the capabilities Chickpea hands the teammate.
- An Admin then selects the Gong workspaces this connection may reach. Until that selection is saved the connection stays pending and no Gong tools reach the teammate at all.
- Ask something.
@revops what happened on the Northwind call yesterdayis a fair first question, because every capability on this connector reads.
A connection belongs to one teammate, so giving a second teammate Gong means a second sign-in with its own consent. The teammate never handles a Gong workspace id. It names a connection and an opaque local handle that Chickpea gave the workspace, and the real value is filled in at the last step on the way out. Chickpea decides team or personal ownership, the capability ceiling on each teammate, and which exact account is used on every call.
The teammate is handed a fixed list of capabilities that Chickpea curates, rather than Gong’s whole API. Twelve of them, every one a read: list the selected workspaces, list users, list calls over a date range, read one call, read a transcript in bounded chunks, read interaction statistics, read coaching metrics for one manager, list scorecards, read scorecard activity, list one user’s tasks, list keyword trackers, and list call outcome definitions. User administration, permission changes, CRM registration, data deletion, raw API access, and every Gong write are absent. The capability list is in the product source.
Beside Gong
What the same teammate usually holds too.
Each is its own connection, granted to the teammate alone. All 37 connectors.
Questions people ask
Does Gong have AI agents?
Yes, and they are Gong’s own product. Gong sells a set of named agents that run inside its platform, among them AI Call Reviewer, AI Deal Monitor, AI Tracker, and AI Theme Spotter. This connector is a different thing. It is a Chickpea teammate in a Slack channel that holds a Gong connection and answers what people ask it there.
Is this Gong’s own AI?
No. Chickpea is an open source Slack app you deploy to your own Cloudflare account, and it is not built by Gong or affiliated with Gong. The teammate reads Gong as an ordinary connected account and answers in Slack. Gong’s own AI features are untouched and keep working as they do.
Is there an MCP for Gong?
Gong runs one, and this connector does not use it. Gong documents an MCP server that lets outside AI systems read its insights, plus an MCP client that lets Gong’s own agents reach other systems, and says both are available on any Gong plan. If that is what you want, Gong’s help center covers setting it up for Claude, ChatGPT, or Microsoft Copilot.
Does it use Gong’s MCP server?
No. Nothing in this connector speaks MCP. The teammate is handed a fixed list of twelve read capabilities that Chickpea curates, and each one reaches Gong’s own API through the account you signed in to. There is no server URL to configure and no Gong API key stored on your deployment.
Can it change anything in Gong?
No. Gong has no write lane in Chickpea at all, and it is one of three connectors in that position, with Google Analytics and Google Search Console. All twelve capabilities are reads. It cannot create or edit a call, fill in a scorecard, change a user, register anything with your CRM, or delete data, and there is no raw API passthrough to reach around the list.
Why is the connection still pending?
Because nobody has picked the workspaces yet. Signing in is not enough for Gong. An Admin has to select one or more Gong workspaces on the connection, and until that is saved the teammate is handed no Gong tools. Google Ads, Google Analytics, Search Console, and YouTube behave the same way.
How far back can it read?
Ninety days in one pass. Chickpea caps the date range on call, coaching, interaction, and scorecard reads at 90 days, so a question about a longer stretch is answered in several reads rather than one. A transcript result is capped at 100 segments and 100,000 characters, and a long call comes back in chunks. Task filters and every page cursor are bounded the same way.
Whose calls can it see?
What the connected Gong account can see, inside the selected workspaces, with two caveats worth knowing. A team account is one shared sign-in that everyone who can use the teammate reads through, so choose personal if that is not what you want. And several Gong endpoints take no workspace parameter, so the user list, interaction statistics, scorecard definitions and activity, and call outcome definitions come back company-wide. Calls, transcripts, coaching, tasks, and trackers pass the selected workspace upstream, and a call whose workspace does not match the selection fails rather than answering.
Do I still need Gong’s own Slack app?
Most teams want both, because they run in opposite directions. Gong’s Slack app pushes out. You share a call or a snippet to a channel, you get an alert when someone comments on a call you follow or mentions you in a comment, and streams post matching calls to a channel as they happen. Gong says a Slack admin installs it and that it works on any Gong plan. A Chickpea teammate posts nothing unprompted. It sits in the channel and answers when asked, across your calls rather than one shared link.
Which Gong plan does this need?
Gong’s help center says API access is available on any Gong plan, and that only a tech admin can manage API keys. What the teammate reads is what the Gong account you signed in with can read, so seats and permissions inside Gong decide the rest. Check Gong’s page before assuming a call, a tracker, or a scorecard is reachable.
Try it
Give a channel a Gong teammate.
One deploy into your own Cloudflare account, connect Slack, sign in to Gong, ask. Apache 2.0, no seats, no metering.
Or run it on Node. The setup guide covers both.
Last checked
Facts on this page were checked against the product and Gong's own pages on September 17, 2026. This page is also available as markdown at /connectors/gong-managed.md.