Skip to content
Data warehouse ⇄ CRM

Databricks to Kustomer integration — real-time, two-way sync

Keep Databricks and Kustomer 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 Kustomer

Sync Kustomer 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. Conversations, Messages, Companies, Custom Objects (Klasses) from Kustomer land in Databricks as live tables, updated within seconds, and columns computed in Databricks write back to fields in Kustomer. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

Common use cases

  • Keep customer attributes updated from billing systems so routing rules and SLAs reflect account value
  • Escalate conversation-derived signals into the CRM as tasks or opportunities
  • Use Change Data Feed to propagate only changed rows to downstream apps instead of full-table scans.
  • Serve ML feature outputs computed in Databricks to production apps through a synced operational store.

A single customer view

Join Kustomer's relationship data with billing, product, and support data in Databricks to build the customer picture the CRM alone cannot hold.

Cleanup that sticks

Deduplication and normalization done in Databricks can be written back, so warehouse-side cleanup actually fixes the CRM.

CRM analytics on live data

Accounts, contacts, and activity from Kustomer are queryable in Databricks moments after they change, so dashboards stop lagging the reality they describe.

What you can sync between Databricks and Kustomer

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 Kustomer objects
Volumes Unity Catalog file storage used for staging bulk loads. Conversations Support threads across channels sync outward for analytics and CRM context.
SQL Warehouses The compute endpoint a sync connects to for query execution. Messages Individual messages within conversations support full-thread replication.
Change Data Feed Row-level change records on Delta tables that drive incremental reads. Companies Organization records group customers and map to CRM accounts.
Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline.
Schemas Group tables and views; syncs typically target a dedicated schema per source system. Users Agent records map conversation ownership to people in other systems.
Delta Tables The primary read and write target; operational data lands here as managed or external tables. Teams Team assignments support routing parity and reporting.
What ships with Databricks ⇄ Kustomer

Connect Databricks and Kustomer for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–Kustomer connection.

Real-time

Two-way sync

Changes in Databricks or Kustomer instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Databricks or Kustomer 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 Kustomer record.

Observability

Monitoring

Track your Databricks ⇄ Kustomer 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 Kustomer.

How the Databricks and Kustomer 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

Kustomer

Integration surface
REST API
Authentication
API key used as a bearer token, scoped by role
Change detection
Outbound webhooks on record events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits
How it works

How to connect Databricks to Kustomer — 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.

  1. 01

    Connect your apps

    Authenticate Databricks and Kustomer with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Databricks connected
    Kustomer connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Databricks and Kustomer 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Databricks ⇄ Kustomer
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Databricks Kustomer
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Databricks and Kustomer integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Databricks and Kustomer.

Popular · 8 of 386
All Databricks integrations All Kustomer integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own