Skip to main content

Gong

This connector captures data from Gong into Estuary collections.

Gong is a revenue intelligence platform that captures and analyzes customer interactions across calls, emails, and meetings to provide insights for sales teams.

Supported data resources

The following data resources are supported through the Gong API:

By default, each resource is mapped to an Estuary collection through a separate binding.

Prerequisites

  • A Gong account with API access enabled.
  • A Gong API key consisting of an access key and access key secret. To generate API credentials, navigate to your Gong settings and create a new API key pair.

Configuration

You configure connectors either in the Estuary web app, or by directly editing the catalog specification files. See connectors to learn more about using connectors. The values and specification sample below provide configuration details specific to the Gong source connector.

Properties

Endpoint

PropertyTitleDescriptionTypeRequired/Default
/credentials/access_keyAccess KeyGong API Access Key.stringRequired
/credentials/access_key_secretAccess Key SecretGong API Access Key Secret.stringRequired
/regionRegionAPI region for your Gong account.stringDefault: us-55616
/start_dateStart DateUTC date and time in the format YYYY-MM-DDTHH:MM:SSZ. Data generated before this date will not be replicated. If left blank, defaults to 30 days before the current date.string
/calls_lookback_windowCalls Lookback WindowNumber of days to look back for calls that may have been enriched after the initial sync. Must be between 1 and 30.integerDefault: 7

Bindings

PropertyTitleDescriptionTypeRequired/Default
/nameData resourceResource in Gong from which collections are captured.stringRequired
/intervalIntervalInterval between data syncs.string

Sample

captures:
${PREFIX}/${CAPTURE_NAME}:
endpoint:
connector:
image: ghcr.io/estuary/source-gong:v1
config:
credentials:
access_key: <secret>
access_key_secret: <secret>
region: us-55616
start_date: 2024-01-01T00:00:00Z
bindings:
- resource:
name: calls
target: ${PREFIX}/calls
- resource:
name: users
target: ${PREFIX}/users
- resource:
name: scorecards
target: ${PREFIX}/scorecards
- resource:
name: scorecard_definitions
target: ${PREFIX}/scorecard_definitions