Real-time
Two-way sync
Changes in Apache Druid or Intercom instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ CRM
Apache Druid to Intercom integration — real-time, two-way sync
Keep Apache Druid 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 Apache Druid and Intercom
Sync Intercom into Apache Druid 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. Tags, Segments, Admins & Teams, Articles from Intercom land in Apache Druid as live tables, updated within seconds, and columns computed in Apache Druid 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
- 01 Keep custom data attributes updated from billing or ERP systems so message segments reflect current plan and spend
- 02 Route qualified leads from Intercom conversations into the CRM as leads or opportunities in near real time
- 03 Feed operational records into Druid via batch ingestion so analysts get interactive slice-and-dice on fresh data.
- 04 Sync Druid query results into a warehouse to combine real-time aggregates with historical models.
Common sync patterns
Cleanup that sticks
Deduplication and normalization done in Apache Druid 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 Apache Druid 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 Apache Druid appear as fields in Intercom, where the people working accounts actually see them.
What you can sync between Apache Druid 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.
| Apache Druid objects | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Segments Saved audience definitions are readable for targeting parity across tools. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tasks Batch ingestion and compaction jobs monitored during data loads. | Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Tasks is specific to Apache Druid and Custom Data Attributes to Intercom — each maps to any object or custom field on the other side. | |
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Datasources is specific to Apache Druid and Tags to Intercom — each maps to any object or custom field on the other side. | |
| Dimensions String and categorical columns used for filtering and grouping in synced queries. | Admins & Teams Teammate records map conversation ownership to CRM users. | Dimensions is specific to Apache Druid and Admins & Teams to Intercom — each maps to any object or custom field on the other side. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Articles Help center content is accessible via API for knowledge sync and audits. | Metrics is specific to Apache Druid and Articles to Intercom — each maps to any object or custom field on the other side. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Ingestion Supervisors is specific to Apache Druid and Contacts to Intercom — each maps to any object or custom field on the other side. |
How changes propagate between Apache Druid and Intercom
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.
Apache Druid Intercom Interval-based propagation
DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Intercom Apache Druid Sub-second propagation
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is applied to Apache Druid as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Apache Druid ⇄ Intercom
Connect Apache Druid and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Apache Druid 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 Apache Druid or Intercom record.
Observability
Monitoring
Track your Apache Druid ⇄ Intercom sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Apache Druid and Intercom.
How the Apache Druid and Intercom connectors work
Apache Druid
- Integration surface
- REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
- Authentication
- Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
- Change detection
- Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
- Capabilities
- read · write
- Rate limits
- No fixed API quotas; query concurrency is bounded by broker and historical node capacity
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 Apache Druid 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 Apache Druid 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.
Apache Druid
connected
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Apache Druid 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 · Apache Druid ⇄ 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.
Apache Druid IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Apache Druid and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Apache Druid and Intercom: authenticate both systems, choose the objects to sync (such as Apache Druid's Segments and Tasks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Apache Druid and Intercom. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Apache Druid: Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates. 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: Tags, Segments, Admins & Teams, Articles, plus custom fields where Intercom exposes them. On the Apache Druid side: Metrics, Ingestion Supervisors, Lookups, Tasks. 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 Apache Druid and Intercom: Cleanup that sticks; CRM analytics on live data; Scores and segments back on the record. Deduplication and normalization done in Apache Druid can be written back, so warehouse-side cleanup actually fixes the CRM.
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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 447 integrations available for Apache Druid and Intercom.
Popular · 6 of 447
-
Apache Druid ⇄ Salesloft -
Apache Druid ⇄ SAP Sales Cloud -
Intercom ⇄ Snowflake -
Intercom ⇄ BigQuery -
Intercom ⇄ MotherDuck -
Intercom ⇄ Databricks
No integrations match .
