Skip to content
CRM ⇄ Data warehouse

Gong to MotherDuck integration — real-time, two-way sync

Keep Gong and MotherDuck 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 MotherDuck

Sync Gong into MotherDuck continuously and push warehouse results back onto CRM records, one two-way connection instead of two pipelines.

The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.

Stacksync does both with one connection. Interaction Stats (Activity), Trackers & Scorecards, CRM Objects, Library from Gong land in MotherDuck as live tables, updated within seconds, and columns computed in MotherDuck write back to fields in Gong. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

Common use cases

  • 01 Upload warehouse- or CRM-derived Accounts, Opportunities, and stages into Gong through the CRM integration API so deal context shows alongside conversations.
  • 02 Submit data-privacy erase-data-for-email requests to Gong to fulfill GDPR/CCPA deletion across recorded conversations.
  • 03 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
  • 04 Sync modeled MotherDuck tables outward to operational tools for activation

Common sync patterns

Scores and segments back on the record

Lead scores, churn risk, or usage segments computed in MotherDuck appear as fields in Gong, where the people working accounts actually see them.

A single customer view

Join Gong's relationship data with billing, product, and support data in MotherDuck to build the customer picture the CRM alone cannot hold.

Cleanup that sticks

Deduplication and normalization done in MotherDuck can be written back, so warehouse-side cleanup actually fixes the CRM.

What you can sync between Gong and MotherDuck

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 MotherDuck objects How this pairing syncs
Trackers & Scorecards Keyword and topic tracker definitions plus coaching scorecards, including answered scorecards, read from Settings as coaching and deal-risk signals. Read-only. Tables The main landing target for synced records and source for analysis. Trackers & Scorecards is specific to Gong and Tables to MotherDuck — 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. Views Modeled projections used as outbound sync sources. CRM Objects is specific to Gong and Views to MotherDuck — 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. Database Shares Read-only copies of a database shared with other users or teams. Library is specific to Gong and Database Shares to MotherDuck — 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. Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Data Privacy (Erasure) is specific to Gong and Attached Local DuckDB Databases to MotherDuck — 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. Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Calls is specific to Gong and Databases to MotherDuck — each maps to any object or custom field on the other side.
Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. Schemas Namespaces within a database used to organize synced tables. Transcripts is specific to Gong and Schemas to MotherDuck — each maps to any object or custom field on the other side.

How changes propagate between Gong and MotherDuck

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 MotherDuck 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 applied to MotherDuck as a row-level write, with types converted between the two schemas.

MotherDuck Gong Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

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.
  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
What ships with Gong ⇄ MotherDuck

Connect Gong and MotherDuck for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gong–MotherDuck connection.

Real-time

Two-way sync

Changes in Gong or MotherDuck instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Gong or MotherDuck 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 MotherDuck record.

Observability

Monitoring

Track your Gong ⇄ MotherDuck 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 MotherDuck.

How the Gong and MotherDuck 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.
Gong setup guide

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide
How it works

How to connect Gong to MotherDuck — 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.

  1. 01

    Connect your apps

    Authenticate Gong and MotherDuck with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Gong connected
    MotherDuck connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Gong and MotherDuck 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Gong ⇄ MotherDuck
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Gong MotherDuck
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Gong and MotherDuck integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 472 integrations available for Gong and MotherDuck.

Popular · 7 of 472
All Gong integrations All MotherDuck integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own