When you configure an export, import, or lookup using the form view designed for the Gong connector, the following API operations are supported:
Note
If your API endpoint isn’t listed here, switch the flow step to HTTP mode and configure the endpoint provided in the Gong API documentation. You can also create a composite endpoint for this application in HTTP mode.
| Resource | API endpoint | Export |
Import |
|---|---|---|---|
| Auditing | Retrieve logs data by type and time range | X |
|
| Calls | Retrieve call data by date range | X |
|
| Add new call |
|
X |
|
| Retrieve data for a specific call | X |
|
|
| Retrieve detailed call data | X |
|
|
| Get manual CRM associations | X |
|
|
| Retrieve transcripts of calls | X |
|
|
| Add call media |
|
X |
|
| Coaching | List all coaching metrics | X |
|
| CRM | Get CRM objects | X |
|
| List schema fields | X |
|
|
| Get generic CRM integration details | X |
|
|
| Get request status | X |
|
|
| Upload CRM objects |
|
X |
|
| Upload object schema |
|
X |
|
| Register a generic CRM integration |
|
X |
|
| Delete a generic CRM integration |
|
X |
|
| Data privacy | Retrieve all references to an email address | X |
|
| Retrieve all references to a phone number | X |
|
|
| Delete the email address, and all associated elements |
|
X |
|
| Delete the phone number, and all associated elements |
|
X |
|
| Digital interactions | Post a digital interaction |
|
X |
| Engage flows | List Gong engage flows | X |
|
| List prospects assigned flows | X |
|
|
| Assign prospects (contacts or leads) to an engage flow |
|
X |
|
| List Gong engage flow folders | X |
|
|
| Submit a bulk assignment of prospects to a flow |
|
X |
|
| Get the results of a bulk assignment of prospects to a flow | X |
|
|
| Unassign flows by CRM prospect ID |
|
X |
|
| Unassign flows by flow instance ID |
|
X |
|
| Get flow details and steps for one or more engage flows | X |
|
|
| Engagement | Report event of a custom action |
|
X |
| Report event of a content share |
|
X |
|
| Report event of a content view |
|
X |
|
| Entities | Ask about an entity | X |
|
| Generate a brief for a CRM entity | X |
|
|
| Integration settings | Integration settings |
|
X |
| Library | List of calls in a specific folder | X |
|
| Retrieve library folders | X |
|
|
| Meetings | Create a new Gong meeting |
|
X |
| Update a Gong meeting |
|
X |
|
| Delete a Gong meeting |
|
X |
|
| Validate Gong meeting integration |
|
X |
|
| Outcomes | List call outcomes | X |
|
| Permissions | List all company permission profiles for a given workspace | X |
|
| Permission profile for a given profile ID | X |
|
|
| List all users attached to a given permission profile | X |
|
|
| Give individual users access to calls |
|
X |
|
| Retrieve users that have specific individual access to calls | X |
|
|
| Remove specific individual users access from calls |
|
X |
|
| Update permission profile |
|
X |
|
| Create permission profile |
|
X |
|
| Settings | Retrieve scorecards details | X |
|
| Retrieve tracker details | X |
|
|
| List all company workspaces | X |
|
|
| Retrieve AI brief settings | X |
|
|
| Stats | Retrieve aggregated activity for defined users by date | X |
|
| Retrieve aggregated activity for defined users by a date range with grouping in time periods | X |
|
|
| Retrieve daily activity for applicable users for a date range | X |
|
|
| Retrieve answered scorecards for applicable reviewed users or scorecards for a date range | X |
|
|
| Retrieve interaction stats for applicable users by date | X |
|
|
| Targets | List target definitions | X |
|
| Upload target assignments |
|
X |
|
| Tasks | List user's tasks | X |
|
| Update task |
|
X |
|
| Users | List all users | X |
|
| Retrieve user | X |
|
|
| Retrieve user settings history | X |
|
|
| List users by filter | X |
|
Available DI objects
The following objects are available when using Gong as a source in Celigo Data Integration (DI).
Primary key: Gong DI endpoints use entity-specific primary keys — callOutcome for call outcomes, id for calls, id for users, and id for workspaces. Each resource has its own identifier field returned by the API.
Note
Gong does not expose hard deletes through its public API — calls and users are managed and deactivated rather than physically removed, and personal-data erasure is handled separately through Gong’s data-privacy (GDPR) endpoints.
Response schemas
Click an object below to view its response fields and delta configuration.
Outcomes — List call outcomes
Response schema:
| Field | Type |
|---|---|
callOutcome |
string (Primary key) |
displayOrder |
number |
connectStatus |
string |
sentiment |
string |
todoAction |
string |
automation |
string |
category |
string |
Settings — List all company workspaces
Response schema:
| Field | Type |
|---|---|
id |
string (Primary key) |
name |
string |
description |
string |
Users — List all users
Response schema:
| Field | Type |
|---|---|
id |
string (Primary key) |
emailAddress |
string |
created |
string |
active |
boolean |
emailAliases |
stringarray |
trustedEmailAddress |
string |
firstName |
string |
lastName |
string |
title |
string |
phoneNumber |
string |
extension |
string |
personalMeetingUrls |
stringarray |
settings |
object |
settings.webConferencesRecorded |
boolean |
settings.preventWebConferenceRecording |
boolean |
settings.telephonyCallsImported |
boolean |
settings.emailsImported |
boolean |
settings.preventEmailImport |
boolean |
settings.nonRecordedMeetingsImported |
boolean |
settings.gongConnectEnabled |
boolean |
managerId |
string |
meetingConsentPageUrl |
string |
spokenLanguages |
objectarray |
spokenLanguages.language |
string |
spokenLanguages.primary |
boolean |
conferencingProviders |
string |