Real-time
Two-way sync
Changes in ClickHouse or Intercom instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ CRM
ClickHouse to Intercom integration — real-time, two-way sync
Keep ClickHouse 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 ClickHouse and Intercom
Sync Intercom into ClickHouse 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. Companies, Conversations, Tickets, Data Events from Intercom land in ClickHouse as live tables, updated within seconds, and columns computed in ClickHouse write back to fields in Intercom. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Common use cases
- Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history
- Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.
- Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.
Cleanup that sticks
Deduplication and normalization done in ClickHouse can be written back, so warehouse-side cleanup actually fixes the CRM.
CRM analytics on live data
Accounts, contacts, and activity from Intercom are queryable in ClickHouse moments after they change, so dashboards stop lagging the reality they describe.
Scores and segments back on the record
Lead scores, churn risk, or usage segments computed in ClickHouse appear as fields in Intercom, where the people working accounts actually see them.
What you can sync between ClickHouse 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.
| ClickHouse objects | Intercom objects | |
|---|---|---|
| Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. | Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | |
| Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | |
| Databases Namespaces that group tables and scope permissions for sync users. | Segments Saved audience definitions are readable for targeting parity across tools. | |
| Views Saved queries used as curated, read-only sync sources. | Admins & Teams Teammate records map conversation ownership to CRM users. | |
| Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. | Articles Help center content is accessible via API for knowledge sync and audits. | |
| Distributed tables Query-routing tables over cluster shards in self-managed deployments. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. |
What ships with ClickHouse ⇄ Intercom
Connect ClickHouse and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever ClickHouse 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 ClickHouse or Intercom record.
Observability
Monitoring
Track your ClickHouse ⇄ Intercom sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between ClickHouse and Intercom.
How the ClickHouse and Intercom connectors work
ClickHouse
- Integration surface
- Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
- Authentication
- Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
- Change detection
- No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
- Capabilities
- read · write
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 ClickHouse 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 ClickHouse 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.
ClickHouse
connected
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the ClickHouse 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 · ClickHouse ⇄ 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.
ClickHouse IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
ClickHouse and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between ClickHouse and Intercom: authenticate both systems, choose the objects to sync (such as ClickHouse's Dictionaries and Tables (MergeTree family)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both ClickHouse and Intercom. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on ClickHouse: No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source. On Intercom: Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Intercom side: Companies, Conversations, Tickets, Data Events, plus custom fields where Intercom exposes them. On the ClickHouse side: Dictionaries, Tables (MergeTree family), Databases, Views. 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 ClickHouse and Intercom: Cleanup that sticks; CRM analytics on live data; Scores and segments back on the record. Deduplication and normalization done in ClickHouse can be written back, so warehouse-side cleanup actually fixes the CRM.
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 ClickHouse and Intercom.
Popular · 8 of 386
-
ClickHouse ⇄ Kustomer -
ClickHouse ⇄ Nimble -
ClickHouse ⇄ Nutshell -
ClickHouse ⇄ Oracle CX Sales -
Intercom ⇄ IBM Netezza -
Intercom ⇄ Materialize -
Intercom ⇄ Rockset -
Intercom ⇄ Starburst Enterprise
No integrations match .
