Skip to content
Database ⇄ CRM

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

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

Treat Gong like part of your database: its records live in DuckDB as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in DuckDB, where it can be queried and joined like everything else.

Stacksync mirrors Users, Interaction Stats (Activity), Trackers & Scorecards, CRM Objects from Gong into Attached databases, Database files, Schemas, Tables in DuckDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Gong with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Submit data-privacy erase-data-for-email requests to Gong to fulfill GDPR/CCPA deletion across recorded conversations.
  • 02 Pull call Transcripts by callId into a warehouse or vector store to power search, RAG, and deal-review summaries over what was said on calls.
  • 03 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
  • 04 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.

Common sync patterns

Query the CRM like a database

Accounts, contacts, and custom objects from Gong become tables in DuckDB you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to DuckDB sync onto the matching records in Gong, giving go-to-market teams live product context.

Internal tools without API code

Back-office apps read and write the synced tables; Stacksync handles the Gong API, limits, and retries.

What you can sync between DuckDB 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.

DuckDB objects Gong objects How this pairing syncs
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. External files (Parquet/CSV/JSON) is specific to DuckDB and Library to Gong — each maps to any object or custom field on the other side.
Attached databases Additional database files or external systems attached into one session for cross-source queries. 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 databases is specific to DuckDB and Data Privacy (Erasure) to Gong — each maps to any object or custom field on the other side.
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. 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. Database files is specific to DuckDB and Calls to Gong — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize tables in sync outputs. 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 is specific to DuckDB and Transcripts to Gong — each maps to any object or custom field on the other side.
Tables Columnar tables created via SQL; the destination for materialized sync data. 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. Tables is specific to DuckDB and Users to Gong — each maps to any object or custom field on the other side.
Views SQL views used to shape or filter data for downstream consumers. Interaction Stats (Activity) Aggregated talk/listen ratios, interaction stats, and day-by-day user activity retrieved via POST /v2/stats endpoints; read out for coaching and engagement reporting. Read-only. Views is specific to DuckDB and Interaction Stats (Activity) to Gong — each maps to any object or custom field on the other side.

How changes propagate between DuckDB 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.

DuckDB Gong Interval-based propagation

DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.

DeliveryEach detected change is written to Gong through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
  • 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 DuckDB ⇄ Gong

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your DuckDB ⇄ Gong sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between DuckDB and Gong.

How the DuckDB and Gong connectors work

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

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
How it works

How to connect DuckDB 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.

  1. 01

    Connect your apps

    Authenticate DuckDB 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.

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

    Choose tables

    Pick the DuckDB 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · DuckDB ⇄ Gong
    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
    DuckDB Gong
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DuckDB and Gong 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 471 integrations available for DuckDB and Gong.

Popular · 7 of 471
All DuckDB integrations All Gong 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