What connects

The connection uses a Gong access key and access key secret over HTTP Basic authentication. Gong plan/API access is required; the read path needs api:calls:read and the write path needs api:calls:create.

Create the API credentials in Gong and provide both the access key and secret.
The key must be allowed to read calls and transcripts. Creating a post-call record additionally requires the call-create scope.
The write path must attribute the new call record to a Gong user available to the connected workspace.

Information used

The inbound sync imports Gong call metadata and transcript monologues into prior-conversation context. A first sync looks back 90 days; later runs use a cursor or watermark with a small overlap to avoid boundary misses.

Call title, start time, duration, participants, and recording URL where Gong provides them.
Transcript segments with speaker, affiliation, topic, timing, and text where Gong permissions allow.
A run is bounded at 30 call-list pages, and transcript backlog processing is bounded at 500 calls; later scheduled runs continue the work.

Why it is useful

Prior calls, objections, commitments, and unresolved questions can give a seller continuity without requiring a manual search through Gong during the next conversation.

How the workflow behaves

Gong history is imported on the scheduled sync cadence. Write-back can be invoked by an approved-proposal flow or by the explicit rep-initiated forward-notes action; it is never automatic.

The outbound action creates a new outbound Gong call record containing the explicit note or approved outcome subject and content.
The new record is attributed to a Gong user and uses a stable client identity so a retry does not create a duplicate.
An existing Gong call is never mutated by this integration.

Prerequisites and limits

Use a Gong plan with API access, create an access key and secret, grant the required read scope (and call-create scope if write-back is wanted), and ensure the key can resolve a Gong user for attribution.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Security and privacy boundaries

Newly saved connector credentials are encrypted before storage.

Connected tools sync server-side under the user's own credentials. Requested permissions and data flows are connector-specific.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Only an explicitly rep-initiated note or an approved outcome is sent on the write path. The provider's call and transcript permissions determine what history is available to IntellaOne.

Read and write scopes are separate: a key can be limited to inbound history.
Gong may rate-limit or reject a call record; a successful write depends on provider acceptance.