Gong API - Parable

Gong is a revenue intelligence platform that captures and analyzes customer interactions (calls, meetings, emails) to provide insights for sales teams. It offers conversation analytics, deal intelligence, coaching scorecards, and CRM integration capabilities. The Gong API (v2) provides programmatic access to calls, transcripts, users, activity statistics, scorecards, trackers, workspaces, CRM entities, and audit logs.

Overview
Setup Guide
Permissions
Troubleshooting

Gong

Connect Parable to Gong for calls, CRM, meetings, and workspace analytics using HTTP Basic authentication with a workspace-scoped Access Key and Secret.

Conversations & CRM

Call recordings, transcripts, CRM associations, meetings

People & workspace

Users, workspaces, scorecards, trackers, audit logs

Gong (OAuth)

Connect Parable to Gong using OAuth 2.0 with Parable’s in-app authorization wizard. You create a Gong OAuth application, register Parable’s redirect URI, set API Base URL under Connection Settings, then authorize from the Provider page. Parable exchanges the authorization code, stores tokens securely, and may update API Base URL from Gong when the token response includes a regional endpoint.You do not paste a refresh token manually.

Conversations & CRM

Call recordings, transcripts, CRM associations, meetings

People & workspace

Users, workspaces, scorecards, trackers, audit logs

Gong (OAuth)

Authorize (browser redirect):

GET https://app.gong.io/oauth2/authorize

Token exchange (used by Parable after authorization):

POST https://app.gong.io/oauth2/generate-customer-token

Authentication uses client_secret_basic (HTTP Basic with client ID and secret).

Data streams

This Provider Plugin defines 20 data streams.

Stream	Description	Sync
`calls`	List all calls by date range from Gong. Returns basic call metadata including call ID, title, scheduled time, duration, direction, and participants.	incremental
`calls_extensive`	Retrieve detailed/extensive call data from Gong including topics, trackers, parties, key points, highlights, and other rich content fields. Uses POST with filter and content selector.	incremental
`call_transcripts`	Retrieve call transcripts from Gong. Returns transcript segments with speaker identification, timestamps, and text for each call. NOTE: Gong does not expose a per-transcript modified timestamp; the watermark is the run window’s end (`fromDateTime`), not a record-level cursor. Re-running an overlapping window refetches transcripts (PK = callId). Bronze stores every run as a new partition; downstream Silver/Gold layers are responsible for dedup-on-`callId`-keep-latest.	incremental
`users`	List all Gong users in the organization. Returns user profiles including name, email, role, and activity status.	full
`user_settings_history`	Retrieve the settings change history for each Gong user. Returns historical records of user settings changes over time, useful for tracking configuration changes and compliance auditing. This is a child endpoint of users — it iterates over all users and fetches settings history for each one via GET /v2/users//settings-history.	full
`scorecards`	Retrieve all scorecard definitions/settings from Gong. Returns scorecard templates with their questions and scoring criteria.	full
`answered_scorecards`	Retrieve answered/completed scorecards for calls within a date range. Returns scorecard responses with scores, answers, and reviewer information.	incremental
`trackers`	Retrieve all keyword tracker definitions from Gong. Returns tracker configurations including keywords, phrases, and associated settings.	full
`workspaces`	List all company workspaces in Gong. Returns workspace definitions with names and configuration.	full
`library_folders`	List all public library folders in Gong. Returns folder hierarchy for organizing call recordings.	full
`logs`	List log entries from Gong by type and time range. Returns audit/activity log entries for compliance and monitoring.	incremental
`manual_crm_associations`	List calls that have been manually associated with CRM objects since a given time. Returns association mappings between calls and CRM entities.	incremental
`daily_activity`	Retrieve day-by-day activity statistics for users. Returns one row per user (with a `dayActivity` array) snapshotting the configured incremental window. NOTE: snapshot semantics — PK = userId; rerunning with an overlapping window emits a fresh snapshot row per user for that window. Bronze appends every run as a new partition; Silver/Gold are responsible for dedup-on-userId-keep-latest. `cursorField` is `fromDate`, the window-start filter sent in the request body, since aggregate responses have no per-record timestamp.	incremental
`interaction_stats`	Retrieves interaction statistics for users including coaching and whisper call metrics. Provides data on manager-rep interaction patterns.	incremental
`crm_entities`	DISABLED: Gong has no list CRM entities API. GET /v2/crm/entities only fetches objects by known CRM IDs (dev verification). Use calls_extensive (Extended context) and manual_crm_associations for CRM data. Enable only for explicit ID-based enrichment follow-ups.	full
`meetings`	DISABLED: Gong has no list meetings API. Meeting metadata (meetingUrl, calendarEventId, schedule) is available on calls and calls_extensive. Enable only if a future Gong list endpoint is added.	incremental
`activity_aggregate`	Retrieve aggregated user activity statistics from Gong. Returns one row per user summarising the configured incremental window. NOTE: snapshot semantics — PK = userId; rerunning with an overlapping window emits a fresh snapshot row per user for that window. Bronze appends every run as a new partition; Silver/Gold are responsible for dedup-on-userId-keep-latest. `cursorField` is `fromDate`, the window-start filter sent in the request body.	incremental
`activity_aggregate_by_period`	Retrieve user activity statistics aggregated by time period from Gong. Same metrics as activity_aggregate broken down by configurable time buckets. NOTE: snapshot semantics — PK = userId; rerunning with an overlapping window emits a fresh snapshot row per user for that window. Bronze appends every run as a new partition; Silver/Gold are responsible for dedup-on-userId-keep-latest. `cursorField` is `fromDate`, the window-start filter sent in the request body.	incremental
`permission_profiles`	Retrieve all permission profiles from Gong for each workspace. Returns workspace permission profiles including profile IDs, names, and access settings.	full
`crm_integrations`	Retrieve CRM integration configuration from Gong. Returns details about connected CRM systems, schema fields, deal stages, and object mappings.	full

Gong

What You’ll Need

Credential	What it is
Access Key	Workspace API access key from Gong
Access Key Secret	Secret shown once when the key is created
API Base URL	Gong API host (`https://api.gong.io` or your regional URL from Company Settings)

Info: Setup access in Gong. These steps require Technical Administrator (to create API keys and manage scopes), or a colleague with equivalent permissions who can create credentials for you. If that is not you, ask your Gong administrator.

Your Gong API Base URL. Most workspaces use https://api.gong.io. Regional endpoints (for example https://us-12345.api.gong.io) appear under Company Settings → Ecosystem → API.

Info: Gong API keys are workspace-scoped. They can expire; Gong notifies workspace admins before rotation.

Step 1: Open Gong API settings

Sign in to Gong as a Technical Administrator.
Open Company Settings → Ecosystem → API (or go to app.gong.io/company/api).

Step 2: Enable required API scopes

Each API key in Gong has scopes toggled individually. Enable only the scopes for the data categories you want Parable to collect.

Scope	Purpose
`api:calls:read:basic`	Call recordings
`api:calls:read:extensive`	Call details & AI insights
`api:calls:read:transcript`	Call transcripts
`api:users:read`	Users & settings history
`api:settings:scorecards:read`	Scorecard definitions
`api:stats:scorecards`	Scorecard responses
`api:settings:trackers:read`	Tracker definitions
`api:workspaces:read`	Workspaces & library folders
`api:logs:read`	Audit logs
`api:crm-calls:manual-association:read`	CRM call associations
`api:stats:user-actions:detailed`	Daily user activity
`api:stats:interaction`	Interaction statistics
`api:stats:user-actions`	Activity aggregates
`api:crm:get-objects`	CRM entities (Accounts, Contacts, Deals)
`api:meetings:integration:status`	Meetings
`api:permission-profile:read`	Permission profiles
`api:crm:integrations:read`	CRM integrations

Info: api:permission-profile:read may need to be enabled by Gong Support on some tiers.

Step 3: Create API credentials

Click Get API Key.
Copy the Access Key and Access Key Secret. The secret is shown once — store it in a password manager before closing the page.

Warning: Copy your Access Key Secret now! This is the only time it will be displayed. Store it in a secure password manager before closing this page.

Step 4: Enter values in the form

Access Key, Access Key Secret, and API Base URL: Enter the values from Gong (use your regional base URL if applicable).
Click Save & test connection.

Use environment variables so secrets do not appear in shell history:

Test with curl

read -rs -p "Access Key: " GONG_KEY && echo
read -rs -p "Access Key Secret: " GONG_SECRET && echo
read -p "API Base URL [https://api.gong.io]: " GONG_BASE_URL
GONG_BASE_URL="${GONG_BASE_URL:-https://api.gong.io}"
curl --silent --user "${GONG_KEY}:${GONG_SECRET}" \
  "${GONG_BASE_URL}/v2/workspaces"
unset GONG_KEY GONG_SECRET GONG_BASE_URL

Success: Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now configure this Provider in Parable.

Tip: A successful response includes requestId, records, and a workspaces array. Prefer curl --netrc-file over curl -u "KEY:SECRET" for one-liners so credentials are not written to shell history.

Tip: Rate Limits: Gong enforces rate limits of about 3 requests/second and 10,000 requests per day; Parable respects Retry-After. Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

Gong (OAuth)

What You’ll Need

Credential	What it is
Client ID	OAuth application client ID from Gong
Client Secret	OAuth application client secret
API Base URL	Gong API host. Default `https://api.gong.io`; use your regional URL when Gong provides one

Info: Setup access in Gong. These steps require Technical Administrator (to create OAuth applications and manage scopes), or a colleague with equivalent permissions who can create credentials for you. If that is not you, ask your Gong administrator.

A Gong OAuth application with the API scopes you need enabled
Permission to register redirect URIs on that OAuth application
Your Gong API Base URL. Most workspaces use https://api.gong.io. Regional endpoints (for example https://us-12345.api.gong.io) appear under Gong Settings → Technical Settings → API Authentication.

Step 1: Create a Gong OAuth application

Sign in to Gong as a Technical Administrator.
Open Company Settings → Ecosystem → API.
Select the Integrations tab.
Create an OAuth application and note the Client ID and Client Secret.

Step 2: Enable required API scopes

Each OAuth application in Gong has scopes toggled individually. Enable only the scopes for the data categories you want Parable to collect.

Scope	Purpose
`api:calls:read:basic`	Call recordings
`api:calls:read:extensive`	Call details & AI insights
`api:calls:read:transcript`	Call transcripts
`api:users:read`	Users & settings history
`api:settings:scorecards:read`	Scorecard definitions
`api:stats:scorecards`	Scorecard responses
`api:settings:trackers:read`	Tracker definitions
`api:workspaces:read`	Workspaces & library folders
`api:logs:read`	Audit logs
`api:crm-calls:manual-association:read`	CRM call associations
`api:stats:user-actions:detailed`	Daily user activity
`api:stats:interaction`	Interaction statistics
`api:stats:user-actions`	Activity aggregates
`api:crm:get-objects`	CRM entities (Accounts, Contacts, Deals)
`api:meetings:integration:status`	Meetings
`api:permission-profile:read`	Permission profiles
`api:crm:integrations:read`	CRM integrations

Info: api:permission-profile:read may need to be enabled by Gong Support on some tiers.

Step 3: Create the connection in Parable

Open the Gong OAuth Provider in Parable and click to add a connection.
Enter a connection name.
Under Connection Settings, set API Base URL. Leave the default (https://api.gong.io) unless Gong shows a regional endpoint (for example https://us-12345.api.gong.io).
Copy the Redirect URI shown on the form.
Click Continue to OAuth setup.

Parable creates the connection and opens the OAuth authorization screen.

Step 4: Register the redirect URI in Gong

In your Gong OAuth application settings, add the Redirect URI you copied from Parable as an allowed redirect URI.
Register it exactly as shown (including your workspace subdomain and path).

Info: The redirect URI includes your workspace subdomain. Example: https://{tenant-name}.parable.work/platform/providers/oauth/callback. Do not register the apex host alone (https://parable.work/...). Gong must match the subdomain of the workspace where you started the connection.

Step 5: Authorize with Parable

On the OAuth authorization screen, enter your Client ID and Client Secret.
Click Connect with OAuth. You are redirected to Gong to approve permissions.
After you approve, Parable redirects back automatically, stores your tokens, and validates the connection. If Gong returns a regional API host in the token response, Parable updates API Base URL on the connection.

Info: Parable validates credentials automatically after authorization. You do not paste a refresh token, and there is no separate Save & test connection step on the OAuth authorization screen.

To rotate credentials later, click Re-authorize with OAuth on the connection page.Parable shows API Base URL under Connection Settings on the Gong OAuth create and connection forms (default https://api.gong.io). Syncs use this value as the Gong API host. After OAuth completes, if Gong returns a regional host with the tokens, Parable updates the same setting.

Value	When to use
`https://api.gong.io`	Default for most Gong accounts
`https://us-12345.api.gong.io` (example)	Regional host shown in Gong Settings → Technical Settings → API Authentication

Gong

Scope	Purpose
`api:calls:read:basic`	Call recordings
`api:calls:read:extensive`	Call details & AI insights
`api:calls:read:transcript`	Call transcripts
`api:users:read`	Users & settings history
`api:settings:scorecards:read`	Scorecard definitions
`api:stats:scorecards`	Scorecard responses
`api:settings:trackers:read`	Tracker definitions
`api:workspaces:read`	Workspaces & library folders
`api:logs:read`	Audit logs
`api:crm-calls:manual-association:read`	CRM call associations
`api:stats:user-actions:detailed`	Daily user activity
`api:stats:interaction`	Interaction statistics
`api:stats:user-actions`	Activity aggregates
`api:crm:get-objects`	CRM entities (Accounts, Contacts, Deals)
`api:meetings:integration:status`	Meetings
`api:permission-profile:read`	Permission profiles
`api:crm:integrations:read`	CRM integrations

Gong (OAuth)

Scope	Purpose
`api:calls:read:basic`	Call recordings
`api:calls:read:extensive`	Call details & AI insights
`api:calls:read:transcript`	Call transcripts
`api:users:read`	Users & settings history
`api:settings:scorecards:read`	Scorecard definitions
`api:stats:scorecards`	Scorecard responses
`api:settings:trackers:read`	Tracker definitions
`api:workspaces:read`	Workspaces & library folders
`api:logs:read`	Audit logs
`api:crm-calls:manual-association:read`	CRM call associations
`api:stats:user-actions:detailed`	Daily user activity
`api:stats:interaction`	Interaction statistics
`api:stats:user-actions`	Activity aggregates
`api:crm:get-objects`	CRM entities (Accounts, Contacts, Deals)
`api:meetings:integration:status`	Meetings
`api:permission-profile:read`	Permission profiles
`api:crm:integrations:read`	CRM integrations

Info: api:permission-profile:read may need to be enabled by Gong Support on some tiers.

Success: After authorization, Parable shows an authorized status and validates the connection automatically.

Tip: Rate Limits: Gong enforces rate limits of about 3 requests per second; Parable respects Retry-After. Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

Activity Aggregate

Developer identifier: activity_aggregateActivity Aggregate. Retrieve aggregated user activity statistics from Gong. Returns one row per user summarising the configured incremental window. cursorField is fromDate, the window-start filter sent in the request body.

Enables: Measure each user’s provider-reported aggregate activity counts across the configured request window.
Scope: Reads the records selected by Gong API’s /{apiVersion}/stats/activity/aggregate operation as a snapshot stream using incremental synchronization. Visibility follows the Gong API credential, workspace access, and the endpoint’s content-selection settings. Aggregate activity counts reflect Gong’s definitions and the configured request window; they do not establish work quality or employee performance. This stream supplies no reliable deletion signal.

User Aggregate Activity Stats

Developer identifier: activity_aggregate.userAggregateActivityStatsUser Aggregate Activity Stats. Aggregated activity counts for the user over the window. It preserves the nested context needed to interpret the parent activity aggregate.

Enables: Attribute user aggregate activity stats in activity_aggregate.userAggregateActivityStats to the parent activity aggregate; identify parent records where that nested user aggregate activity stats object is absent.
Interpretation: Gong API reports user aggregate activity stats as a nested object on each activity aggregate; optional children may be absent from a valid response.

Calls As Host

Developer identifier: activity_aggregate.userAggregateActivityStats.callsAsHostCalls As Host. Total calls as host. It supplies the calls as host measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls as host through activity_aggregate.userAggregateActivityStats.callsAsHost for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls as host as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Attended

Developer identifier: activity_aggregate.userAggregateActivityStats.callsAttendedCalls Attended. Total calls attended. It supplies the calls attended measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls attended through activity_aggregate.userAggregateActivityStats.callsAttended for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls attended as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Comments Given

Developer identifier: activity_aggregate.userAggregateActivityStats.callsCommentsGivenCalls Comments Given. Total comments given. It supplies the calls comments given measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls comments given through activity_aggregate.userAggregateActivityStats.callsCommentsGiven for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls comments given as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Comments Received

Developer identifier: activity_aggregate.userAggregateActivityStats.callsCommentsReceivedCalls Comments Received. Total comments received. It supplies the calls comments received measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls comments received through activity_aggregate.userAggregateActivityStats.callsCommentsReceived for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls comments received as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Gave Feedback

Developer identifier: activity_aggregate.userAggregateActivityStats.callsGaveFeedbackCalls Gave Feedback. Total calls where the user gave feedback. It supplies the calls gave feedback measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls gave feedback through activity_aggregate.userAggregateActivityStats.callsGaveFeedback for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls gave feedback as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Marked As Feedback Given

Developer identifier: activity_aggregate.userAggregateActivityStats.callsMarkedAsFeedbackGivenCalls Marked As Feedback Given. Total calls marked as feedback given. It supplies the calls marked as feedback given measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls marked as feedback given through activity_aggregate.userAggregateActivityStats.callsMarkedAsFeedbackGiven for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls marked as feedback given as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Marked As Feedback Received

Developer identifier: activity_aggregate.userAggregateActivityStats.callsMarkedAsFeedbackReceivedCalls Marked As Feedback Received. Total calls marked as feedback received. It supplies the calls marked as feedback received measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls marked as feedback received through activity_aggregate.userAggregateActivityStats.callsMarkedAsFeedbackReceived for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls marked as feedback received as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Received Feedback

Developer identifier: activity_aggregate.userAggregateActivityStats.callsReceivedFeedbackCalls Received Feedback. Total calls where the user received feedback. It supplies the calls received feedback measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls received feedback through activity_aggregate.userAggregateActivityStats.callsReceivedFeedback for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls received feedback as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Requested Feedback

Developer identifier: activity_aggregate.userAggregateActivityStats.callsRequestedFeedbackCalls Requested Feedback. Total calls where the user requested feedback. It supplies the calls requested feedback measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls requested feedback through activity_aggregate.userAggregateActivityStats.callsRequestedFeedback for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls requested feedback as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Scorecards Filled

Developer identifier: activity_aggregate.userAggregateActivityStats.callsScorecardsFilledCalls Scorecards Filled. Total scorecards filled. It supplies the calls scorecards filled measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls scorecards filled through activity_aggregate.userAggregateActivityStats.callsScorecardsFilled for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls scorecards filled as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Scorecards Received

Developer identifier: activity_aggregate.userAggregateActivityStats.callsScorecardsReceivedCalls Scorecards Received. Total scorecards received. It supplies the calls scorecards received measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls scorecards received through activity_aggregate.userAggregateActivityStats.callsScorecardsReceived for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls scorecards received as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Shared Externally

Developer identifier: activity_aggregate.userAggregateActivityStats.callsSharedExternallyCalls Shared Externally. Total calls shared externally. It supplies the calls shared externally measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls shared externally through activity_aggregate.userAggregateActivityStats.callsSharedExternally for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls shared externally as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Calls Shared Internally

Developer identifier: activity_aggregate.userAggregateActivityStats.callsSharedInternallyCalls Shared Internally. Total calls shared internally. It supplies the calls shared internally measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure calls shared internally through activity_aggregate.userAggregateActivityStats.callsSharedInternally for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls shared internally as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Others Calls Listened To

Developer identifier: activity_aggregate.userAggregateActivityStats.othersCallsListenedToOthers Calls Listened To. Total others’ calls listened to. It supplies the others calls listened to measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure others calls listened to through activity_aggregate.userAggregateActivityStats.othersCallsListenedTo for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports others calls listened to as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

Own Calls Listened To

Developer identifier: activity_aggregate.userAggregateActivityStats.ownCallsListenedToOwn Calls Listened To. Total own calls listened to. It supplies the own calls listened to measure for the user aggregate activity stat at the provider’s declared unit and grain.

Enables: Measure own calls listened to through activity_aggregate.userAggregateActivityStats.ownCallsListenedTo for each user aggregate activity stat and compare only values with the same unit and record grain.
Interpretation: Gong API reports own calls listened to as a measure on each user aggregate activity stat; compare only records with the same unit and aggregation grain.

User Email Address

Developer identifier: activity_aggregate.userEmailAddressUser Email Address. Email address of the user. It supplies the provider-reported address or location facet for the activity aggregate, not a residency determination.

Enables: Attribute each activity aggregate to a person or account by the exact user email address in activity_aggregate.userEmailAddress; identify addresses that do not match the Gong API directory.
Interpretation: Gong API reports user email address as an address on each activity aggregate; aliases, casing, and unverified addresses can prevent a one-to-one person match.

User ID

Developer identifier: activity_aggregate.userIdUser ID. User ID. It provides the reference needed to connect the activity aggregate to the corresponding provider object.

Enables: Match repeated activity aggregate entries on user ID in activity_aggregate.userId; collapse only entries that share this declared transform key.
Interpretation: Gong API reports user ID as an identifier in its user namespace; it is not a universal identity outside Gong API. The connector explicitly marks this field as a transform deduplication key.

Activity Aggregate By Period

Developer identifier: activity_aggregate_by_periodActivity Aggregate By Period. Retrieve user activity statistics aggregated by time period from Gong. Same metrics as activity_aggregate broken down by configurable time buckets. cursorField is fromDate, the window-start filter sent in the request body.

Enables: Compare each user’s provider-reported activity counts across the configured period buckets.
Scope: Reads the records selected by Gong API’s /{apiVersion}/stats/activity/aggregate-by-period operation as a snapshot stream using incremental synchronization. Visibility follows the Gong API credential, workspace access, and the endpoint’s content-selection settings. Period aggregates reflect Gong’s definitions and requested buckets; they do not establish work quality or employee performance. This stream supplies no reliable deletion signal.

User Aggregate Activity

Developer identifier: activity_aggregate_by_period.userAggregateActivityUser Aggregate Activity. Aggregated activity counts per time period. It preserves the nested context needed to interpret the parent activity aggregate by period.

Enables: Measure each returned user aggregate activity in activity_aggregate_by_period.userAggregateActivity at its element and time grain; compare values only when Gong API reports the same unit and aggregation.
Interpretation: Gong API returns user aggregate activity as an array of user aggregate activity entries on each activity aggregate by period; missing, empty, and permission-redacted arrays are not equivalent.

Calls As Host

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsAsHostCalls As Host. Calls as host in period. It supplies the calls as host measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls as host through activity_aggregate_by_period.userAggregateActivity.callsAsHost for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls as host as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Attended

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsAttendedCalls Attended. Calls attended in period. It supplies the calls attended measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls attended through activity_aggregate_by_period.userAggregateActivity.callsAttended for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls attended as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Comments Given

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsCommentsGivenCalls Comments Given. Comments given in period. It supplies the calls comments given measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls comments given through activity_aggregate_by_period.userAggregateActivity.callsCommentsGiven for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls comments given as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Comments Received

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsCommentsReceivedCalls Comments Received. Comments received in period. It supplies the calls comments received measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls comments received through activity_aggregate_by_period.userAggregateActivity.callsCommentsReceived for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls comments received as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Gave Feedback

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsGaveFeedbackCalls Gave Feedback. Calls where the user gave feedback in period. It supplies the calls gave feedback measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls gave feedback through activity_aggregate_by_period.userAggregateActivity.callsGaveFeedback for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls gave feedback as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Marked As Feedback Given

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsMarkedAsFeedbackGivenCalls Marked As Feedback Given. Calls marked as feedback given in period. It supplies the calls marked as feedback given measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls marked as feedback given through activity_aggregate_by_period.userAggregateActivity.callsMarkedAsFeedbackGiven for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls marked as feedback given as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Marked As Feedback Received

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsMarkedAsFeedbackReceivedCalls Marked As Feedback Received. Calls marked as feedback received in period. It supplies the calls marked as feedback received measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls marked as feedback received through activity_aggregate_by_period.userAggregateActivity.callsMarkedAsFeedbackReceived for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls marked as feedback received as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Received Feedback

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsReceivedFeedbackCalls Received Feedback. Calls where the user received feedback in period. It supplies the calls received feedback measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls received feedback through activity_aggregate_by_period.userAggregateActivity.callsReceivedFeedback for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls received feedback as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Requested Feedback

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsRequestedFeedbackCalls Requested Feedback. Calls where the user requested feedback in period. It supplies the calls requested feedback measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls requested feedback through activity_aggregate_by_period.userAggregateActivity.callsRequestedFeedback for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls requested feedback as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Scorecards Filled

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsScorecardsFilledCalls Scorecards Filled. Scorecards filled in period. It supplies the calls scorecards filled measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls scorecards filled through activity_aggregate_by_period.userAggregateActivity.callsScorecardsFilled for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls scorecards filled as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Scorecards Received

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsScorecardsReceivedCalls Scorecards Received. Scorecards received in period. It supplies the calls scorecards received measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls scorecards received through activity_aggregate_by_period.userAggregateActivity.callsScorecardsReceived for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls scorecards received as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Shared Externally

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsSharedExternallyCalls Shared Externally. Calls shared externally in period. It supplies the calls shared externally measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls shared externally through activity_aggregate_by_period.userAggregateActivity.callsSharedExternally for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls shared externally as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Calls Shared Internally

Developer identifier: activity_aggregate_by_period.userAggregateActivity.callsSharedInternallyCalls Shared Internally. Calls shared internally in period. It supplies the calls shared internally measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure calls shared internally through activity_aggregate_by_period.userAggregateActivity.callsSharedInternally for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports calls shared internally as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

From Date

Developer identifier: activity_aggregate_by_period.userAggregateActivity.fromDateFrom Date. Start of the period in ISO-8601. It anchors the activity aggregate by period on the provider’s reported timeline.

Enables: Match repeated user aggregate activity entries on from date in activity_aggregate_by_period.userAggregateActivity.fromDate; collapse only entries that share this declared transform key.
Interpretation: Gong API reports from date as a timestamp on each user aggregate activity; timezone and precision follow this API field, and absence is not an inferred event time. The connector explicitly marks this field as a transform deduplication key.

Others Calls Listened To

Developer identifier: activity_aggregate_by_period.userAggregateActivity.othersCallsListenedToOthers Calls Listened To. Others’ calls listened to in period. It supplies the others calls listened to measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure others calls listened to through activity_aggregate_by_period.userAggregateActivity.othersCallsListenedTo for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports others calls listened to as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

Own Calls Listened To

Developer identifier: activity_aggregate_by_period.userAggregateActivity.ownCallsListenedToOwn Calls Listened To. Own calls listened to in period. It supplies the own calls listened to measure for the user aggregate activity at the provider’s declared unit and grain.

Enables: Measure own calls listened to through activity_aggregate_by_period.userAggregateActivity.ownCallsListenedTo for each user aggregate activity and compare only values with the same unit and record grain.
Interpretation: Gong API reports own calls listened to as a measure on each user aggregate activity; compare only records with the same unit and aggregation grain.

To Date

Developer identifier: activity_aggregate_by_period.userAggregateActivity.toDateTo Date. End of the period in ISO-8601. It anchors the activity aggregate by period on the provider’s reported timeline.

Enables: Order Activity Aggregate By Period by to date in activity_aggregate_by_period.userAggregateActivity.toDate and isolate records inside an exact provider reporting window.
Interpretation: Gong API reports to date as a timestamp on each user aggregate activity; timezone and precision follow this API field, and absence is not an inferred event time.

User Email Address

Developer identifier: activity_aggregate_by_period.userEmailAddressUser Email Address. Email address of the user. It supplies the provider-reported address or location facet for the activity aggregate by period, not a residency determination.

Enables: Attribute each activity aggregate by period to a person or account by the exact user email address in activity_aggregate_by_period.userEmailAddress; identify addresses that do not match the Gong API directory.
Interpretation: Gong API reports user email address as an address on each activity aggregate by period; aliases, casing, and unverified addresses can prevent a one-to-one person match.

User ID

Developer identifier: activity_aggregate_by_period.userIdUser ID. User ID. It provides the reference needed to connect the activity aggregate by period to the corresponding provider object.

Enables: Match repeated activity aggregate by period entries on user ID in activity_aggregate_by_period.userId; collapse only entries that share this declared transform key.
Interpretation: Gong API reports user ID as an identifier in its user namespace; it is not a universal identity outside Gong API. The connector explicitly marks this field as a transform deduplication key.

Answered Scorecards

Developer identifier: answered_scorecardsAnswered Scorecards. Retrieve answered/completed scorecards for calls within a date range. Returns scorecard responses with scores, answers, and reviewer information.

Enables: Match provider-entered scorecard answers to calls, questions, reviewers, and completion times.
Scope: Reads the records selected by Gong API’s /{apiVersion}/stats/activity/scorecards operation as an event stream using incremental synchronization. Visibility follows the Gong API credential, workspace access, and the endpoint’s content-selection settings. Answers, scores, and reviewer context are entered or calculated in Gong and must remain within their scorecard and call context. This stream supplies no reliable deletion signal.

Answered Scorecard ID

Developer identifier: answered_scorecards.answeredScorecardIdAnswered Scorecard ID. Unique identifier. It provides the reference needed to connect the answered scorecard to the corresponding provider object.

Enables: Match repeated answered scorecard entries on answered scorecard ID in answered_scorecards.answeredScorecardId; collapse only entries that share this declared transform key.
Interpretation: Gong API reports answered scorecard ID as an identifier in its answered scorecard namespace; it is not a universal identity outside Gong API. The connector explicitly marks this field as a transform deduplication key.

Answers

Developer identifier: answered_scorecards.answersAnswers. Answers given for each scorecard question. It preserves the nested context needed to interpret the parent answered scorecard.

Enables: Search the returned answers content in answered_scorecards.answers while preserving element order and attribution to the parent answered scorecard.
Interpretation: Gong API returns answers as ordered content or provider-generated content metadata on each answered scorecard; truncation, omission, and inaccessible source media can limit completeness.

Answer Text

Developer identifier: answered_scorecards.answers.answerTextAnswer Text. Free-text answer or numeric score as text. Nullable. It defines the content surface available for this answered scorecard.

Enables: Locate answer records by answer text in answered_scorecards.answers.answerText; attribute each text match to its parent answered scorecard and, when present, its reported author.
Interpretation: Gong supplies this call content; provider-generated excerpts or summaries may omit context and are not Parable-authored assessments.

Is Overall

Developer identifier: answered_scorecards.answers.isOverallIs Overall. The provider-reported is overall for each answer in Answered Scorecards. It distinguishes the provider-defined is overall state or classification for the answer.

Enables: Filter Answered Scorecards by whether is overall in answered_scorecards.answers.isOverall; count true, false, and missing results separately.
Interpretation: Gong API reports is overall as a boolean on each answer; a missing field is unknown, not false.

Not Applicable

Developer identifier: answered_scorecards.answers.notApplicableNot Applicable. Whether the reviewer marked the question not applicable. It distinguishes the provider-defined not applicable state or classification for the answer.

Enables: Filter Answered Scorecards by whether the reviewer marked the question not applicable in answered_scorecards.answers.notApplicable; count true, false, and missing results separately.
Interpretation: Gong API reports the reviewer marked the question not applicable as a boolean on each answer; a missing field is unknown, not false.

Question ID

Developer identifier: answered_scorecards.answers.questionIdQuestion ID. The provider-reported question ID for each answer in Answered Scorecards. It provides the reference needed to connect the answered scorecard to the corresponding provider object.

Enables: Match repeated answer entries on question ID in answered_scorecards.answers.questionId; collapse only entries that share this declared transform key.
Interpretation: Gong API reports question ID as an identifier in its question namespace; it is not a universal identity outside Gong API. The connector explicitly marks this field as a transform deduplication key.

Question Revision ID

Developer identifier: answered_scorecards.answers.questionRevisionIdQuestion Revision ID. The provider-reported question revision ID for each answer in Answered Scorecards. It provides the reference needed to connect the answered scorecard to the corresponding provider object.

Enables: Connect each answer in Answered Scorecards to the referenced question revision through answered_scorecards.answers.questionRevisionId; flag question revision ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports question revision ID as an identifier in its question revision namespace; it is not a universal identity outside Gong API.

Score

Developer identifier: answered_scorecards.answers.scoreScore. Numeric score for the question, if applicable. It supplies the returned score text needed to understand the answer in context.

Enables: Search the returned score text in answered_scorecards.answers.score and attribute each match to its parent answered scorecard and reported author when available.
Interpretation: Gong API supplies score as returned text on each answer; truncation, formatting, and access boundaries can limit completeness.

Selected Options

Developer identifier: answered_scorecards.answers.selectedOptionsSelected Options. Selected answer options for choice questions. Nullable. It preserves the nested context needed to interpret the parent answered scorecard.

Enables: Compare the exact Gong API-configured selected options set in answered_scorecards.answers.selectedOptions for each answer; preserve provider labels and unknown entries.
Interpretation: Gong API returns selected options as an array of selected option value entries on each answer; missing, empty, and permission-redacted arrays are not equivalent.

Call ID

Developer identifier: answered_scorecards.callIdCall ID. Call ID that was scored. It provides the reference needed to connect the answered scorecard to the corresponding provider object.

Enables: Connect each answered scorecard in Answered Scorecards to the referenced call through answered_scorecards.callId; flag call ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports call ID as an identifier in its call namespace; it is not a universal identity outside Gong API.

Call Start Time

Developer identifier: answered_scorecards.callStartTimeCall Start Time. Call start time. It anchors the answered scorecard on the provider’s reported timeline.

Enables: Filter Answered Scorecards by call start time in answered_scorecards.callStartTime; pair that boundary with the corresponding end before measuring elapsed time.
Interpretation: Gong API reports call start time as a timestamp on each answered scorecard; timezone and precision follow this API field, and absence is not an inferred event time.

Editor User ID

Developer identifier: answered_scorecards.editorUserIdEditor User ID. User who last edited the answered scorecard. Nullable. It provides the reference needed to connect the answered scorecard to the corresponding provider object.

Enables: Connect each answered scorecard in Answered Scorecards to the referenced editor user through answered_scorecards.editorUserId; flag editor user ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports editor user ID as an identifier in its editor user namespace; it is not a universal identity outside Gong API.

Reviewed User ID

Developer identifier: answered_scorecards.reviewedUserIdReviewed User ID. User being reviewed. It provides the reference needed to connect the answered scorecard to the corresponding provider object.

Enables: Connect each answered scorecard in Answered Scorecards to the referenced reviewed user through answered_scorecards.reviewedUserId; flag reviewed user ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports reviewed user ID as an identifier in its reviewed user namespace; it is not a universal identity outside Gong API.

Reviewer User ID

Developer identifier: answered_scorecards.reviewerUserIdReviewer User ID. Reviewer user ID. Null when the scorecard was filled automatically. It provides the reference needed to connect the answered scorecard to the corresponding provider object.

Enables: Connect each answered scorecard in Answered Scorecards to the referenced reviewer user through answered_scorecards.reviewerUserId; flag reviewer user ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports reviewer user ID as an identifier in its reviewer user namespace; it is not a universal identity outside Gong API.

Review Method

Developer identifier: answered_scorecards.reviewMethodReview Method. How the scorecard was completed (e.g., MANUAL, AUTOMATIC). It distinguishes the provider-defined review method state or classification for the answered scorecard.

Enables: Filter Answered Scorecards by the exact Gong API-defined review method in answered_scorecards.reviewMethod and preserve unknown values as distinct categories.
Interpretation: Gong API supplies review method from its own taxonomy on each answered scorecard; preserve unknown and newly introduced labels.

Review Time

Developer identifier: answered_scorecards.reviewTimeReview Time. Review completion time. It is needed to place the answered scorecard on the provider timeline at the field’s stated precision.

Enables: Order Answered Scorecards by the provider-reported instant in answered_scorecards.reviewTime and isolate records inside the same time window and precision.
Interpretation: Gong API reports review time as a time value for each answered scorecard; format, timezone, precision, and absolute-versus-relative meaning follow this field’s contract. A connector directive uses this field to order records for latest-state or incremental processing. The schema designates this field as the event timestamp.

Scorecard ID

Developer identifier: answered_scorecards.scorecardIdScorecard ID. Scorecard template ID. It provides the reference needed to connect the answered scorecard to the corresponding provider object.

Enables: Connect each answered scorecard in Answered Scorecards to the referenced scorecard through answered_scorecards.scorecardId; flag scorecard ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports scorecard ID as an identifier in its scorecard namespace; it is not a universal identity outside Gong API.

Scorecard Name

Developer identifier: answered_scorecards.scorecardNameScorecard Name. Scorecard name. It gives the answered scorecard a human-readable provider label while its identifier remains the stable reference.

Enables: Label each answered scorecard with scorecard name from answered_scorecards.scorecardName; distinguish records that share that display name but have different Gong API identifiers.
Interpretation: Gong API reports scorecard name as display text for each answered scorecard; names are mutable and are not stable identities.

Visibility Type

Developer identifier: answered_scorecards.visibilityTypeVisibility Type. Visibility setting. It distinguishes the provider-defined visibility type state or classification for the answered scorecard.

Enables: Segment answered scorecard entries in Answered Scorecards by visibility type in answered_scorecards.visibilityType; compare counts only within the same Gong API taxonomy.
Interpretation: Gong API reports visibility type as a label from its own taxonomy on each answered scorecard; preserve unknown labels rather than mapping them by assumption.

Call Transcripts

Developer identifier: call_transcriptsCall Transcripts. Retrieve call transcripts from Gong. Returns transcript segments with speaker identification, timestamps, and text for each call. Gong does not expose a per-transcript modified timestamp, so the plan’s request window supplies fromDateTime and toDateTime.

Enables: Locate transcript sentences by call, speaker, and offset for conversation review.
Scope: Reads the records selected by Gong API’s /{apiVersion}/calls/transcript operation as an event stream using incremental synchronization. Visibility follows the Gong API credential, workspace access, and the endpoint’s content-selection settings. The stream contains provider transcript text with speaker labels and offsets, not recording audio or video. This stream supplies no reliable deletion signal.

Call ID

Developer identifier: call_transcripts.callIdCall ID. Unique identifier of the call. It provides the reference needed to connect the call transcript to the corresponding provider object.

Enables: Match repeated call transcript entries on call ID in call_transcripts.callId; collapse only entries that share this declared transform key.
Interpretation: Gong API reports call ID as an identifier in its call namespace; it is not a universal identity outside Gong API. The connector explicitly marks this field as a transform deduplication key.

Transcript

Developer identifier: call_transcripts.transcriptTranscript. Array of transcript segments. It preserves the nested context needed to interpret the parent call transcript.

Enables: Reconstruct the returned transcript in call_transcripts.transcript by preserving sentence order, speaker attribution, and call-relative offsets for the parent call transcript.
Interpretation: Gong API returns transcript as ordered content or provider-generated content metadata on each call transcript; truncation, omission, and inaccessible source media can limit completeness.

Sentences

Developer identifier: call_transcripts.transcript.sentencesSentences. The provider-returned sentences collection nested under the transcript structure for each call transcript; needed to retain every element with its parent relationship.

Enables: Reconstruct the returned transcript in call_transcripts.transcript.sentences by preserving sentence order, speaker attribution, and call-relative offsets for the parent call transcript.
Interpretation: Gong API returns sentences as ordered content or provider-generated content metadata on each transcript; truncation, omission, and inaccessible source media can limit completeness.

End

Developer identifier: call_transcripts.transcript.sentences.endEnd. End time in ms. It supplies the end measure for the sentence at the provider’s declared unit and grain.

Enables: Order call excerpts by the numeric end in call_transcripts.transcript.sentences.end; pair start and end positions before calculating a span.
Interpretation: Gong API reports end as milliseconds on each sentence; compare only records with the same unit and aggregation grain. Gong returns a call-relative position in the stated unit; it is not a wall-clock timestamp.

Start

Developer identifier: call_transcripts.transcript.sentences.startStart. Start time in ms. It supplies the start measure for the sentence at the provider’s declared unit and grain.

Enables: Order call excerpts by the numeric start in call_transcripts.transcript.sentences.start; pair start and end positions before calculating a span.
Interpretation: Gong API reports start as milliseconds on each sentence; compare only records with the same unit and aggregation grain. Gong returns a call-relative position in the stated unit; it is not a wall-clock timestamp.

Text

Developer identifier: call_transcripts.transcript.sentences.textText. Transcribed text. It defines the content surface available for this call transcript.

Enables: Locate sentence records by text in call_transcripts.transcript.sentences.text; attribute each text match to its parent call transcript and, when present, its reported author.
Interpretation: This is provider transcript data, not the source audio or video, and speaker attribution can reflect provider labeling limits.

Speaker ID

Developer identifier: call_transcripts.transcript.speakerIdSpeaker ID. Speaker ID. It provides the reference needed to connect the call transcript to the corresponding provider object.

Enables: Match repeated transcript entries on speaker ID in call_transcripts.transcript.speakerId; collapse only entries that share this declared transform key.
Interpretation: Gong API reports speaker ID as an identifier in its speaker namespace; it is not a universal identity outside Gong API. The connector explicitly marks this field as a transform deduplication key.

Topic

Developer identifier: call_transcripts.transcript.topicTopic. Topic label. It supplies the returned topic text needed to understand the transcript in context.

Enables: Search the returned topic text in call_transcripts.transcript.topic and attribute each match to its parent call transcript and reported author when available.
Interpretation: Gong API supplies topic as returned text on each transcript; truncation, formatting, and access boundaries can limit completeness. Gong API generated or classified this result; it may be incomplete and is not a Parable-authored judgment.

Calls

Developer identifier: callsCalls. List all calls by date range from Gong. Returns basic call metadata including call ID, title, scheduled time, duration, direction, and participants.

Enables: Inventory Gong call metadata by date range and attribute each call to its participants, direction, and scheduled time.
Scope: Reads the records selected by Gong API’s /{apiVersion}/calls operation as an event stream using incremental synchronization. Visibility follows the Gong API credential, workspace access, and the endpoint’s content-selection settings. The stream contains basic call metadata, not transcript text, recordings, or the richer provider-generated content from the extensive-call operation. This stream supplies no reliable deletion signal.

Calendar Event ID

Developer identifier: calls.calendarEventIdCalendar Event ID. Associated calendar event ID. It provides the reference needed to connect the call to the corresponding provider object.

Enables: Connect each call in Calls to the referenced calendar event through calls.calendarEventId; flag calendar event ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports calendar event ID as an identifier in its calendar event namespace; it is not a universal identity outside Gong API.

Client Unique ID

Developer identifier: calls.clientUniqueIdClient Unique ID. Client-provided unique identifier. It provides the reference needed to connect the call to the corresponding provider object.

Enables: Connect each call in Calls to the referenced client unique through calls.clientUniqueId; flag client unique ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports client unique ID as an identifier in its client unique namespace; it is not a universal identity outside Gong API.

Custom Data

Developer identifier: calls.customDataCustom Data. Custom data associated with the call. It must be interpreted with the enclosing provider field name, type, or custom schema for the call.

Enables: Interpret calls.customData with the enclosing custom field name, declared type, and provider schema; compare only records that share that contract.
Interpretation: Gong API reports custom data under the enclosing custom or typed field contract on each call; compare it only with values from the same provider key and type.

Direction

Developer identifier: calls.directionDirection. Direction of the call (Inbound or Outbound). It distinguishes the provider-defined direction state or classification for the call.

Enables: Filter Calls by the exact Gong API-defined direction in calls.direction and preserve unknown values as distinct categories.
Interpretation: Gong API supplies direction from its own taxonomy on each call; preserve unknown and newly introduced labels.

Duration

Developer identifier: calls.durationDuration. Duration of the call in seconds. It supplies the duration measure for the call at the provider’s declared unit and grain.

Enables: Measure duration through calls.duration for each call and compare only values with the same unit and record grain.
Interpretation: Gong API reports duration as a measure on each call; compare only records with the same unit and aggregation grain.

Developer identifier: calls.idID. Unique identifier for the call. It provides the reference needed to connect the call to the corresponding provider object.

Enables: Match repeated call entries on ID in calls.id; collapse only entries that share this declared transform key.
Interpretation: Gong API reports ID as an identifier in its call namespace; it is not a universal identity outside Gong API. The connector explicitly marks this field as a transform deduplication key.

Is Private

Developer identifier: calls.isPrivateIs Private. Whether the call is private. It distinguishes the provider-defined is private state or classification for the call.

Enables: Filter Calls by whether the call is private in calls.isPrivate; count true, false, and missing results separately.
Interpretation: Gong API reports the call is private as a boolean on each call; a missing field is unknown, not false.

Language

Developer identifier: calls.languageLanguage. Language of the call. It supplies the language profile facet used to reconcile or attribute the call.

Enables: Reconcile the call’s language in calls.language with its provider profile or directory identity; confirm ambiguous matches with the stable provider ID.
Interpretation: Gong API reports language as a mutable profile or directory attribute on each call; it may be absent, shared, or non-unique.

Media

Developer identifier: calls.mediaMedia. Media type of the call. It distinguishes the provider-defined media state or classification for the call.

Enables: Filter Calls by the exact Gong API-defined media in calls.media and preserve unknown values as distinct categories.
Interpretation: Gong API supplies media from its own taxonomy on each call; preserve unknown and newly introduced labels.

Meeting URL

Developer identifier: calls.meetingUrlMeeting URL. Meeting URL for the call. It locates the provider resource or path associated with the call.

Enables: Associate each call with the resource identified by meeting URL in calls.meetingUrl; verify the link resolves to the expected Gong API object.
Interpretation: Gong API reports meeting URL as a resource locator for each call; access still depends on viewer permissions and the URL may expire or change.

Primary User ID

Developer identifier: calls.primaryUserIdPrimary User ID. ID of the primary Gong user associated with the call. It provides the reference needed to connect the call to the corresponding provider object.

Enables: Connect each call in Calls to the referenced primary user through calls.primaryUserId; flag primary user ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports primary user ID as an identifier in its primary user namespace; it is not a universal identity outside Gong API.

Purpose

Developer identifier: calls.purposePurpose. Purpose of the call. It supplies the returned purpose text needed to understand the call in context.

Enables: Search the returned purpose text in calls.purpose and attribute each match to its parent call and reported author when available.
Interpretation: Gong API supplies purpose as returned text on each call; truncation, formatting, and access boundaries can limit completeness.

Scheduled

Developer identifier: calls.scheduledScheduled. Scheduled time of the call in ISO-8601 format. It is needed to place the call on the provider timeline at the field’s stated precision.

Enables: Order Calls by the provider-reported instant in calls.scheduled and isolate records inside the same time window and precision.
Interpretation: Gong API reports scheduled as a time value for each call; format, timezone, precision, and absolute-versus-relative meaning follow this field’s contract.

Scope

Developer identifier: calls.scopeScope. Scope of the call (Internal/External). It distinguishes the provider-defined scope state or classification for the call.

Enables: Filter Calls by the exact Gong API-defined scope in calls.scope and preserve unknown values as distinct categories.
Interpretation: Gong API supplies scope from its own taxonomy on each call; preserve unknown and newly introduced labels.

Sdr Disposition

Developer identifier: calls.sdrDispositionSdr Disposition. Sales-development representative disposition tag. It distinguishes the provider-defined sdr disposition state or classification for the call.

Enables: Filter Calls by the exact Gong API-defined sdr disposition in calls.sdrDisposition and preserve unknown values as distinct categories.
Interpretation: Gong API supplies sdr disposition from its own taxonomy on each call; preserve unknown and newly introduced labels.

Started

Developer identifier: calls.startedStarted. Actual start time of the call in ISO-8601 format. It anchors the call on the provider’s reported timeline.

Enables: Order Calls by started in calls.started and isolate records inside an exact provider reporting window.
Interpretation: Gong API reports started as a timestamp on each call; timezone and precision follow this API field, and absence is not an inferred event time. A connector directive uses this field to order records for latest-state or incremental processing. The schema designates this field as the event timestamp.

System

Developer identifier: calls.systemSystem. Telephony or conferencing system used. It distinguishes the provider-defined system state or classification for the call.

Enables: Filter Calls by the exact Gong API-defined system in calls.system and preserve unknown values as distinct categories.
Interpretation: Gong API supplies system from its own taxonomy on each call; preserve unknown and newly introduced labels.

Title

Developer identifier: calls.titleTitle. Title or subject of the call. It supplies the returned title text needed to understand the call in context.

Enables: Label each call with title from calls.title; distinguish records that share that display name but have different Gong API identifiers.
Interpretation: Gong API reports title as display text for each call; names are mutable and are not stable identities.

URL

Developer identifier: calls.urlURL. URL to view the call in Gong. It locates the provider resource or path associated with the call.

Enables: Associate each call with the resource identified by URL in calls.url; verify the link resolves to the expected Gong API object.
Interpretation: Gong API reports URL as a resource locator for each call; access still depends on viewer permissions and the URL may expire or change.

Workspace ID

Developer identifier: calls.workspaceIdWorkspace ID. Workspace the call belongs to. It provides the reference needed to connect the call to the corresponding provider object.

Enables: Connect each call in Calls to the referenced workspace through calls.workspaceId; flag workspace ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports workspace ID as an identifier in its workspace namespace; it is not a universal identity outside Gong API.

Calls Extensive

Developer identifier: calls_extensiveCalls Extensive. Retrieve detailed/extensive call data from Gong including topics, trackers, parties, key points, highlights, and other rich content fields. Uses POST with filter and content selector.

Enables: Review Gong-provided topics, trackers, highlights, comments, and interaction measures in the context of each call.
Scope: Reads the records selected by Gong API’s /{apiVersion}/calls/extensive operation as an event stream using incremental synchronization. Visibility follows the Gong API credential, workspace access, and the endpoint’s content-selection settings. Gong supplies topics, trackers, highlights, summaries, and classifications; they may be incomplete and are not independent Parable assessments. Transcript text and recording bytes are not part of this operation. This stream supplies no reliable deletion signal.

Collaboration

Developer identifier: calls_extensive.collaborationCollaboration. Collaboration data (public comments) on the call. It preserves the nested context needed to interpret the parent extensive call.

Enables: Attribute collaboration in calls_extensive.collaboration to the parent extensive call; identify parent records where that nested collaboration object is absent.
Interpretation: Gong API reports collaboration as a nested object on each extensive call; optional children may be absent from a valid response.

Public Comments

Developer identifier: calls_extensive.collaboration.publicCommentsPublic Comments. The provider-returned public comments collection nested under the collaboration structure for each extensive call; needed to retain every element with its parent relationship.

Enables: Search the returned public comments content in calls_extensive.collaboration.publicComments while preserving element order and attribution to the parent extensive call.
Interpretation: Gong API returns public comments as ordered content or provider-generated content metadata on each collaboration; truncation, omission, and inaccessible source media can limit completeness.

Audio End Time

Developer identifier: calls_extensive.collaboration.publicComments.audioEndTimeAudio End Time. The provider-reported audio end time for each public comment in extensive call. It supplies the audio end time measure for the public comment at the provider’s declared unit and grain.

Enables: Order call excerpts by the numeric audio end time in calls_extensive.collaboration.publicComments.audioEndTime; pair start and end positions before calculating a span.
Interpretation: Gong API reports audio end time as a number at the parent record’s grain on each public comment; compare only records with the same unit and aggregation grain. Gong returns a numeric call-relative position here, but this declaration does not state a unit; do not interpret it as a wall-clock timestamp.

Audio Start Time

Developer identifier: calls_extensive.collaboration.publicComments.audioStartTimeAudio Start Time. The provider-reported audio start time for each public comment in extensive call. It supplies the audio start time measure for the public comment at the provider’s declared unit and grain.

Enables: Order call excerpts by the numeric audio start time in calls_extensive.collaboration.publicComments.audioStartTime; pair start and end positions before calculating a span.
Interpretation: Gong API reports audio start time as a number at the parent record’s grain on each public comment; compare only records with the same unit and aggregation grain. Gong returns a numeric call-relative position here, but this declaration does not state a unit; do not interpret it as a wall-clock timestamp.

Comment

Developer identifier: calls_extensive.collaboration.publicComments.commentComment. The provider-reported comment for each public comment in extensive call. It defines the content surface available for this extensive call.

Enables: Locate public comment records by comment in calls_extensive.collaboration.publicComments.comment; attribute each text match to its parent extensive call and, when present, its reported author.
Interpretation: Gong supplies this call content; provider-generated excerpts or summaries may omit context and are not Parable-authored assessments.

Commenter User ID

Developer identifier: calls_extensive.collaboration.publicComments.commenterUserIdCommenter User ID. The provider-reported commenter user ID for each public comment in extensive call. It provides the reference needed to connect the extensive call to the corresponding provider object.

Enables: Connect each public comment in extensive call to the referenced commenter user through calls_extensive.collaboration.publicComments.commenterUserId; flag commenter user ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports commenter user ID as an identifier in its commenter user namespace; it is not a universal identity outside Gong API.

During Call

Developer identifier: calls_extensive.collaboration.publicComments.duringCallDuring Call. The provider-reported during call for each public comment in extensive call. It distinguishes the provider-defined during call state or classification for the public comment.

Enables: Filter extensive call by whether during call in calls_extensive.collaboration.publicComments.duringCall; count true, false, and missing results separately.
Interpretation: Gong API reports during call as a boolean on each public comment; a missing field is unknown, not false.

Developer identifier: calls_extensive.collaboration.publicComments.idID. The provider-reported ID for each public comment in extensive call. It provides the reference needed to connect the extensive call to the corresponding provider object.

Enables: Connect each public comment in extensive call to the referenced public comment through calls_extensive.collaboration.publicComments.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Gong API reports ID as an identifier in its public comment namespace; it is not a universal identity outside Gong API.

In Reply To

Developer identifier: calls_extensive.collaboration.publicComments.inReplyToIn Reply To. The provider-reported in reply to for each public comment in extensive call. It identifies the related provider object that gives the public comment its parent, owner, or container context.

Enables: Connect each public comment to the related in reply to in calls_extensive.collaboration.publicComments.inReplyTo and verify that the referenced provider object resolves in the expected parent or container.
Interpretation: Gong API reports in reply to as relationship context on each public comment; resolve it in the named provider namespace rather than by display text alone.

Posted

Developer identifier: calls_extensive.collaboration.publicComments.postedPosted. ISO-8601 timestamp. It is needed to place the public comment on the provider timeline at the field’s stated precision.

Enables: Order Calls Extensive by the provider-reported instant in calls_extensive.collaboration.publicComments.posted and isolate records inside the same time window and precision.
Interpretation: Gong API reports posted as a time value for each public comment; format, timezone, precision, and absolute-versus-relative meaning follow this field’s contract.

Content

Developer identifier: calls_extensive.contentContent. Rich content for the call (topics, trackers, brief, highlights, etc.). It preserves the nested context needed to interpret the parent extensive call.

Enables: Attribute content in calls_extensive.content to the parent extensive call; identify parent records where that nested content object is absent.
Interpretation: Gong API reports content as a nested object on each extensive call; optional children may be absent from a valid response. Gong API generated or classified this result; it may be incomplete and is not a Parable-authored judgment.

Brief

Developer identifier: calls_extensive.content.briefBrief. AI-generated brief summary of the call. It defines the content surface available for this extensive call.

Enables: Locate content records by brief in calls_extensive.content.brief; attribute each text match to its parent extensive call and, when present, its reported author.
Interpretation: Gong supplies this call content; provider-generated excerpts or summaries may omit context and are not Parable-authored assessments. Gong API generated or classified this result; it may be incomplete and is not a Parable-authored judgment.

Call Outcome

Developer identifier: calls_extensive.content.callOutcomeCall Outcome. The structured call outcome details attached to each content in extensive call. It preserves the nested context needed to interpret the parent extensive call.

Enables: Attribute call outcome in calls_extensive.content.callOutcome to the parent extensive call; identify parent records where that nested call outcome object is absent.
Interpretation: Gong API reports call outcome as a nested object on each content; optional children may be absent from a valid response.

Gong

Error	Meaning	Solution
`401 Unauthorized`	Bad Access Key or Secret	Re-generate the key from the API settings page
`401` after a working period	Key expired	Generate a fresh key; Gong rotates keys periodically
`403 Forbidden` on a specific endpoint	Missing API scope	Ask the Gong admin to enable the scope for that data category
`429 Too Many Requests`	Rate limit	Parable backs off using `Retry-After`
Connection shows a permissions error right after saving the key	Parable checks the key with `GET /v2/users` on the connection’s API Base URL; Gong answered `403`	Enable the `api:users:read` scope for the key, and if the Gong workspace restricts API access by IP, allow Parable’s addresses
Connection shows a configuration error right after saving the key	The same check got a response that is neither success nor `401`/`403`, usually because API Base URL is not a Gong API host	Set API Base URL to the value in Gong’s API settings, for example `https://us-12345.api.gong.io`, not the `app.gong.io` web address
Empty data on `calls`	No calls in range	Calls need `fromDateTime` in the last 90 days per request

Common Issues

Cannot find the API page

The Ecosystem → API menu appears only for users with the Technical Administrator role.

Permission Profiles returns 401 / 403

Requires api:permission-profile:read on the key. Some tiers need Gong support to enable the scope.Gong API docs — Endpoint reference (requires login)API access guide — Customer-facing setup guide

Gong (OAuth)

Error	Meaning	Solution
`401 Unauthorized`	Invalid client credentials	Verify Client ID and Client Secret on the OAuth authorization screen
`403 Forbidden`	Missing OAuth scope	Enable the scope on the OAuth application
Authorization redirect fails	Redirect URI mismatch	Copy the redirect URI from Parable (must include your workspace subdomain, e.g. `{tenant-name}.parable.work`) and add it exactly to your Gong OAuth app
Authorized in Parable but sync fails	Wrong API Base URL or token issue	Confirm API Base URL under Connection Settings matches Gong (default or regional); click Re-authorize with OAuth and confirm validation succeeded
`429 Too Many Requests`	Rate limit	Parable backs off using `Retry-After`

Gong API docs — Endpoint reference (requires login)API access guide — Customer-facing setup guide

​Gong

​Conversations & CRM

​People & workspace

​Gong (OAuth)

​Conversations & CRM

​People & workspace

​Gong (OAuth)

​Data streams

​Gong

​What You’ll Need

​Step 1: Open Gong API settings

​Step 2: Enable required API scopes

​Step 3: Create API credentials

​Step 4: Enter values in the form

​Gong (OAuth)

​What You’ll Need

​Step 1: Create a Gong OAuth application

​Step 2: Enable required API scopes

​Step 3: Create the connection in Parable

​Step 4: Register the redirect URI in Gong

​Step 5: Authorize with Parable

​Gong

​Gong (OAuth)

​Gong

​Common Issues

​Cannot find the API page

​Permission Profiles returns 401 / 403

​Gong (OAuth)

Gong

Conversations & CRM

People & workspace

Gong (OAuth)

Conversations & CRM

People & workspace

Gong (OAuth)

Data streams

Gong

What You’ll Need

Step 1: Open Gong API settings

Step 2: Enable required API scopes

Step 3: Create API credentials

Step 4: Enter values in the form

Gong (OAuth)

What You’ll Need

Step 1: Create a Gong OAuth application

Step 2: Enable required API scopes

Step 3: Create the connection in Parable

Step 4: Register the redirect URI in Gong

Step 5: Authorize with Parable

Gong

Gong (OAuth)

Gong

Common Issues

Cannot find the API page

Permission Profiles returns 401 / 403

Gong (OAuth)