Integrations / Gong

Gong

Gong revenue intelligence for calls, transcripts, scorecards, users, and sales conversation analytics.

Basic auth

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Gong workspace on a plan that includes API access.

A user who can create API keys (usually tech admin).

Vendor setup

Get the credential

Create an access key

In Gong, open Company Settings → API. Create an access key and secret.

Paste in Telara

Settings → Integrations → Gong.

In Telara

Connect in Telara

Basic auth

Gong API access key and secret. Gong API access depends on company plan and assigned seats.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

Access Key
Access Key Secret

Knowledge

What gets indexed

Resource	Coverage
Users	Partial — not every record the vendor holds is synced
Call	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Users	Up to 1 day	Removed records disappear on the next full sync
Call	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Users, Call.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

API access depends on plan and assigned seats. A seatless tech admin may still be unable to issue keys.

The key sees the workspace it was issued for.