Real-time
Two-way sync
Changes in Databricks or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ CRM
Databricks to Twenty CRM integration — real-time, two-way sync
Keep Databricks 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 Databricks and Twenty CRM
Sync Twenty CRM into Databricks 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. Notes, Custom Objects, Attachments, Workspace Members from Twenty CRM land in Databricks as live tables, updated within seconds, and columns computed in Databricks 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
- Two-way sync of People and Companies between Twenty and a production Postgres database so engineers can query CRM data with SQL.
- Push product usage or billing data from a warehouse into Twenty custom fields to give reps account context.
- Land CRM and ERP records in Delta tables continuously so lakehouse models work from current operational data.
- Use Change Data Feed to propagate only changed rows to downstream apps instead of full-table scans.
CRM analytics on live data
Accounts, contacts, and activity from Twenty CRM are queryable in Databricks 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 Databricks appear as fields in Twenty CRM, where the people working accounts actually see them.
A single customer view
Join Twenty CRM's relationship data with billing, product, and support data in Databricks to build the customer picture the CRM alone cannot hold.
What you can sync between Databricks 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.
| Databricks objects | Twenty CRM objects | |
|---|---|---|
| Delta Tables The primary read and write target; operational data lands here as managed or external tables. | Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. | |
| Views Curated read-only projections used as sync sources for downstream tools. | Attachments Files linked to records. | |
| Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. | Workspace Members User accounts used for record ownership and assignment mapping. | |
| Volumes Unity Catalog file storage used for staging bulk loads. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | |
| SQL Warehouses The compute endpoint a sync connects to for query execution. | Companies Account-level records that group people and opportunities. | |
| Change Data Feed Row-level change records on Delta tables that drive incremental reads. | Opportunities Deal records tracked through pipeline stages, synced for forecasting. |
What ships with Databricks ⇄ Twenty CRM
Connect Databricks and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Databricks 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 Databricks or Twenty CRM record.
Observability
Monitoring
Track your Databricks ⇄ 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 Databricks and Twenty CRM.
How the Databricks and Twenty CRM connectors work
Databricks
- Integration surface
- SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution
- Authentication
- Personal access tokens or OAuth machine-to-machine credentials for service principals
- Change detection
- Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns
- Capabilities
- read · write · CDC
- Rate limits
- Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits
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 Databricks 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 Databricks 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.
Databricks
connected
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Databricks 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 · Databricks ⇄ 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.
Databricks Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Databricks and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Databricks and Twenty CRM: authenticate both systems, choose the objects to sync (such as Databricks's Delta Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Twenty CRM side: Notes, Custom Objects, Attachments, Workspace Members, plus custom fields where Twenty CRM exposes them. On the Databricks side: Catalogs, Schemas, Delta Tables, 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 Databricks and Twenty CRM: CRM analytics on live data; Scores and segments back on the record; A single customer view. Accounts, contacts, and activity from Twenty CRM are queryable in Databricks moments after they change, so dashboards stop lagging the reality they describe.
-
Databricks: SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution. Authentication: Personal access tokens or OAuth machine-to-machine credentials for service principals. Twenty CRM: GraphQL and REST APIs. Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
-
Twenty CRM: Webhooks can be registered on record events, giving push-based change delivery without polling. Databricks: Unity Catalog imposes a three-level namespace (catalog.schema.table) that governs access across workspaces. Stacksync's field mapping accounts for these differences between Databricks and Twenty CRM without custom code.
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 Databricks and Twenty CRM.
Popular · 8 of 386
-
Databricks ⇄ Nutshell -
Databricks ⇄ Oracle CX Sales -
Databricks ⇄ Outreach -
Databricks ⇄ Salesloft -
Twenty CRM ⇄ Apache Hive -
Twenty CRM ⇄ Apache Impala -
Twenty CRM ⇄ Apache Kylin -
Twenty CRM ⇄ Apache Pinot
No integrations match .
