Real-time
Two-way sync
Changes in Gong or Kommo instantly reflect in both systems. No stale data, no manual imports.
CRM
Gong to Kommo integration — real-time, two-way sync
Keep Gong and Kommo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Gong and Kommo
Run Gong and Kommo side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.
Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.
Stacksync syncs Calls, Transcripts, Users, Interaction Stats (Activity) in Gong with Contacts, Companies, Pipelines & Statuses, Tasks in Kommo in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.
Common use cases
- 01 Import externally recorded dialer or web-conference calls into Gong via POST /v2/calls so they get transcribed and analyzed like native Gong calls.
- 02 Upload warehouse- or CRM-derived Accounts, Opportunities, and stages into Gong through the CRM integration API so deal context shows alongside conversations.
- 03 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
- 04 Keep customer records consistent between Kommo and invoicing or ERP systems
Common sync patterns
Post-acquisition consolidation
Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
Migration with a parallel run
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Divisional or regional split
Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
What you can sync between Gong and Kommo
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Gong objects | Kommo objects | How this pairing syncs | |
|---|---|---|---|
| Users Gong users and team members with roles, titles, email, and settings, read via GET /v2/users to map call owners and participants to CRM and warehouse identities. Read-only. | Users Account users map lead ownership to people in other systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Trackers & Scorecards Keyword and topic tracker definitions plus coaching scorecards, including answered scorecards, read from Settings as coaching and deal-risk signals. Read-only. | Leads The central pipeline record; external signups and form fills sync in as leads. | Trackers & Scorecards is specific to Gong and Leads to Kommo — each maps to any object or custom field on the other side. | |
| CRM Objects Accounts, opportunities, stages, and users uploaded into Gong through the CRM integration API so CRM context appears alongside conversations. Write (upload) path. | Contacts Person records sync with other CRMs and databases for a shared contact file. | CRM Objects is specific to Gong and Contacts to Kommo — each maps to any object or custom field on the other side. | |
| Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. | Companies Organization records map to accounts in ERPs and invoicing tools. | Library is specific to Gong and Companies to Kommo — each maps to any object or custom field on the other side. | |
| Data Privacy (Erasure) GDPR/CCPA deletion handled by POST /v2/data-privacy/erase-data-for-email, with data-for-email lookups on the read side; a write path used for compliance deletions. | Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. | Data Privacy (Erasure) is specific to Gong and Pipelines & Statuses to Kommo — each maps to any object or custom field on the other side. | |
| Calls Retrieved via POST /v2/calls/extensive with participants, topics, trackers, scorecards, and media URLs, filtered by fromDateTime/toDateTime; external recordings are also imported via POST /v2/calls with media uploaded via PUT /v2/calls/{id}/media. Read and write. | Tasks Follow-up records keep rep activity consistent across systems. | Calls is specific to Gong and Tasks to Kommo — each maps to any object or custom field on the other side. |
How changes propagate between Gong and Kommo
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Gong Kommo Interval-based propagation
DetectionStacksync polls Gong for changes on an incremental schedule, reading only records changed since the previous pass. Polling POST /v2/calls/extensive on fromDateTime/toDateTime.
DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.
Kommo Gong Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.
DeliveryEach detected change is written to Gong through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Gong: 3 API calls per second and 10,000 calls per day per company by default; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong.
- Kommo: Subject to per-account request rate limits.
What ships with Gong ⇄ Kommo
Connect Gong and Kommo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gong–Kommo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Gong or Kommo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Gong or Kommo record.
Observability
Monitoring
Track your Gong ⇄ Kommo sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Gong and Kommo.
How the Gong and Kommo connectors work
Gong
- Integration surface
- REST API on api.gong.io/v2 - retrieval endpoints (calls, transcript, users, stats, settings, library, logs) plus write endpoints for importing calls, uploading CRM data, and data-privacy erasure
- Authentication
- Basic authorization header combining an Access Key and Access Key Secret (created by a Gong technical admin, base64-encoded as key:secret); OAuth 2.0 Bearer tokens are supported for marketplace apps
- Change detection
- Polling POST /v2/calls/extensive on fromDateTime/toDateTime; the public API exposes no outbound webhooks or CDC, though a Gong admin can configure a product-side automation Rule that POSTs matching calls to a URL. Transcripts and analysis appear only after asynchronous processing.
- Capabilities
- read · write
- Rate limits
- 3 API calls per second and 10,000 calls per day per company by default; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong.
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request rate limits
How it works
How to connect Gong to Kommo — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Gong and Kommo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Gong
connected
Kommo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Gong and Kommo objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Gong ⇄ KommoCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Gong KommoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Gong and Kommo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Gong and Kommo: authenticate both systems, choose the objects to sync (such as Gong's Users and Trackers & Scorecards), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Gong and Kommo. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Gong: Polling POST /v2/calls/extensive on fromDateTime/toDateTime; the public API exposes no outbound webhooks or CDC, though a Gong admin can configure a product-side automation Rule that POSTs matching calls to a URL. Transcripts and analysis appear only after asynchronous processing. On Kommo: Webhooks on record add and update events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Gong side: Calls, Transcripts, Users, Interaction Stats (Activity), plus custom fields where Gong exposes them. On the Kommo side: Contacts, Companies, Pipelines & Statuses, Tasks. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Gong and Kommo: Post-acquisition consolidation; Migration with a parallel run; Divisional or regional split. Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 541 integrations available for Gong and Kommo.
Popular · 8 of 541
-
Gong ⇄ Pipedrive -
Gong ⇄ Zoho CRM -
Gong ⇄ Shopify -
Gong ⇄ Affinity -
Kommo ⇄ Nimble -
Kommo ⇄ Nutshell -
Kommo ⇄ Oracle CX Sales -
Kommo ⇄ Outreach
No integrations match .
