Gong | Alephant Documentation

What it indexes

The Gong connector creates one searchable document per call transcript. It combines transcript data with call details fetched from Gong’s extensive-call endpoint.

Call data	Indexing behavior
Transcript	Speaker segments are joined into speaker-attributed text. Sentence text is indexed; audio and video media are not downloaded.
Call details	The call title becomes the document identifier. Purpose is added as a call description, and the Gong call URL becomes the citation.
Parties	When Gong returns party names or email addresses, they identify speakers in searchable text. If neither value is available, the speaker is `Unknown`.
Dates and metadata	The call start time is used for both document creation and update time. The call’s source system is stored as `client` metadata.
Scope	Optional workspace names or IDs restrict calls. With no workspace entries, transcripts from all workspaces visible to the credential are requested.

The current Admin form does not expose the connector’s internal speaker-anonymization option. Treat returned participant names and email addresses as indexed content when planning access.

Prerequisites

Create a Gong API access key and access-key secret for a dedicated integration user.
Grant access to list workspaces, read call transcripts, and read extensive call details including parties.
Determine whether the account uses the default US API host or a region-specific Gong API host.
If limiting scope, collect each exact workspace ID or exact case-sensitive workspace name.
The connector worker only needs HTTPS access to the selected Gong API host; it stores but does not open the citation URL returned by Gong.
End-user browsers must be able to reach the host in the returned Gong citation URL to open the source call.
Decide whether the deployment-level GONG_CONNECTOR_START_TIME should bound historical ingestion, while accounting for the connector’s one-day overlap.

Credentials

Method	OpenCore credential values	Authentication behavior
Gong API key pair	`gong_access_key: <GONG_ACCESS_KEY>`, `gong_access_key_secret: <GONG_ACCESS_KEY_SECRET>`, optional `gong_base_url: <GONG_API_BASE_URL>`	OpenCore Base64-encodes the key and secret as HTTP Basic authentication. The Base URL defaults to `https://api.gong.io`.

For non-US data residency, enter the region-specific HTTPS host supplied for the Gong account. OpenCore accepts api.gong.io or a subdomain ending in .api.gong.io, adds https:// when omitted, and rejects HTTP or non-Gong hosts.

Configure in OpenCore

In the Admin panel, open Connectors, select Gong, and create the access-key credential. Set the optional regional Base URL only when the account requires it.
Under Workspaces, enter zero or more exact workspace names or IDs. Leave the list empty only when all credential-visible workspaces are approved.
If several entries are configured, OpenCore keeps every entry that resolves. Invalid entries are logged and skipped; if none resolve, indexing fails instead of widening to all workspaces.
Choose Private and assign OpenCore groups for restricted call content. Use Public only when every OpenCore account may search every transcript and participant identifier in scope.
Set refresh and cleanup options, create the connector, and run the first indexing attempt.

On the first checkpoint invocation, OpenCore resolves workspace IDs and caches one time range, then returns without fetching a transcript page. Later invocations process one page for one workspace at a time.

Permissions

The Gong key pair controls which workspaces, calls, transcripts, details, and parties OpenCore can ingest. Gong workspace membership, call-library access, team permissions, and individual call access are not synchronized into OpenCore; this connector has no source ACL or query-time Gong access check.

After indexing, search access is controlled by the connector’s OpenCore Private groups or Public mode. Any user with connector access can search the full indexed transcript and returned participant identifiers, even if that user cannot open the call in Gong. Use a least-privilege Gong integration user, explicit workspace scope, and separate connectors and OpenCore groups for audiences that must not share calls.

Verify

Run the connector and confirm configured workspace names or IDs resolve to the intended workspace IDs.
Continue checkpoint invocations until the run is complete, then search for one call title and a distinctive transcript sentence from each configured workspace.
Confirm a call from an unconfigured workspace is absent. With an empty workspace list, confirm the all-workspace scope is intentional.
Inspect a result for call purpose, speaker identifiers, call start time, and the Gong citation URL.
Verify the earliest indexed calls against GONG_CONNECTOR_START_TIME and the one-day overlap; do not treat the deployment value as a strict no-ingestion boundary.
Test every assigned OpenCore group because Gong permissions will not be re-evaluated at search time.

Troubleshooting

Symptom	What to check
Requests return 401	Replace the access key or access-key secret and confirm they belong to the same Gong API credential.
Regional requests target the wrong host	Set the account’s exact regional API Base URL. Only HTTPS `api.gong.io` or `*.api.gong.io` hosts are accepted.
No configured workspace resolves	Use the exact case-sensitive name or workspace ID. If at least one entry resolves, invalid entries are skipped; if none resolve, the connector fails closed.
Empty workspace configuration reads unexpected calls	Empty scope means all workspaces visible to the credential. Add explicit workspace names or IDs and use a narrower integration user.
The first checkpoint produces no documents	This is expected. The first invocation resolves workspace scope and caches the time range; a later invocation fetches the first transcript page.
Historical calls appear before the configured start	OpenCore takes the later of the poll start and `GONG_CONNECTOR_START_TIME`, then moves the request start one day earlier so completed calls can appear. The setting is not a strict privacy cutoff.
A transcript is delayed after it appears in Gong	Call details can lag behind the transcript. OpenCore retries unresolved details across checkpoint runs, with six total attempts and gated exponential delays; unresolved calls then produce `ConnectorFailure`.
Pagination restarts and documents repeat	Gong cursors can expire after roughly one hour from the pagination sequence start. OpenCore restarts the current workspace; call-ID upserts make reprocessing idempotent.
Requests receive 429 or transient 5xx errors	The connector spaces requests by at least 0.5 seconds and configures a retry adapter for those statuses. Do not assume every POST was retried; inspect the attempt log, wait for the limit or service window to recover, and rerun when needed.
Users can search calls they cannot open in Gong	This is expected because Gong ACLs are not synchronized. Restrict the connector with OpenCore groups or split workspaces across connectors.