Skip to main content

Gong

What a customer says on a call is feedback that usually never leaves the call. It is spoken once, to one person, and the part worth acting on is four minutes into a forty-minute recording. Connecting Gong is how those moments join everything else Actify reasons over.

:::info Rolling out Connecting an account is available now. Choosing which calls become feedback, and bringing them in, is being released next — this page describes the integration as a whole so you can see what the key you create will eventually be used for. :::

What it does​

  • Connect a Gong account with an API key, and see the workspaces Actify can reach. Available now.
  • Choose which workspaces produce feedback, so recorded internal meetings do not become customer feedback. Coming soon.
  • Bring calls in on a schedule, as their transcripts finish processing. Coming soon.
  • Keep the customer's words, not ours. Only what external participants said becomes feedback. Coming soon.

Why Actify asks you for a key​

Every other integration here connects with a button that sends you to the provider to approve Actify. Gong is different: OAuth access requires being an approved Gong partner, so until that is in place, you create the credential and paste it into Actify.

That means it is worth being precise about what the key can do and what happens to it, which is what the rest of this page is for.

What Actify can access​

You choose the key's scopes when you create it. Actify needs three:

ScopeWhat it grants
api:workspaces:readList the workspaces in your Gong account. This is what the connection check uses.
api:calls:read:extensiveRead call metadata — title, time, duration, and who was on the call.
api:calls:read:transcriptRead call transcripts.

A key created without all three will connect only if the missing scope is not needed yet, and Actify tells you which one is absent rather than failing later in the background.

What is not requested​

  • api:calls:read:media-url is deliberately not requested. It would give access to the call audio and video themselves. Actify works from transcripts, so it does not ask for the recordings.
  • Actify does not request any scope that writes to Gong. It cannot change, delete, or add anything in your Gong account.

Whose words become feedback​

When ingestion arrives, only speech from external participants — the people Gong marks as not belonging to your company — will become feedback. Your own team's side of the call is not ingested.

This is not a nicety. Actify reasons over what customers tell you, and a recording is half your own pitch; ingesting that would mean your roadmap was partly justified by your own words repeated back to you.

Getting a key from Gong​

You need to be a technical administrator in Gong.

  1. In Gong, open Company settings → Ecosystem → API.
  2. Choose Get API key.
  3. Tick the three scopes in the table above before generating the key — a key's scopes cannot be changed afterwards, so a key made without them has to be created again.
  4. Copy the Access Key and Access Key Secret. Gong shows the secret once.

If your company has its own API address​

Most Gong accounts are reached at https://api.gong.io. Some — usually larger or region-specific ones — are given their own address that looks like https://us-1234.api.gong.io. Gong shows yours on the same page as the key.

If yours is not the default, enter it in the Gong API URL field when connecting. Leave the field blank otherwise.

Connecting​

  1. In Actify, go to Settings → Integrations → Gong.
  2. Paste the Access Key and Access Key Secret.
  3. Enter the Gong API URL only if Gong gave your company its own.
  4. Press Connect Gong.

Actify checks the key against Gong before storing anything. If the key is wrong, a scope is missing, or the API address is not right, you are told which — a connection that saved successfully is one that genuinely works.

Connecting is restricted to an organization's owner or admin. A key that can read every recorded call in your company is not a member-level thing to hand over.

Replacing a key​

Rotate a key in Gong, then use Replace key on the same screen. Both halves are replaced together, because a rotated Access Key comes with a new secret.

Rate limits​

Gong allows 3 API calls per second and 10,000 per day, and that allowance is shared across your whole Gong account — every tool you have connected to Gong draws on the same budget, not just Actify.

Actify's scheduled sync will stay well inside it, and if Gong does rate-limit a request, Actify waits and retries rather than treating the connection as broken.

Disconnecting​

Settings → Integrations → Gong → Disconnect.

Actify forgets its copy of the key immediately, and stops reading anything from Gong.

:::caution The key stays valid until you revoke it Unlike Slack and Linear, Actify cannot withdraw this credential — it is a key your Gong administrator created and it may be in use by other tools of yours. Disconnecting does not revoke it. If you want the key itself retired, delete it in Gong as well. :::

Feedback already ingested from Gong is kept, and continues to say which call it came from. Actify does not delete evidence when a connection ends.

Data stored​

  • The Gong API address your account uses
  • The names and ids of the workspaces the key can see
  • Once ingestion arrives, for each ingested call: its Gong id and link, title, time, duration, and the external participants' names, email addresses and what they said

The Access Key and its secret are stored encrypted in a secrets vault, readable only by the Actify service. They are never shown again after you paste them, never written to a log, and never sent back to your browser.

Questions about this integration: [email protected]