Gong Connector

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.

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.

Credentials

Provide Configuration

Only the two credentials and the base URL are required; every other field has a safe default.

connector: gong
instance: default
source: gong
common:
  enabled: true
  cron-spec: "*/30 * * * *"
configuration:
  access-key:
    value: "<your-access-key>"
  secret-access-key:
    value: "<your-access-key-secret>"
  base-url: "https://us-12345.api.gong.io"

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