Skip to main content

Gong Data Source

The Gong connector enables you to ingest revenue intelligence data from Gong, including call records, transcripts, user information, scorecards, trackers, workspace data, and logs. This connector is particularly useful for applications that need to extract sales performance data, analyze customer interactions, monitor revenue intelligence metrics, or integrate Gong data into analytics systems. Follow the instructions below to create a new data flow that ingests data from a Gong source in Nexla.
gong_api.png

Gong

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Gong connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Gong instance, and click Next; or, create a new Gong credential for use in this flow.

  3. In Nexla, Gong data sources can be created using pre-built endpoint templates, which expedite source setup for common Gong endpoints. Each template is designed specifically for the corresponding Gong endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Gong sources can also be configured manually, allowing you to ingest data from Gong endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Gong endpoints. Each template is designed specifically for the corresponding Gong endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    Calls

    This endpoint retrieves call records from Gong, including call metadata, participants, duration, and other call-related information. Use this endpoint when you need to extract call data for sales performance analysis, call analytics, or integration with other systems.

    • Optionally, enter a start date and time in the Start Date and Time field to specify the beginning of the time range for call retrieval. The date should be in ISO-8601 format (yyyy-MM-ddTHH:mm:ssZ), such as 2024-01-01T00:00:00Z. If left empty, the default value {now-7} will be used, which retrieves calls from 7 days ago to the current time.
    • Optionally, enter an end date and time in the End Date and Time field to specify the end of the time range for call retrieval. The date should be in ISO-8601 format (yyyy-MM-ddTHH:mm:ssZ), such as 2024-01-08T23:59:59Z. If left empty, the default value {now} will be used, which sets the end time to the current time.

    This endpoint uses pagination to handle large datasets efficiently. The endpoint automatically fetches additional pages using cursor-based pagination, ensuring all call records within the specified time range are retrieved. For more information about the Calls endpoint, refer to the Gong API Documentation.

    Call Transcripts

    This endpoint retrieves call transcript data from Gong, including the full text transcription of calls. Use this endpoint when you need to extract call transcripts for text analysis, conversation intelligence, or natural language processing applications.

    • Optionally, enter a start date and time in the Start Date and Time field to specify the beginning of the time range for transcript retrieval. The date should be in ISO-8601 format (yyyy-MM-ddTHH:mm:ssZ), such as 2024-01-01T00:00:00Z. If left empty, the default value {now-7} will be used, which retrieves transcripts from 7 days ago to the current time.
    • Optionally, enter an end date and time in the End Date and Time field to specify the end of the time range for transcript retrieval. The date should be in ISO-8601 format (yyyy-MM-ddTHH:mm:ssZ), such as 2024-01-08T23:59:59Z. If left empty, the default value {now} will be used, which sets the end time to the current time.

    This endpoint uses POST method with a filter in the request body and supports pagination through cursor-based pagination. The endpoint automatically handles pagination to retrieve all transcripts within the specified time range. For more information about the Call Transcripts endpoint, refer to the Gong API Documentation.

    Users

    This endpoint retrieves user data from Gong, including user profiles, contact information, and user-related metadata. Use this endpoint when you need to extract user information for user management, reporting, or integration with other systems.

    • This endpoint automatically retrieves all users accessible to your Gong workspace. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses pagination to handle large user datasets efficiently, automatically fetching additional pages using cursor-based pagination.

    This endpoint returns user metadata including user names, email addresses, user IDs, and other user-related information. For more information about the Users endpoint, refer to the Gong API Documentation.

    Scorecards

    This endpoint retrieves scorecard data from Gong, including scorecard definitions, criteria, and configuration. Use this endpoint when you need to extract scorecard information for sales coaching, performance tracking, or analytics purposes.

    • This endpoint automatically retrieves all scorecards configured in your Gong workspace. No additional configuration is required beyond selecting this endpoint template.

    Scorecards in Gong are used to evaluate and score sales calls based on predefined criteria. This endpoint returns scorecard metadata including scorecard names, IDs, and configuration details. For more information about the Scorecards endpoint, refer to the Gong API Documentation.

    Trackers

    This endpoint retrieves tracker data from Gong, including tracker definitions and configuration. Use this endpoint when you need to extract tracker information for sales analytics, conversation tracking, or integration with other systems.

    • This endpoint automatically retrieves all trackers configured in your Gong workspace. No additional configuration is required beyond selecting this endpoint template.

    Trackers in Gong are used to identify and track specific topics, keywords, or phrases in sales conversations. This endpoint returns tracker metadata including tracker names, IDs, and configuration details. For more information about the Trackers endpoint, refer to the Gong API Documentation.

    Workspaces

    This endpoint retrieves workspace data from Gong, including workspace information and metadata. Use this endpoint when you need to extract workspace information for multi-workspace management or integration purposes.

    • This endpoint automatically retrieves all workspaces accessible to your Gong account. No additional configuration is required beyond selecting this endpoint template.

    This endpoint returns workspace metadata including workspace names, IDs, and other workspace-related information. For more information about the Workspaces endpoint, refer to the Gong API Documentation.

    Folders

    This endpoint retrieves folder data from Gong's library, including folder information and metadata. Use this endpoint when you need to extract folder information for content organization, library management, or integration with other systems.

    • Enter the Workspace ID in the Workspace ID field. This is Gong's unique identifier for the workspace that will be used to scope folder content retrieval. You can find the Workspace ID by using the "Workspaces" endpoint to retrieve available workspaces and their corresponding IDs.

    This endpoint requires a Workspace ID to scope the folder retrieval to a specific workspace. The Workspace ID is a unique identifier that can be obtained from the "Workspaces" endpoint. For more information about the Folders endpoint, refer to the Gong API Documentation.

    Folder Content

    This endpoint retrieves folder content from Gong's library, including items within a specific folder. Use this endpoint when you need to extract folder content for content analysis, library management, or integration with other systems.

    • Enter the Folder ID in the Folder ID field. This is Gong's unique identifier for the folder for which you want to retrieve content. You can find the Folder ID by first using the "Folders" endpoint to retrieve available folders and their corresponding IDs.

    This endpoint requires a Folder ID to retrieve content from a specific folder. The Folder ID is a unique identifier that can be obtained from the "Folders" endpoint. For more information about the Folder Content endpoint, refer to the Gong API Documentation.

    Logs

    This endpoint retrieves log data from Gong, including access logs, user activity logs, and other system logs. Use this endpoint when you need to extract log data for auditing, compliance, security monitoring, or system analysis purposes.

    • Select the log type from the Log Type field. Available log types include:

      • AccessLog: Logs of API access and authentication events
      • UserActivityLog: Logs of user activities and actions within Gong
      • UserCallPlay: Logs of when users play or access call recordings
      • ExternallySharedCallAccess: Logs of external access to shared calls
      • ExternallySharedCallPlay: Logs of when external users play shared calls
    • Enter a start date and time in the From Date Time field to specify the beginning of the time range for log retrieval. The date should be in ISO-8601 format (yyyy-MM-ddTHH:mm:ssZ), such as 2024-01-01T00:00:00Z. The default value {now-7} will be used if left empty, which retrieves logs from 7 days ago to the current time.
    • Optionally, enter an end date and time in the To Date Time field to specify the end of the time range for log retrieval. The date should be in ISO-8601 format (yyyy-MM-ddTHH:mm:ssZ), such as 2024-01-08T23:59:59Z. If left empty, the default value {now} will be used, which sets the end time to the current time.

    This endpoint uses pagination to handle large log datasets efficiently. The endpoint automatically fetches additional pages using cursor-based pagination, ensuring all log records within the specified time range are retrieved. For more information about the Logs endpoint, refer to the Gong API Documentation.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Gong data sources can be manually configured to ingest data from any valid Gong API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Gong sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Gong API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API
    • POST: For sending data to the API or triggering actions

API Endpoint URL​

  1. Enter the URL of the Gong API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL.

Date/Time Macros (API URL)​

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

Macros are particularly useful for APIs that require date ranges, pagination parameters, or other dynamic values that change between data ingestion runs.

  1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

    • {now} – The current datetime
    • {now-1} – The datetime one time unit before the current datetime
    • {now+1} – The datetime one time unit after the current datetime
    • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

  2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

  3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)​

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.

Lookup-based macros are useful when you need to create API endpoints that reference specific IDs, values, or parameters from other data sources in your Nexla environment.

  1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

  2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data​

Optional

If only a subset of the data that will be returned by API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

For example, when a request call is used to fetch a list of items, the API will typically return an array of records, along with metadata, in the response. By entering the path to the relevant data, you can configure Nexla to treat each element of the returned array as a record.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.data.items[*] to access an array of items within a data object).

    • For responses in XML format, enter the XPath that points to the object/array containing relevant data. XPath uses slash notation (e.g., /response/data/item to access item elements within a data element).

    Path to Data Example:

    If the API response is in JSON format and includes a top-level array named data that contains the relevant data, the path to the response would be entered as $.data[*].

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

Metadata​

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records but isn't part of the main data array.

For example, when a request call is used to fetch a list of items, the API response will typically include an array of records along with metadata such as total count, pagination information, or request timestamps. In this case, if you have specified the path to the relevant data but metadata of interest is located in a different part of the response, you can specify a path to this metadata to include it with each record in the generated Nexset(s).

Metadata paths are particularly useful for preserving API response context like request IDs, timestamps, or summary statistics that apply to all records in the response.

  • To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

    • For responses in JSON format, enter the JSON path to the object or array that contains the metadata, and for responses in XML format, enter the XPath.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Gong data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.