---
title: "Gong AI agent in Slack: ask what happened on your calls | Chickpea"
description: "Give a Slack channel an AI teammate connected to Gong. Ask what a call decided or what an account said across a quarter of calls. Read only, open source."
canonical: https://chickpea.co/connectors/gong-managed
keyword: "Gong AI agent in Slack"
verified: 2026-09-17
---

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

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/gong-managed; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**Gong** (Gong.io, Inc., https://www.gong.io): Analyze calls, transcripts, coaching, tasks, and trackers in selected workspaces. Category: Business and support. Lane: Hosted sign-in. Sign in: OAuth, managed.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @revops, published to #growth.

### What happened on a call
- @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
- @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
- @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
- @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
- @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.

### Example conversations

**What happened on the call**
> **Sofia:** @revops what happened on the Northwind call yesterday, and what did they ask for?
> **@revops:** Northwind renewal, Tue Sep 16, 2:00 PM, 48 minutes, five people. They asked for annual billing at a discount and named a competitor’s quote twice. Priya said legal reviews the new terms before anyone signs.
> **@revops:** I read the call detail and 62 transcript segments. I cannot change anything in Gong, so this is the read and nothing else.

**What did they say about pricing**
> **Marco:** @revops what has Northwind said about pricing across every call this quarter?
> **@revops:** Four calls mention price. They started at a flat discount ask and moved to annual prepay once Priya put terms in front of them.
>
> | Call | Date | Who raised it | What they asked for |
> |---|---|---|---|
> | Northwind discovery | Jul 30 | Northwind | Any discount, no structure named |
> | Northwind technical | Aug 21 | Marco | 10% for annual prepay |
> | Northwind renewal | Sep 9 | Northwind | 15%, matched to a competitor quote |
> | Northwind QBR | Sep 16 | Priya | 12% annual, legal to review terms |
> **@revops:** One call read covers at most 90 days, so this quarter took two passes.

**Which trackers fired**
> **Dana:** @revops which trackers fired on last week’s calls, and where are we losing them?
> **@revops:** Nine trackers fired across 23 calls. Two are worth your morning.
> **@revops:** There is no deal record in this connection, so that is calls, outcomes, and tasks rather than pipeline.

**Every Monday**
> **Priya:** @revops every Monday at 9am Eastern, list last week’s calls where a competitor came up.
> **@revops:** Saved. Every Monday at 9:00 AM Eastern I’ll read last week’s calls in the selected Gong workspaces and post the ones where a competitor tracker fired, here in #growth. First run is Mon Sep 21.
> **@revops:** It runs on your Gong connection. Disconnect that account and it stops with a reason rather than running on someone else’s.

## Connect Gong
1. 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.
2. 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.
3. 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.
4. 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.
5. Ask something. `@revops what happened on the Northwind call yesterday` is 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.

## What the teammate is handed with Gong
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: https://github.com/pejmanjohn/chickpea/blob/main/src/connections/catalog/gong.ts

## Beside Gong
- **HubSpot:** What the customer said on the call, beside what the deal record claims
- **Granola:** Gong for the customer calls, Granola for the internal ones
- **Fireflies:** Two recorders and one teammate, when half the team sits on each
- **Gmail:** The call and the thread that followed it, read in one ask
- All 37 connectors: https://chickpea.co/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.

## Sources
- [Chickpea docs: connector catalog, the managed lane and the pending-selection table](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: managed connectors, the sign-in and the workspace selection](https://docs.chickpea.co/agents/managed-connectors/)
- [Chickpea docs: connections, team and personal accounts, the binding as a ceiling](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation, including the managed-capability effect gate](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service, and the authorization link posted in Slack](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules, time zones and what each run rechecks](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the Gong capability list, its read lane and its bounds](https://github.com/pejmanjohn/chickpea/blob/main/src/connections/catalog/gong.ts)
- [Chickpea source: the Gong preset (managed toolkit, provider, category)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Gong: the AI agents Gong sells for revenue teams](https://www.gong.io/platform/ai-agents-for-revenue-teams)
- [Gong help: about Gong MCP, the server, the client, and the plans](https://help.gong.io/docs/about-gong-mcp)
- [Gong help: about the Slack integration, sharing, alerts, and streams](https://help.gong.io/docs/about-the-slack-integration)
- [Gong help: manage API keys, available on any Gong plan, tech admin only](https://help.gong.io/docs/receive-access-to-the-api)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Airtable MCP in Slack](https://chickpea.co/connectors/airtable.md)
- [Asana AI agent in Slack](https://chickpea.co/connectors/asana.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gamma MCP in Slack](https://chickpea.co/connectors/gamma.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [Granola MCP in Slack](https://chickpea.co/connectors/granola.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [Linear MCP in Slack](https://chickpea.co/connectors/linear.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [PostHog MCP in Slack](https://chickpea.co/connectors/posthog.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co