Real-time
Two-way sync
Changes in DuckDB or Intercom instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
DuckDB to Intercom integration — real-time, two-way sync
Keep DuckDB and Intercom 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 Intercom
Treat Intercom 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 Data Events, Custom Data Attributes, Tags, Segments from Intercom into Database files, Schemas, Tables, Views in DuckDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Intercom 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
- Mirror conversations and tickets into a warehouse for support analytics and SLA reporting
- Keep custom data attributes updated from billing or ERP systems so message segments reflect current plan and spend
- Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
- Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Intercom API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Intercom arrive as row changes in DuckDB, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Intercom become tables in DuckDB you can join with application data directly.
What you can sync between DuckDB and Intercom
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 | Intercom objects | |
|---|---|---|
| Views SQL views used to shape or filter data for downstream consumers. | Tickets Structured ticket records track issues alongside conversational threads. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Data Events Behavioral events pushed in from product databases trigger messages and flows. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Segments Saved audience definitions are readable for targeting parity across tools. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Admins & Teams Teammate records map conversation ownership to CRM users. |
What ships with DuckDB ⇄ Intercom
Connect DuckDB and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB or Intercom 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 Intercom record.
Observability
Monitoring
Track your DuckDB ⇄ Intercom 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 Intercom.
How the DuckDB and Intercom 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
Intercom
- Integration surface
- REST API
- Authentication
- OAuth 2.0 for public apps or a workspace access token
- Change detection
- Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-app rate limits on the Intercom API
How it works
How to connect DuckDB to Intercom — 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 DuckDB and Intercom with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
DuckDB
connected
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB and Intercom 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 · DuckDB ⇄ IntercomCustomers 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.
DuckDB IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Intercom: authenticate both systems, choose the objects to sync (such as DuckDB's Views and External files (Parquet/CSV/JSON)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 DuckDB and Intercom: Internal tools without API code; Trigger workflows from CRM changes; Query the CRM like a database. Back-office apps read and write the synced tables; Stacksync handles the Intercom API, limits, and retries.
-
DuckDB: 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). Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Stacksync manages authentication, retries, and rate limits on both sides.
-
Intercom: Conversations are composed of nested conversation parts (messages, notes, assignments), which matters when replicating full thread history. DuckDB: It queries Parquet, CSV, and JSON files directly without importing them, which makes file-based exchange a natural sync pattern. Stacksync's field mapping accounts for these differences between DuckDB and Intercom without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means DuckDB and Intercom records are not retained after a sync operation.
SECURITY
Security teams love 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 386 integrations available for DuckDB and Intercom.
Popular · 8 of 386
-
DuckDB ⇄ Pipedrive -
DuckDB ⇄ Zoho CRM -
DuckDB ⇄ Shopify -
DuckDB ⇄ Affinity -
Intercom ⇄ RavenDB -
Intercom ⇄ Redis Enterprise -
Intercom ⇄ SAP ASE (Sybase) -
Intercom ⇄ Scaleway Postgres
No integrations match .
