Real-time
Two-way sync
Changes in Clari or Gong instantly reflect in both systems. No stale data, no manual imports.
CRM
Clari to Gong integration — real-time, two-way sync
Keep Clari and Gong 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 Clari and Gong
Run Clari and Gong 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 Forecast, Quota, Opportunities, Activity (Capture) in Clari with CRM Objects, Library, Data Privacy (Erasure), Calls in Gong 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 Pull Activity (Capture) meetings and emails, mapped to their accounts and opportunities, into a database for coverage and engagement analysis.
- 02 Write warehouse-computed health scores and usage metrics onto Clari Opportunity records as field extensions via the ingest API so deal reviews show product signals.
- 03 Sync Interaction Stats such as talk ratios and per-rep activity into a coaching database for engagement and rep-performance dashboards.
- 04 Import externally recorded dialer or web-conference calls into Gong via POST /v2/calls so they get transcribed and analyzed like native Gong calls.
Common sync patterns
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.
Where both track pipeline: deal visibility across systems
Deal stage and value on shared accounts stay visible from either CRM.
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.
What you can sync between Clari and Gong
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.
| Clari objects | Gong objects | How this pairing syncs | |
|---|---|---|---|
| Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. | CRM Objects Accounts, opportunities, stages, and users uploaded into Gong through the CRM integration API so CRM context appears alongside conversations. Write (upload) path. | Opportunity field extensions is specific to Clari and CRM Objects to Gong — each maps to any object or custom field on the other side. | |
| Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. | Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. | Audit Events is specific to Clari and Library to Gong — each maps to any object or custom field on the other side. | |
| Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. | 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. | Forecast is specific to Clari and Data Privacy (Erasure) to Gong — each maps to any object or custom field on the other side. | |
| Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. | 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. | Quota is specific to Clari and Calls to Gong — each maps to any object or custom field on the other side. | |
| Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. | Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. | Opportunities is specific to Clari and Transcripts to Gong — each maps to any object or custom field on the other side. | |
| Activity (Capture) Meetings, emails, and attachments captured by Clari and mapped to accounts and opportunities; exported read-only via async activity jobs. | 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. | Activity (Capture) is specific to Clari and Users to Gong — each maps to any object or custom field on the other side. |
How changes propagate between Clari and Gong
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.
Clari Gong Interval-based propagation
DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).
DeliveryEach detected change is written to Gong through its API, with automatic retries and rate-limit backoff.
Gong Clari 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 Clari through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
- 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.
What ships with Clari ⇄ Gong
Connect Clari and Gong for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Clari–Gong connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Clari or Gong 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 Clari or Gong record.
Observability
Monitoring
Track your Clari ⇄ Gong sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Clari and Gong.
How the Clari and Gong connectors work
Clari
- Integration surface
- REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
- Authentication
- API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
- Change detection
- Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
- Capabilities
- read · write
- Rate limits
- Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
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.
How it works
How to connect Clari to Gong — 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 Clari and Gong with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Clari
connected
Gong
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Clari and Gong 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 · Clari ⇄ GongCustomers 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.
Clari GongCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Clari and Gong integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Clari and Gong: authenticate both systems, choose the objects to sync (such as Clari's Opportunity field extensions and Audit Events), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Clari and Gong. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Clari: Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks. 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Clari side: Forecast, Quota, Opportunities, Activity (Capture), plus custom fields where Clari exposes them. On the Gong side: CRM Objects, Library, Data Privacy (Erasure), Calls. 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 Clari and Gong: Divisional or regional split; Where both track pipeline: deal visibility across systems; Post-acquisition consolidation. Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
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 445 integrations available for Clari and Gong.
Popular · 6 of 445
-
Clari ⇄ Clearbit -
Clari ⇄ Close -
Clari ⇄ Copper CRM -
Gong ⇄ Folk CRM -
Gong ⇄ Freshsales -
Gong ⇄ Freshworks CRM
No integrations match .
