Gong: what this connector can do

Member·5 minutes to read

What this page is for

The setup guide is for whoever runs your organisation's Botseon deployment: how Gong's key, its base URL and the connect check work. This page is the other half: what Gong actually lets a bot do once it is connected to your account, what it asks you for along the way, its limits, and how to take the connection away again, in Botseon and at Gong.

List and read recorded calls, their transcripts and the people in the account.

Connecting your Gong account

Gong connects with a key, not a sign-in window. Only someone with Gong's Tech admin role can create one, so ask yours if you do not see Gong's API page.

In Gong, open Admin center → Settings → Ecosystem → API and create a key. Copy the Access Key and the Access Key Secret — Gong shows the secret only once. Note the base URL shown on the same page.
In Botseon, open Plugins, add Gong, and open its card.
Under its settings, fill in Gong API base URL with the base URL from step 1, with or without https://.
Under Accounts, paste the key as <access key>:<access key secret> — the two values joined by a colon — tick the four permissions and press Connect.

Botseon asks Gong for one page of your company's users with that key, on that address, and keeps the key only if Gong accepts it. If it says the Gong API base URL is required, the field is empty or is not a gong.io address. If it says the provider refused the key, check that you copied both halves, and that the key's Trusted IPs in Gong (if any) include your deployment's address. I updated the key (shown beside a tool marked as needing a permission) asks Gong the same question again after you change the key at Gong.

What a bot can do with it

Read — Gong tells a bot things, nothing changes

Tool	What it does
`gong.list_calls`	List recorded calls in a date range.
`gong.get_call`	Read one call and its details.
`gong.get_call_transcript`	Read a call’s transcript.
`gong.list_users`	List the people in the account.

Write

This connector has no write tools yet. A bot can only read through it.

The permissions it asks for, in plain words

Every call a bot makes through this connector is tagged with what kind of thing it is. Only the tags below ever apply here — a tag this connector's tools never carry is not listed, because it can never ask you for it.

read — Looks something up. Nothing changes, and nothing is sent anywhere. A bot never has to ask first for this.

Limits

List and read recorded calls, their transcripts and the people in the account. Nothing outside that list is possible through this connector, however a bot is asked to use it.

Gong is also only ever as wide as the permissions you tick when you connect your key — the setup guide lists the four.

Disconnecting

In Botseon

Open Plugins from the sidebar, press this connector's card to open its detail page, and under Accounts press Remove next to the account — or Uninstall to remove the plugin and every account connected to it at once. Either one revokes the stored connection immediately: nothing more is read or changed through it from that moment on. Install a plugin walks through the same screen step by step.

At Gong

Removing the account in Botseon deletes the stored key from Botseon, but the key itself stays valid at Gong until you delete or rotate it yourself. Do that from Gong's own API key page (an Access Key and its Access Key Secret) — the same place you created it — which is the only way to be sure nothing else can use it, since Botseon has no way to revoke a key it did not issue.

What Botseon keeps, and how your data is used

Whatever a bot reads or writes through this connector becomes part of your conversations and the record of that run — the same records, and the same retention schedule, as everything else a bot works on. Botseon is the processor for that content; your organisation decides what it may read and remember, and can delete it sooner than the schedule would on its own.

Your data is sent to a model provider only to produce the bot's answer, and for nothing else — it is not used to train any model. The Privacy Policy's Models and How long we keep it sections have the full detail, including exactly how long each kind of record is kept for.