Skip to content
Data warehouse ⇄ Marketing

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

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

Put modeled data to work and measure what it drives: Databricks and Rollworks 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; Rollworks 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 Schemas, Delta Tables, Views, Materialized Views in Databricks with Reporting and Attribution, Target Account Lists, Account Tiers, Accounts (TAL Items) in Rollworks 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 Rollworks 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 Push a Target Account List from a CRM or warehouse into RollWorks, keeping Accounts (domains) and their Account Tiers aligned as the source data changes.
  • 04 Sync CRM Audience Segments from a database of emails through the Audience API so lists are populated for advertising without manual CSV uploads.

Common sync patterns

Enrich records with warehouse context

Product-usage counts, plan tier, region, or account owner computed in Databricks appear on the matching record in Rollworks, 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 Rollworks, so campaigns target the people your data actually points to instead of a static export.

Keep the contact and audience list current

New and updated contacts, leads, or audience members flow between Databricks and Rollworks, so the marketing audience reflects the people in your warehouse and corrections propagate instead of the two sides drifting apart.

What you can sync between Databricks and Rollworks

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 Rollworks objects How this pairing syncs
Schemas Group tables and views; syncs typically target a dedicated schema per source system. Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. Schemas is specific to Databricks and Reporting and Attribution to Rollworks — 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. Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. Delta Tables is specific to Databricks and Target Account Lists to Rollworks — each maps to any object or custom field on the other side.
Views Curated read-only projections used as sync sources for downstream tools. Account Tiers Groups within a Target Account List; an account belongs to only one tier per list, so tier assignments are written from source-of-truth data to drive tiered targeting. Views is specific to Databricks and Account Tiers to Rollworks — each maps to any object or custom field on the other side.
Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. Materialized Views is specific to Databricks and Accounts (TAL Items) to Rollworks — each maps to any object or custom field on the other side.
Volumes Unity Catalog file storage used for staging bulk loads. Audience Segments CRM (email), custom (cookie or ID), and lookalike segments created via /audience/v1/segments; membership is written from a warehouse with a duration of 1 to 540 days. Volumes is specific to Databricks and Audience Segments to Rollworks — each maps to any object or custom field on the other side.
SQL Warehouses The compute endpoint a sync connects to for query execution. Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. SQL Warehouses is specific to Databricks and Campaigns to Rollworks — each maps to any object or custom field on the other side.

How changes propagate between Databricks and Rollworks

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 Rollworks 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 Rollworks through its API, with automatic retries and rate-limit backoff.

Rollworks Databricks Interval-based propagation

DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.

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.
  • Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
What ships with Databricks ⇄ Rollworks

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Rollworks

Integration surface
REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
Authentication
OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
Change detection
Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
Capabilities
read · write
Rate limits
NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
How it works

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

    Choose tables

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

Databricks and Rollworks 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.

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

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 414 integrations available for Databricks and Rollworks.

Popular · 6 of 414
All Databricks integrations All Rollworks 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