Skip to main content

Gong

Read Gong calls, transcripts, users and deal activity with a Gong API access key.

Connect it with: User name and password. Gong's own documentation: https://help.gong.io/docs/receive-access-to-the-api.

What agents can do​

Connect Gong so the agents working your tasks can reach it. With it connected, they can:

  • List calls in a date range and read their participants, topics and trackers.
  • Read call transcripts to summarise a deal or pull customer quotes.
  • Read users and workspaces to know who ran a call.
  • Read activity and interaction stats for coaching reports.

Before you start​

  • A Gong technical administrator, who alone can create API keys.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Gong​

Jaah connects to Gong with a user name and password, not with a sign-in button.

Connect with an API key​

Find each value first:

  • API base URL: Your company's API address, shown at the top of Gong's Admin center > Settings > Ecosystem > API page; keep https://api.gong.io unless that page names another.
  • Access key: In Gong, open Admin center > Settings > Ecosystem > API, select Get API key, name it Jaah, select Get API key again and copy the Access key.
  • Access key secret: Shown beside the access key in the same Get API key window; copy it before closing, because Gong never shows it again.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Gong card.
  2. Name the secret and choose who can use it.
  3. Fill in API base URL, Access key, Access key secret.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Gong with a user name and password, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Gong's API once (GET <API base URL>/v2/workspaces) with the stored values, and shows whether Gong accepted it, or which value Gong refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: base_url, access_key, access_key_secret.

Tell the agent in your task description which secret to use, for example “use the Gong secret org/gong”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Gong once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Gong's side too, change the password at Gong or remove the user.

Limitations​

  • A key reaches every call in the company, whatever the creating admin's own permissions; treat it as company-wide access.
  • Gong limits the API to 3 calls per second and 10,000 calls per day per company by default.
  • A key may carry an expiry (TTL) and a trusted-IP list set when it was created; a key restricted to IPs must allow the Jaah control plane and runners.
  • Agents can do only what the connected Gong account allows.

Troubleshooting​

Test says Gong rejected the access key (401)

The key was revoked, expired (its TTL ran out) or the secret was mistyped. Create a new key under Admin center > Settings > Ecosystem > API and select Replace on the secret.

Test says Gong rejected the access key (403)

The key has a trusted-IP list that does not include the address Jaah calls from. Create a key without the IP restriction, or ask Gong support to add Jaah's addresses.

Test says Gong cannot be reached at that address

The API base URL is wrong. Copy the base URL shown on Gong's API settings page, or put back https://api.gong.io.

Still stuck? Select Test and read the result: it names the value Gong refused and the status it answered.

FAQ​

Why does Gong need two values?

Gong authenticates with HTTP Basic: the access key is the user name and the access key secret the password. Jaah sends them that way.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Gong account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.