Ellipse Gradient for Header

Gong Integration Guide

Connect Gong conversation and activity data with enterprise systems through REST APIs, selected webhook notifications, and Martini workflows.

Gong integration options at a glance

Gong’s primary integration mechanism is its versioned REST API for users, calls, call transcripts, accounts, contacts, deals, activity, and conversation intelligence data. Gong also provides webhook-style notifications for selected events and processing states, allowing Martini to initiate near-real-time workflows while using the REST API to retrieve complete resources. Larger datasets may use applicable bulk or asynchronous retrieval patterns with pagination, filters, and status polling. Recording and transcript resources may be available through supported API capabilities, subject to permissions and retention. Martini can authenticate with Gong access keys and secrets or supported OAuth 2.0 configurations, then orchestrate synchronization, transformation, reconciliation, and downstream writes.

Integration pointSupported by Gong?Common use casesHow Martini supports it
REST APIsYesRetrieve Users, Calls, Call transcripts, Accounts, Contacts, Deals, activity, and conversation intelligence data. REST APIs are Gong’s principal programmatic integration method.Martini can consume Gong REST APIs from workflows, handle pagination, map response payloads, apply business rules, and write results to applications or databases.
Webhooks / outbound callbacksLimitedReceive notifications for selected Gong events or processing states, such as changes related to call availability or processing.Martini can expose an API or webhook workflow to receive notifications, validate them, retrieve the current Gong resource, and process events idempotently.
Bulk / async / batch APIsLimitedRetrieve larger call and activity datasets using applicable asynchronous jobs, date filters, page or cursor controls, and status polling.Martini can create retrieval jobs where supported, poll status, checkpoint progress, process pages or result windows, and route failures for replay.
File / attachment APIsLimitedRetrieve supported call recordings, transcripts, or related resources where Gong exposes metadata, download URLs, or content through the relevant endpoint.Martini can retrieve and route supported content or URLs, subject to permissions, expiration, retention, and call-processing state.
AuthenticationYesUse Gong access keys and secrets with HTTP Basic Authentication for server-to-server access, or OAuth 2.0 for supported application and delegated-authorization scenarios.Martini can store credentials in environment secrets and apply the appropriate REST authentication configuration without embedding secrets in workflows.
GraphQL APIsNot confirmedNo official Gong GraphQL API was confirmed in the reviewed materials.Martini should use the confirmed Gong REST APIs rather than assuming GraphQL availability.
SOAP APIsNoNo official Gong SOAP API was confirmed.Martini should use Gong REST APIs and supported webhook mechanisms for this integration.
Database / analytics accessNot confirmedNo direct Gong database or general-purpose analytics-database interface was confirmed.Martini can retrieve Gong data through APIs and persist it in a supported downstream SQL database or analytics platform.

How Gong exposes data and business events

Gong REST APIs

Gong REST APIs provide the primary programmatic access to Users, Calls, Call transcripts, Accounts, Contacts, Deals, activity, and conversation intelligence data. Responses are versioned and may be paginated, while permissions determine which resources an integration account can access.

Martini implementation pattern

Martini uses a workflow to authenticate to Gong, retrieve pages or filtered time windows, normalize the response, apply matching and business rules, and write data to a target application or database. The workflow can persist watermarks and source identifiers so incremental runs remain recoverable and idempotent.

Implementation sequence

Authenticate to the Gong REST API
Retrieve the selected resource or time window
Follow pagination or cursor controls
Map Gong fields to the target model
Apply matching, validation, and business rules
Write or upsert the target data and persist the checkpoint

Gong Webhook Notifications

Gong supports webhook-style notifications for selected events and processing states. Coverage is selective rather than universal, and a notification may contain an event summary or identifier rather than a complete Gong object.

Martini implementation pattern

Martini exposes an API or webhook workflow to receive the notification, validates configured authentication or signature information, acknowledges quickly, and retrieves the current Gong resource through the REST API. A scheduled reconciliation workflow can recover missed notifications or cover unsupported events.

Implementation sequence

Receive the Gong webhook notification
Validate the request and event identifier
Acknowledge the notification promptly
Retrieve the current Gong resource through the REST API
Check call or transcript processing state
Process the resource idempotently and record the event checkpoint

Gong Bulk and Asynchronous Retrieval

Gong provides bulk or asynchronous retrieval patterns for applicable call and activity datasets. These operations may involve job creation, status polling, large result sets, date filters, and page or cursor controls, so resource-specific behavior must be validated.

Martini implementation pattern

Martini separates historical or high-volume retrieval from normal incremental workflows. It starts an applicable Gong job, polls its status with controlled delays, processes result windows in batches, records progress, and routes individual failures for replay without restarting the entire import.

Implementation sequence

Define the resource and bounded export window
Create the applicable Gong retrieval job
Poll the job status with controlled retries
Retrieve result pages or output windows
Transform and persist each batch with a checkpoint
Capture failed batches for targeted replay

Gong Recording and Transcript Retrieval

Supported Gong API capabilities may expose call recording or transcript metadata, download URLs, or content. Availability depends on call type, processing state, permissions, retention policies, and the selected endpoint; a universal attachment API is not confirmed.

Martini implementation pattern

Martini receives or discovers a Call, checks whether processing is complete, retrieves the supported transcript or recording representation, and applies organizational rules before copying content or metadata to a downstream system. Expiring URLs and sensitive transcript data require deliberate handling.

Implementation sequence

Identify the Gong Call to process
Check recording or transcript availability
Retrieve the supported metadata, URL, or content
Validate retention and downstream data-sharing rules
Transform or summarize the content as required
Persist the result and record completion or retry state

Common Gong integration patterns

Pattern 1: Sync Gong calls and transcripts to Salesforce

When to use this pattern

Use this pattern when sales teams need Gong conversation activity, transcript-derived information, and account or deal context available alongside Salesforce records. A scheduled workflow can provide incremental synchronization, while selected Gong notifications can reduce latency for newly processed calls.

Integration direction
Gong
Martini
Salesforce
Example Mapping
Gong FieldCanonical FieldTarget Field
callIdsourceCallIdExternal_Call_ID__c
startedAtconversationStartTimeActivityDate
userIdownerSourceIdOwnerId
accountIdaccountSourceIdAccountId
Martini implementation pattern

Martini retrieves newly processed Calls and related transcripts, resolves Gong Users, Accounts, Contacts, and Deals to Salesforce identifiers, applies data-sharing and duplicate rules, and writes activities or approved summaries. The workflow uses Gong call IDs as external keys, overlap windows for late-arriving data, and retry or exception handling for rate limits and incomplete processing.

Martini capabilities used
  • workflows
  • API consumption
  • scheduling
  • data mapping
  • business rules
  • error handling

Pattern 2: Stream Gong notifications to a data warehouse

When to use this pattern

Use this pattern when an analytics platform needs incremental Gong call or activity data without repeatedly polling every resource. Notifications provide an initiation signal, while a scheduled reconciliation process provides backfill and missed-event recovery.

Integration direction
Gong
Martini
SQL database
Example Mapping
Gong FieldCanonical FieldTarget Field
eventIdsourceEventIdgong_event_id
callIdsourceCallIdgong_call_id
processingStateconversationProcessingStateprocessing_state
updatedAtsourceUpdatedAtsource_updated_at
Martini implementation pattern

Martini receives a supported webhook notification, validates and deduplicates the event, retrieves the complete Gong resource, normalizes nested payloads, and writes raw or curated data to a SQL database. A separate scheduled workflow uses date windows and watermarks to reconcile missed notifications, while checkpoints and source IDs support replay.

Martini capabilities used
  • API exposure
  • webhook consumption
  • workflows
  • data mapping
  • SQL database integration
  • checkpointing
  • error handling

Pattern 3: Synchronize Gong activity with HubSpot

When to use this pattern

Use this pattern when HubSpot users need Gong Calls, Contacts, Accounts, and Deals associated with marketing or sales records. It is appropriate for incremental synchronization using a persisted watermark and target-side idempotent upserts.

Integration direction
Gong
Martini
HubSpot
Example Mapping
Gong FieldCanonical FieldTarget Field
contactIdcontactSourceIdHubSpot contact association
accountIdcompanySourceIdHubSpot company association
dealIdopportunitySourceIdHubSpot deal association
callIdactivityExternalIdHubSpot activity external reference
Martini implementation pattern

A scheduled Martini workflow retrieves Gong data for an overlapping time window, resolves target associations, transforms calls and conversation metadata into HubSpot activity structures, and upserts using stable Gong identifiers. Validation rules reject incomplete associations into an exception path, while throttling and retries protect both APIs.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • identifier correlation
  • business rules
  • retry handling

Pattern 4: Route Gong call-processing notifications to Slack or Microsoft Teams

When to use this pattern

Use this pattern when managers or customer-facing teams need selected operational notifications after Gong processes a call or reaches a supported state. It is best suited to concise metadata or approved summaries rather than unrestricted transcript distribution.

Integration direction
Gong
Martini
Slack or Microsoft Teams
Example Mapping
Gong FieldCanonical FieldTarget Field
callIdconversationReferencemessage reference
processingStatenotificationStatusmessage status
userIdconversationOwnermessage owner
accountIdcustomerOrganizationmessage context
Martini implementation pattern

Martini receives a supported notification, retrieves current Call and Account details, applies routing, privacy, and severity rules, and publishes a formatted message through the selected collaboration API. Duplicate event IDs are ignored, transient failures are retried, and transcript content is omitted unless explicitly permitted.

Martini capabilities used
  • webhook consumption
  • workflow orchestration
  • API consumption
  • business rules
  • data transformation
  • error handling

Applications commonly integrated with Gong

Gong data can be connected with CRM, collaboration, meeting, and sales-engagement applications through API-led Martini workflows. Exact object coverage and direction should be validated against the relevant Gong and target-application APIs.

Application Scenario Direction Martini Pattern
Salesforce Synchronize Gong calls, transcripts, account context, contacts, and deal activity with CRM records. Gong → Martini → Salesforce Use a scheduled or webhook-triggered workflow to retrieve the complete Gong resource, match Accounts, Contacts, and Deals using stable identifiers, map conversation data to Salesforce activity fields, and perform idempotent writes with retry handling.
HubSpot Associate Gong conversation activity and sales insights with HubSpot Contacts, Companies, and Deals. Gong → Martini → HubSpot Retrieve Gong data for an incremental time window, normalize Users, Accounts, Contacts, Calls, and Deals, resolve HubSpot associations, and upsert activities using Gong identifiers as external keys.
Slack Deliver selected Gong call-processing notifications, coaching alerts, or management summaries to collaboration channels. Gong → Martini → Slack Receive a supported Gong notification, retrieve current call details, apply routing and data-sharing rules, format a concise message, and publish it through the target Slack API while avoiding unauthorized transcript content.
Microsoft Teams Share selected Gong notifications or conversation summaries with sales and customer-facing teams. Gong → Martini → Microsoft Teams Trigger a Martini workflow from a supported Gong event or scheduled query, enrich the notification with call state and ownership data, apply sensitive-data rules, and send a formatted Teams message.
Zoom Associate recorded meetings and call metadata with Gong conversation intelligence workflows where the organization has enabled the relevant configuration. Zoom → Martini → Gong Use Martini to orchestrate approved meeting metadata or recording flows between Zoom and Gong, transform identifiers and status fields, and retain processing checkpoints for replay and reconciliation.
Google Meet Send meeting recordings or meeting activity into Gong where supported by the organization’s Gong configuration. Google Meet → Martini → Gong Coordinate supported meeting-capture or recording data with Gong through authenticated APIs, validate availability and permissions, and track processing state before downstream synchronization.
Outreach Correlate sales-engagement activity with Gong calls, coaching, and deal context. Gong → Martini → Outreach Retrieve relevant Gong activity, match sales engagement users and prospects, transform activity payloads to the target model, and use source identifiers and controlled retries to prevent duplicates.
Salesloft Combine sales-engagement activity with Gong conversation and performance data. Gong → Martini → Salesloft Run an incremental synchronization workflow that maps Gong Users, Calls, Accounts, Contacts, and Deals to Salesloft activity structures, applies correlation rules, and records failed items for replay.

How to build a Gong integration in Martini

Objective

Establish authenticated access to Gong and the target application using environment-specific configuration.

Instructions in Martini

  • Choose Gong access keys with HTTP Basic Authentication or a supported OAuth 2.0 configuration.
  • Store Gong credentials and target-system secrets in Martini environment secrets.
  • Use separate development, test, and production credentials where possible.
  • Confirm Gong organization, role, application, and resource permissions.

Objective

Select the trigger that matches the required latency, event coverage, and data volume.

Instructions in Martini

  • Use a supported Gong webhook notification for selected processing events.
  • Use a scheduler for incremental synchronization, reconciliation, and resources without webhook coverage.
  • Use a separate scheduled workflow for historical or bulk retrieval.
  • Define overlap windows and persisted watermarks for late-arriving updates.

Objective

Obtain complete Gong resources rather than relying on notification payloads alone.

Instructions in Martini

  • Receive and validate the webhook notification when applicable.
  • Retrieve the current Call, transcript, User, Account, Contact, or Deal through the Gong REST API.
  • Follow pagination, cursor, filter, and asynchronous-job status controls.
  • Check processing state before requesting transcript or recording resources.

Objective

Coordinate retrieval, enrichment, target writes, and recovery as a maintainable Martini workflow.

Instructions in Martini

  • Separate event intake from longer-running resource retrieval where necessary.
  • Add correlation identifiers and checkpoints to each workflow run.
  • Control concurrency for high-volume imports and bulk operations.
  • Route validation failures and exhausted retries to an operational exception path.

Objective

Transform Gong payloads into the canonical and target application models.

Instructions in Martini

  • Map Gong Users, Calls, Call transcripts, Accounts, Contacts, and Deals to target fields.
  • Normalize timestamps, identifiers, ownership, processing states, and nested data.
  • Use stable Gong identifiers as external keys.
  • Apply transcript and recording redaction or summarization rules where required.

Objective

Enforce business, privacy, matching, and synchronization rules before writing downstream data.

Instructions in Martini

  • Resolve Gong Accounts, Contacts, and Deals to target records using configured matching keys.
  • Reject or quarantine payloads missing required identifiers or associations.
  • Apply rules that limit sensitive transcript or recording content.
  • Ignore duplicate webhook events and update existing target objects on replay.

Common Gong data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
UsersRepresent Gong sales representatives, managers, and administrators for ownership, attribution, and access context.Salesforce, HubSpot, data warehouses, sales-engagement platformsMartini retrieves Users, normalizes identifiers and attributes, and resolves them against target users or owners before writing related activity.
CallsStore recorded or imported customer interactions, metadata, ownership, timestamps, and processing state.Salesforce, HubSpot, SQL databases, analytics platforms, Slack, Microsoft TeamsMartini retrieves Calls through REST APIs or after supported notifications, waits for processing when necessary, applies idempotent upsert rules, and routes selected summaries or metadata.
Call transcriptsProvide transcript content and speaker or conversation information for supported calls.Salesforce, data warehouses, analytics platforms, operational databasesMartini retrieves transcript data only when available and authorized, transforms or summarizes it according to policy, and protects sensitive content during downstream writes.
AccountsRepresent customer or prospect organizations associated with Gong activity.Salesforce, HubSpot, data warehouses, sales-engagement platformsMartini maps Gong Accounts to target organizations using configured matching keys, preserves Gong identifiers, and handles unmatched objects through exception paths.
ContactsRepresent individuals associated with customer accounts and interactions.Salesforce, HubSpot, Outreach, Salesloft, data warehousesMartini normalizes contact attributes, applies matching and deduplication rules, and links Contacts to Calls, Accounts, or target activities.
DealsRepresent sales opportunities associated with Gong activity and CRM synchronization.Salesforce, HubSpot, Outreach, Salesloft, analytics platformsMartini correlates Deals with target opportunities, maps lifecycle and ownership fields, and updates existing records using stable Gong identifiers.

Authentication and security considerations

Authentication options

Gong supports API access keys and secrets transmitted with HTTP Basic Authentication for common server-to-server access. OAuth 2.0 is available for supported application and delegated-authorization scenarios.

Credential protection

Store Gong credentials in Martini environment secrets rather than embedding them in workflows or API definitions. Use separate credentials for development, testing, and production where possible.

Permissions and sensitive data

Gong organization, user, role, and application permissions determine which Calls, transcripts, Users, Accounts, Contacts, and Deals an integration can access. Apply least privilege and protect recordings and transcript content as potentially sensitive data.

  • Validate webhook authentication or signature information according to Gong configuration.
  • Restrict downstream transcript and recording access.
  • Consider retention, consent, data residency, and personally identifiable information requirements.

Operational considerations for Gong integrations

Rate limits and pagination

Gong responses may be paginated and endpoint limits should be confirmed for the organization. Use cursors or page controls, controlled concurrency, exponential backoff for HTTP 429 responses, and separate workflows for high-volume historical imports.

Processing state and late data

Webhook notifications may arrive before Calls, transcripts, or recordings are fully available. Check processing state, wait or retry when necessary, and use overlap windows or scheduled reconciliation to capture late updates.

Idempotency and replay

Persist Gong source identifiers, webhook event IDs where provided, source timestamps, and synchronization checkpoints. Use target-side external keys and idempotent upserts so retries and replay do not create duplicate activities.

Schema and testing

Treat Gong response fields as versioned contracts. Validate required fields, preserve or safely ignore unknown fields, separate mappings from control logic, and test representative Calls, transcripts, Accounts, Contacts, and Deals across processing states.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrate beyond a single API call

Scripts often combine authentication, polling, pagination, mapping, retries, and target writes in one code path. Martini separates these responsibilities into reusable workflows and APIs that can support scheduled, event-driven, bulk, and reconciliation processes.

Maintainable data transformation

Martini provides visual mapping and workflow orchestration for transforming Gong payloads into CRM, collaboration, database, or analytics models while keeping business rules and exception paths explicit.

Reliable operations

Checkpointing, idempotency, controlled retries, validation, logging, and monitoring help teams recover from rate limits, delayed processing, schema changes, and missed webhook notifications without rebuilding point-to-point logic.

  • Consume Gong REST APIs and expose controlled Martini APIs.
  • Combine webhook intake with scheduled reconciliation.
  • Centralize secrets and environment-specific configuration.
  • Reuse integration assets across target systems and deployment environments.

Frequently asked questions

How can Gong be integrated with enterprise systems?

Gong can be integrated primarily through its REST APIs for Users, Calls, Call transcripts, Accounts, Contacts, Deals, activity, and conversation intelligence data. Selected webhook-style notifications can initiate processing for supported events or call-processing states, while scheduled workflows support incremental synchronization, reconciliation, and bulk or asynchronous retrieval.

Can Martini integrate with Gong?

Yes. Martini can integrate with Gong by consuming Gong REST APIs, receiving supported webhook notifications through an exposed API or workflow, authenticating with access keys and secrets or supported OAuth 2.0 configurations, and transforming Gong data for applications, databases, and collaboration platforms.

Do I need a connector to integrate Gong with Martini?

No. A dedicated Gong connector is not required. Martini can use Gong’s confirmed native integration mechanisms, including REST APIs, selected webhook notifications, applicable bulk or asynchronous retrieval patterns, and supported authentication methods.

Is there any extra Lonti cost to integrate Gong with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Gong. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Gong, cloud infrastructure, databases, or other third-party systems based on subscriptions, usage, and deployment model.

Which Gong integration methods should an enterprise use?

Use Gong REST APIs as the primary integration method. Use selected webhook notifications when supported events or processing states need prompt handling, and use scheduled REST API synchronization for reconciliation, historical imports, missed events, and resources without webhook coverage. Gong GraphQL and SOAP APIs were not confirmed.

Are Gong webhooks available for event-driven integrations?

Gong supports webhook-style notifications for selected events and processing states, but coverage is not universal. A robust design validates the notification, retrieves the complete Gong resource through the REST API, handles delayed call or transcript processing, and runs scheduled reconciliation for missed or unsupported events.

How does Martini synchronize Gong data without creating duplicates?

Martini can use stable identifiers such as Gong Call, User, Account, Contact, Deal, and webhook event IDs, together with persisted timestamps or synchronization watermarks. Overlap windows can capture late-arriving updates, while idempotent upserts ensure retries update existing target data instead of creating duplicates.

How does Martini handle Gong transcripts, errors, and sensitive data?

Martini can retrieve supported transcript resources after Gong processing is complete, map or summarize the content, and write it to approved targets. Workflows can handle pagination, rate limits, retries, validation failures, and replay. Access controls, retention, consent, data residency, and transcript-sharing policies should determine what content is copied downstream.

Related Martini documentation

APIs

Events

Workflows

Security

Operations

Connect Gong with your enterprise systems

Use Martini to build maintainable Gong integrations with REST APIs, selected webhook notifications, scheduled synchronization, data transformation, and reliable workflow orchestration.

EXPLORE MARTINI
BOOK A DEMO