Connect Gong to Rig

Before you start

• You need the Tech admin role in Gong to create API keys.
• Find the API base URL shown next to your key. Most accounts use https://api.gong.io and some regions use https://<region>.api.gong.io.
• If you restrict the key to trusted IP addresses, Gong rejects requests from anywhere else with a 403. Leave the field empty unless you have the address Rig syncs from.

Step 1: Create a Gong API key

1. In Gong, click Admin center in the left sidebar.
2. In the Settings tab, click API under Ecosystem.
3. Click + Get API key.
4. Enter a Key name. Leave TTL (days) empty if the key should not expire, because a key that expires stops the sync until you replace it.
5. Click Get API key, then copy the access key and the secret. Gong shows the secret only once, so you cannot read it again after you close the dialog.

Step 2: Connect it in Rig

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
2. Search for Gong, open the card and click Connect.
3. Access key: paste the access key.
4. Access key secret: paste the secret.
5. API base URL: pre-filled with https://api.gong.io. Change it only if Gong shows a regional address next to your key.
6. Earliest call start to sync: pre-filled with a rolling 180-day window. Leave it as it is, and Rig works out the date again at every sync.
7. Earliest call start to sync transcripts for: pre-filled with a rolling 90-day window. Leave it as it is, or narrow it if you want less transcript data.
8. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
9. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

What Rig pulls in

Gong lands in its own gong schema in your warehouse:

• Workspaces and users: your Gong workspaces and the people in them.
• Calls: call records inside the call window.
• Calls extensive: the same calls with CRM-linked parties (including Salesforce object IDs), topics, trackers and interaction stats.
• Transcripts: call transcripts inside the transcript window.

Transcripts are the heaviest and most sensitive stream. To reduce them, narrow the transcript window or leave the stream out when you pick streams.

Good to know

• Gong allows 3 requests per second and 10,000 per day for each key. Rig paces itself under that, and the default windows need only a few hundred requests a sync.
• Calls outside the window are not deleted. Each sync merges rows by call, so calls that age out of the window stay in the warehouse.
• For longer history, widen the two date fields and sync again. Rig does not backfill beyond them on its own.
• To disconnect Gong, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

What people use this for

• Tie conversations to deals and accounts
• Track the topics and trackers your team cares about
• Read the transcripts behind the numbers
• Compare rep conversation behaviour

More ideas for using Gong

Gong documentation

• Manage API keys in Gong
• Gong API introduction