Skip to content
CRM ⇄ Database

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

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

Treat Chorusai 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 Scorecards, Moments, Playlists, Engagements from Chorusai into Schemas, Tables, Views, External files (Parquet/CSV/JSON) in DuckDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Chorusai 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 Read the Deals associated with each conversation to attribute call activity to open opportunities in a BI model.
  • 02 Upload externally recorded dialer or web-conference audio into Chorus as Recordings so it gets transcribed and analyzed like native calls.
  • 03 Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
  • 04 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.

Common sync patterns

Trigger workflows from CRM changes

Field and stage updates in Chorusai arrive as row changes in DuckDB, ready to drive jobs and notifications.

Query the CRM like a database

Accounts, contacts, and custom objects from Chorusai 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 Chorusai, giving go-to-market teams live product context.

What you can sync between Chorusai and DuckDB

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.

Chorusai objects DuckDB objects How this pairing syncs
Recordings (Conversations) The recorded call with utterances, transcript, thumbnails, and metrics; read for analysis and uploaded or deleted through the API. Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. Recordings (Conversations) is specific to Chorusai and Database files to DuckDB — each maps to any object or custom field on the other side.
Users Chorus users with roles and team membership; read to map engagement owners and participants to CRM and warehouse identities. Schemas Namespaces within a database used to organize tables in sync outputs. Users is specific to Chorusai and Schemas to DuckDB — each maps to any object or custom field on the other side.
Trackers AI keyword and topic trackers (pricing, competitors, next steps) surfaced within a conversation; read out as coaching and deal-risk signals. Tables Columnar tables created via SQL; the destination for materialized sync data. Trackers is specific to Chorusai and Tables to DuckDB — each maps to any object or custom field on the other side.
Deals CRM opportunity context attached to a conversation (account, deal, owner); read to attribute call activity to open pipeline. Views SQL views used to shape or filter data for downstream consumers. Deals is specific to Chorusai and Views to DuckDB — each maps to any object or custom field on the other side.
Scorecards Call QA and coaching assessments with reviewer, recipient, and scores; read and exported for rep-performance reporting. External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. Scorecards is specific to Chorusai and External files (Parquet/CSV/JSON) to DuckDB — each maps to any object or custom field on the other side.
Moments Timestamped highlight clips from a conversation; created via the API to capture key call snippets. Attached databases Additional database files or external systems attached into one session for cross-source queries. Moments is specific to Chorusai and Attached databases to DuckDB — each maps to any object or custom field on the other side.

How changes propagate between Chorusai and DuckDB

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.

Chorusai DuckDB Interval-based propagation

DetectionStacksync polls Chorusai for changes on an incremental schedule, reading only records changed since the previous pass. Polling the engagements endpoint on date_time and processing_state.

DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.

DuckDB Chorusai 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 Chorusai through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Chorusai: Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes.
  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
What ships with Chorusai ⇄ DuckDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Chorusai and DuckDB connectors work

Chorusai

Integration surface
REST API (api-docs.chorus.ai)
Authentication
Per-user API token generated in Chorus Personal Settings, sent in the Authorization request header
Change detection
Polling the engagements endpoint on date_time and processing_state; no public change webhooks or CDC
Capabilities
read · write
Rate limits
Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes
Chorusai setup guide

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

How to connect Chorusai to DuckDB — 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 Chorusai and DuckDB 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
    Chorusai connected
    DuckDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Chorusai and DuckDB 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 · Chorusai ⇄ DuckDB
    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
    Chorusai DuckDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Chorusai and DuckDB 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 469 integrations available for Chorusai and DuckDB.

Popular · 5 of 469
All Chorusai integrations All DuckDB 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