Skip to content
Data warehouse ⇄ Marketing

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

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

Put modeled data to work and measure what it drives: Databricks and Demandbase keep contacts, audiences, and campaign results in step in real time, in both directions.

Databricks is where your team models customers, product usage, and revenue into trusted tables; Demandbase runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.

Stacksync syncs SQL Warehouses, Change Data Feed, Catalogs, Schemas in Databricks with Account & Person Lists (Audiences), Company Details (B2B enrichment), Change Subscriptions, Accounts in Demandbase field by field, in real time, and in both directions. You decide which system owns which fields — a computed score or segment can flow out to Demandbase while sends, opens, and conversions flow back to Databricks — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Land CRM and ERP records in Delta tables continuously so lakehouse models work from current operational data.
  • 02 Use Change Data Feed to propagate only changed rows to downstream apps instead of full-table scans.
  • 03 Subscribe to Demandbase company and person change webhooks - firmographic updates, M&A, and leadership or employment changes - and land them in an operational store for real-time account alerts.
  • 04 Push warehouse-computed account scores, custom fields, and audiences into Demandbase via the Data Import API so ABM campaigns and sales plays target the segments the warehouse defines.

Common sync patterns

Suppression and consent stay aligned

Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Databricks holds the current state for auditing.

Enrich records with warehouse context

Product-usage counts, plan tier, region, or account owner computed in Databricks appear on the matching record in Demandbase, so targeting, routing, and personalization use up-to-date context.

Activate a modeled audience

A segment or score built in Databricks — high-intent accounts, churn risk, a lifetime-value tier — lands as an audience or contact field in Demandbase, so campaigns target the people your data actually points to instead of a static export.

What you can sync between Databricks and Demandbase

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 Demandbase objects How this pairing syncs
Volumes Unity Catalog file storage used for staging bulk loads. Company Details (B2B enrichment) Firmographics, technographics, competitors, and corporate family tree fetched by domain or name via the B2B Company Search and Details endpoints; read-only enrichment. Volumes is specific to Databricks and Company Details (B2B enrichment) to Demandbase — each maps to any object or custom field on the other side.
SQL Warehouses The compute endpoint a sync connects to for query execution. Change Subscriptions Company firmographic, company news, family-tree (ownership), and DB person employment subscriptions delivered as webhook alerts with a signing secret; the real-time change feed. SQL Warehouses is specific to Databricks and Change Subscriptions to Demandbase — each maps to any object or custom field on the other side.
Change Data Feed Row-level change records on Delta tables that drive incremental reads. Accounts Company/account records with firmographics, intent, and Demandbase qualification and engagement scores; exported via the Data Export API and imported or updated via the Data Import API. Change Data Feed is specific to Databricks and Accounts to Demandbase — each maps to any object or custom field on the other side.
Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. Opportunities Opportunity records synced from the CRM into Demandbase; exported with calculated insights and imported or updated through the Data Import API. Read and write. Catalogs is specific to Databricks and Opportunities to Demandbase — each maps to any object or custom field on the other side.
Schemas Group tables and views; syncs typically target a dedicated schema per source system. People (Persons) Contact/person records with verified business email, title, seniority, and quality grades; fetched and matched via the B2B Contact endpoints and exported or imported. Schemas is specific to Databricks and People (Persons) to Demandbase — each maps to any object or custom field on the other side.
Delta Tables The primary read and write target; operational data lands here as managed or external tables. Activities Engagement and custom activity records (web, campaign, intent); exported via Data Export and pushed in through the Data Import API using custom activity types. Delta Tables is specific to Databricks and Activities to Demandbase — each maps to any object or custom field on the other side.

How changes propagate between Databricks and Demandbase

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.

Databricks Demandbase Sub-second propagation

DetectionChanges in Databricks are captured at the source via change data capture — no polling loop against its API. Delta Lake Change Data Feed for row-level changes.

DeliveryEach detected change is written to Demandbase through its API, with automatic retries and rate-limit backoff.

Demandbase Databricks Sub-second propagation

DetectionDemandbase notifies Stacksync of record changes through webhook events. Subscription API webhooks - company firmographic, company news, family-tree (ownership), and person employment-change alerts to a configurable URL.

DeliveryEach detected change is applied to Databricks as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Databricks: Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits.
  • Demandbase: Credit-based per API call; bulk jobs accept up to 10,000 records per submission, CSV uploads up to 5GB, and result URLs stay valid 24 hours; subscription alerts page up to 5,000 entities and list endpoints up to 100 per page.
What ships with Databricks ⇄ Demandbase

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Demandbase

Integration surface
REST APIs (Demandbase One) - a B2B API (company/contact search, details, and match with async bulk enrichment jobs), a read-only Data Export API and a write-capable Data Import API (both async bulk jobs), and a Subscription API for webhook change alerts.
Authentication
JWT bearer tokens minted from Demandbase One API Key Sets at the platform level; each credential set expires after 8 hours and is rotated. Legacy single-user API tokens are deprecated.
Change detection
Subscription API webhooks - company firmographic, company news, family-tree (ownership), and person employment-change alerts to a configurable URL secured with a signing secret; bulk reads run as async export jobs (submit, poll, download). No log-based CDC.
Capabilities
read · write · webhooks
Rate limits
Credit-based per API call; bulk jobs accept up to 10,000 records per submission, CSV uploads up to 5GB, and result URLs stay valid 24 hours; subscription alerts page up to 5,000 entities and list endpoints up to 100 per page.
How it works

How to connect Databricks to Demandbase — 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 Demandbase 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
    Demandbase connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Databricks and Demandbase 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 ⇄ Demandbase
    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 Demandbase
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Databricks and Demandbase integration FAQ

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 510 integrations available for Databricks and Demandbase.

Popular · 8 of 510
Coworkers laughing in front of a laptop in a casual office setting

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