Gong Connector

Index calls, transcripts, and trackers in Gong, along with the users and permission profiles that control access to them.

The Gong connector indexes calls, call transcripts, and keyword trackers in Gong, along with the users and permission profiles that define who can see each call.

Setup takes 2 steps:

  1. Create a Gong API key.
  2. Provide the connector its credentials and API base URL (see Required Configuration Values).

Create the API Key

Only a Gong user with the Tech admin role can manage API keys.

  1. In Gong, select Admin center from the left sidebar.
  2. On the Settings tab, under Ecosystem, select API.
  3. Select + Get API key.
  4. Enter a Key name, for example Atolio. Optionally, set:
    • TTL (days): when the key expires. Leave it empty for a key that does not expire. An expired key stops the connector, so if you set one, plan to rotate the key before it lapses.
    • Trusted IPs: the addresses allowed to use the key. If you set this, include the egress IP addresses of your Atolio deployment, or the connector’s requests are rejected.
  5. Copy the Access Key and Access Key Secret. Gong shows the secret only once, and it cannot be retrieved after you close the dialog.

The same page shows your tenant’s API base URL (for example https://us-12345.api.gong.io). The connector needs this value because each Gong tenant is served from its own regional host.

Note: The API page also offers Create Integration, for OAuth apps. The connector does not use OAuth; use + Get API key. If you do not see + Get API key, check that your Gong user has the Tech admin role.

Note: The connection test lists workspaces and fails if none are returned, or if a configured workspace is not found. If it fails with an authorization error, check that the access key is still active and that base-url matches the host shown on the API page.

Required Configuration Values

Enter these values in the Atolio Admin console (v4.24 and later), or send them to Atolio Support (your Deployment Engineer).

ValueWhere to find itExample / formatSecret
Access KeyCreate the API Key step 5; Admin center → Settings → Ecosystem → APIAlphanumeric stringYes
Access Key SecretCreate the API Key step 5; shown once, when the access key is createdLong random stringYes
API base URLAdmin center → Settings → Ecosystem → APIhttps://us-12345.api.gong.ioNo
Workspace names (optional: only to index some workspaces)Admin center → Settings → WorkspacesNorth America, EMEANo

Keep secrets secure: Share values marked “Yes” in the Secret column only through a password-manager share (e.g. 1Password) or another secure channel agreed with Atolio Support. Never send them in plain email, chat, or support tickets.

Configuration Example

Add this block to connector-values.yaml. Replace each <PLACEHOLDER> with the matching value from the table above, and remove any line marked “Only if” that doesn’t apply.

connectors:
  gong:
    default:
      gong:
        connector: gong
        instance: default
        source: gong
        common:
          enabled: true
          identity-provider: false
          cron-spec: "*/30 * * * *"
        secrets:
          access-key:
            value: "<ACCESS_KEY>"
          secret-access-key:
            value: "<ACCESS_KEY_SECRET>"
        configuration:
          base-url: "<API_BASE_URL>"
          workspaces:  # Only if indexing some workspaces
            - "<WORKSPACE_NAME>"

The cron-spec sets how often the connector syncs. See Scheduling Syncs.

Reference: Configuration Parameters

Only the two credentials and the base URL are required. Every other field has a safe default. The two credentials go under secrets:; the other parameters go under configuration:.

ParameterTypeRequiredDefaultDescription
access-keysecretYes—Gong API access key.
secret-access-keysecretYes—Gong API access key secret, paired with access-key.
base-urlstringYes—Your tenant’s Gong API base URL, e.g. https://us-12345.api.gong.io.
workspaceslistNoAll workspacesWorkspace names to index (see below).
processing-delay-minsintegerNo60How far behind “now” each run stops, giving Gong time to finish processing recent calls.
lookback-minsintegerNo240How far before the last checkpoint each run starts, to catch calls that appear late or were edited.
cache-ttl-hoursintegerNo48How long the connector remembers indexed calls, so calls re-read in the lookback are skipped unless they changed.
fill-from-daysintegerNo1825How far back the first run indexes calls (default 5 years).
fill-batch-size-hoursintegerNo168Size of each checkpointed batch during a fill (default 7 days).
priority-fill-every-nintegerNo1Re-index users and permission profiles every Nth run instead of every run.

Unset or 0 values use the default. processing-delay-mins must be shorter than lookback-mins, and lookback-mins shorter than cache-ttl-hours.

Note: Leave the optional settings at their defaults unless you are tuning freshness or API usage.

Scheduling Syncs

Gong does not provide change events, so the connector runs as a scheduled backfill. Set common.cron-spec to control how often it runs, e.g. */30 * * * * to sync every 30 minutes. Without a cron-spec, the connector runs a single backfill at startup and does not pick up new calls afterwards.

The first run indexes calls from the last fill-from-days. Each later run picks up new calls, and re-indexes recent calls that changed in Gong. Transcripts are indexed together with their calls.

Limiting Workspaces

Gong workspaces separate teams or business units within one Gong tenant, and each has its own calls, trackers, and permission profiles. By default the connector indexes every workspace. To index only some of them, list their names under workspaces:

configuration:
  # ... credentials ...
  workspaces:
    - "North America"
    - "EMEA"

Names are matched case-insensitively; workspace IDs are also accepted. An unknown name stops the connector, and the error lists the available workspaces.

Note: The Gong connector does not currently support per-resource included/excluded filters. Use workspaces to narrow scope.

Permissions

Atolio mirrors Gong’s call visibility rules:

  • Private calls are visible only to the call’s owner and its internal participants.
  • Other calls are visible to the owner and participants, plus anyone whose Gong permission profile grants access to them: all calls, their own calls, calls of their reports, or calls of their manager’s team.

Indexed Resources

ResourceDisplay nameDescription
callGong CallCalls, including participants, brief, key points, outline, highlights, topics, trackers, and linked CRM context.
transcriptGong TranscriptSpeaker-attributed call transcripts; child of the call.
trackerGong TrackerKeyword trackers defined in each workspace.
userGong UserGong users; resolve ACLs, call participants, and transcript speakers.
acl_groupGong ACL GroupGroups derived from permission profiles and the reporting hierarchy, used in call and transcript ACLs.