Skip to content
CRM ⇄ Data warehouse

6sense to Databricks integration — real-time data sync

Keep 6sense and Databricks 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 6sense and Databricks

Flow 6sense data into Databricks in real time — no exports, no schedulers, no custom scripts.

6sense is a read-only source: Stacksync reads its data in real time and delivers it into Databricks, so Databricks always reflects the current state of 6sense — without exports, scripts, or schedulers.

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. Accounts, Segments, Buying Stage Scores, Intent Signals from 6sense land in Databricks as live tables, updated within seconds, and columns computed in Databricks write back to fields in 6sense. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

Common use cases

  • Enrich inbound leads with 6sense firmographic and account-match data before routing.
  • Feed in-market account lists to sales engagement tools to start sequences automatically.
  • 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.

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 6sense 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 6sense, where the people working accounts actually see them.

What you can sync between 6sense and Databricks

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.

6sense objects Databricks objects
Intent Signals Keyword-level research activity used to flag in-market accounts. Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs.
People / Contacts Persona and contact data surfaced for accounts, used to build outreach lists. Volumes Unity Catalog file storage used for staging bulk loads.
Reach Scores Model scores reflecting the level and recency of outreach to an account or contact, used to prioritize follow-up. SQL Warehouses The compute endpoint a sync connects to for query execution.
Accounts Company records enriched with firmographics and intent data, matched to CRM accounts. Change Data Feed Row-level change records on Delta tables that drive incremental reads.
Segments Dynamic account lists built from intent and fit criteria, read out to drive targeting. Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address.
Buying Stage Scores Model-predicted stage per account, synced onto CRM records for prioritization. Schemas Group tables and views; syncs typically target a dedicated schema per source system.
What ships with 6sense ⇄ Databricks

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your 6sense ⇄ Databricks sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between 6sense and Databricks.

How the 6sense and Databricks connectors work

6sense

Integration surface
REST API
Authentication
API key (token passed in request headers)
Change detection
Polling; scores and segment membership are typically refreshed on the platform's model update cadence
Capabilities
read
Rate limits
Subject to the platform's API rate limits, which vary by contracted API package

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
How it works

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

    Choose tables

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

6sense and Databricks 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.

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 6sense and Databricks.

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

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