Real-time
Two-way sync
Changes in Apache Druid or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ CRM
Apache Druid to Twenty CRM integration — real-time, two-way sync
Keep Apache Druid and Twenty CRM 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 Twenty CRM
Sync Twenty CRM 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. Tasks, Notes, Custom Objects, Attachments from Twenty CRM land in Apache Druid as live tables, updated within seconds, and columns computed in Apache Druid write back to fields in Twenty CRM. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Common use cases
- Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
- Two-way sync of People and Companies between Twenty and a production Postgres database so engineers can query CRM data with SQL.
- Expose product telemetry stored in Druid to business tools without granting direct cluster access.
- Query aggregated event metrics from Druid and sync them into CRM account fields for usage-based selling.
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 Twenty CRM 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 Twenty CRM, where the people working accounts actually see them.
What you can sync between Apache Druid and Twenty CRM
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 | Twenty CRM objects | |
|---|---|---|
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Notes Free-form notes attached to records, useful for mirroring activity from other tools. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. | |
| Dimensions String and categorical columns used for filtering and grouping in synced queries. | Attachments Files linked to records. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Workspace Members User accounts used for record ownership and assignment mapping. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Companies Account-level records that group people and opportunities. |
What ships with Apache Druid ⇄ Twenty CRM
Connect Apache Druid and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Apache Druid or Twenty CRM 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 Twenty CRM record.
Observability
Monitoring
Track your Apache Druid ⇄ Twenty CRM 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 Twenty CRM.
How the Apache Druid and Twenty CRM 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
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Apache Druid to Twenty CRM — 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 Twenty CRM 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
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Apache Druid and Twenty CRM 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 ⇄ Twenty CRMCustomers 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 Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Apache Druid and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Apache Druid and Twenty CRM: authenticate both systems, choose the objects to sync (such as Apache Druid's Datasources and Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Apache Druid and Twenty CRM records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Apache Druid and Twenty CRM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Apache Druid–Twenty CRM integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Apache Druid and Twenty CRM. 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 Twenty CRM: Webhooks on record create, update, and delete events, or polling on record update timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Twenty CRM side: Tasks, Notes, Custom Objects, Attachments, plus custom fields where Twenty CRM exposes them. On the Apache Druid side: Dimensions, Metrics, Ingestion Supervisors, Lookups. Stacksync auto-detects both schemas and converts types between the two systems.
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 Apache Druid and Twenty CRM.
Popular · 8 of 386
-
Apache Druid ⇄ Attio -
Apache Druid ⇄ Pipedrive -
Apache Druid ⇄ Zoho CRM -
Apache Druid ⇄ Shopify -
Twenty CRM ⇄ Vertica -
Twenty CRM ⇄ Yellowbrick -
Twenty CRM ⇄ Snowflake -
Twenty CRM ⇄ BigQuery
No integrations match .
