Real-time
Real-time sync
Changes in Databricks or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ CRM
Databricks to Dun And Bradstreet integration — real-time data sync
Keep Databricks and Dun And Bradstreet 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 Dun And Bradstreet
Flow Dun And Bradstreet data into Databricks in real time — no exports, no schedulers, no custom scripts.
Dun And Bradstreet 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 Dun And Bradstreet — 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. Financial Strength & Risk Insight (Data Block), Identity Resolution (Match / cleanseMatch), Criteria Search, Monitoring Notifications from Dun And Bradstreet land in Databricks as live tables, updated within seconds, and columns computed in Databricks write back to fields in Dun And Bradstreet. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Common use cases
- 01 Poll D&B Monitoring notifications for a registered portfolio of key accounts and suppliers and update the CRM or warehouse record whenever a firmographic or risk score changes.
- 02 Pull D&B risk and credit signals (PAYDEX, Failure Score, D&B Rating) into a warehouse for credit-risk, vendor-risk, and third-party-risk analytics.
- 03 Land CRM and ERP records in Delta tables continuously so lakehouse models work from current operational data.
- 04 Use Change Data Feed to propagate only changed rows to downstream apps instead of full-table scans.
Common sync patterns
A single customer view
Join Dun And Bradstreet'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 Dun And Bradstreet are queryable in Databricks moments after they change, so dashboards stop lagging the reality they describe.
What you can sync between Databricks and Dun And Bradstreet
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 | Dun And Bradstreet objects | How this pairing syncs | |
|---|---|---|---|
| Volumes Unity Catalog file storage used for staging bulk loads. | Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. | Volumes is specific to Databricks and Monitoring Notifications to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| SQL Warehouses The compute endpoint a sync connects to for query execution. | Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. | SQL Warehouses is specific to Databricks and Company Information (Data Block) to Dun And Bradstreet — 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. | Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. | Change Data Feed is specific to Databricks and Principals & Contacts (Data Block) to Dun And Bradstreet — 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. | Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Catalogs is specific to Databricks and Company Hierarchy & Connections (Family Tree) to Dun And Bradstreet — 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. | Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. | Schemas is specific to Databricks and Financial Strength & Risk Insight (Data Block) to Dun And Bradstreet — 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. | Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. | Delta Tables is specific to Databricks and Identity Resolution (Match / cleanseMatch) to Dun And Bradstreet — each maps to any object or custom field on the other side. |
How changes propagate between Databricks and Dun And Bradstreet
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 Dun And Bradstreet 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.
DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating Databricks records.
Dun And Bradstreet Databricks Interval-based propagation
DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).
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.
- Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
What ships with Databricks ⇄ Dun And Bradstreet
Connect Databricks and Dun And Bradstreet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–Dun And Bradstreet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Databricks or Dun And Bradstreet 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 Dun And Bradstreet record.
Observability
Monitoring
Track your Databricks ⇄ Dun And Bradstreet 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 Dun And Bradstreet.
How the Databricks and Dun And Bradstreet 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
Dun And Bradstreet
- Integration surface
- D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring
- Authentication
- OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours.
- Change detection
- Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
- Capabilities
- read
- Rate limits
- Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
How it works
How to connect Databricks to Dun And Bradstreet — 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 Dun And Bradstreet 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
Dun And Bradstreet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Databricks and Dun And Bradstreet 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 ⇄ Dun And BradstreetCustomers 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 Dun And BradstreetCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Databricks and Dun And Bradstreet integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Databricks and Dun And Bradstreet — Dun And Bradstreet is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Dun And Bradstreet is a read-only source, so this integration runs one-way: Stacksync reads from Dun And Bradstreet in real time and delivers into Databricks. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for Databricks and Dun And Bradstreet: A single customer view; Cleanup that sticks; CRM analytics on live data. Join Dun And Bradstreet's relationship data with billing, product, and support data in Databricks to build the customer picture the CRM alone cannot hold.
-
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. Dun And Bradstreet: D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring. Authentication: OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours. Stacksync manages authentication, retries, and rate limits on both sides.
-
Dun And Bradstreet: Change detection uses D&B Monitoring: register a portfolio of DUNS and pull change notices (retained ~60 days) or receive bundled push delivery set up with your D&B rep - not a standard HTTP webhook. Databricks: SQL warehouses expose standard JDBC/ODBC connectivity plus a REST statement-execution endpoint, so tools can integrate without cluster management. Stacksync's field mapping accounts for these differences between Databricks and Dun And Bradstreet without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Databricks and Dun And Bradstreet records are not retained after a sync operation.
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
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 527 integrations available for Databricks and Dun And Bradstreet.
Popular · 7 of 527
-
Databricks ⇄ Intercom -
Databricks ⇄ Kommo -
Databricks ⇄ Kustomer -
Databricks ⇄ Nimble -
Dun And Bradstreet ⇄ Apache Druid -
Dun And Bradstreet ⇄ Apache Hive -
Dun And Bradstreet ⇄ Apache Impala
No integrations match .
