Real-time
Real-time sync
Changes in DuckDB or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
DuckDB to Dun And Bradstreet integration — real-time data sync
Keep DuckDB 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 DuckDB and Dun And Bradstreet
Treat Dun And Bradstreet like part of your database: its records live in DuckDB as real tables, and writes in either place sync to the other in seconds.
Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into DuckDB, so DuckDB always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in DuckDB, where it can be queried and joined like everything else.
Common use cases
- 01 Sync the D&B corporate family tree (parent and subsidiary DUNS) into the CRM so ABM and territory owners see full account hierarchies and roll pipeline up to the global ultimate.
- 02 Build target-account lists with Criteria Search and land the resulting DUNS plus firmographics in a database for outbound and TAM analysis.
- 03 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
- 04 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
Common sync patterns
Query the CRM like a database
Accounts, contacts, and custom objects from Dun And Bradstreet become tables in DuckDB you can join with application data directly.
Product events onto CRM records
Signup, usage, or lifecycle changes written to DuckDB sync onto the matching records in Dun And Bradstreet, giving go-to-market teams live product context.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Dun And Bradstreet API, limits, and retries.
What you can sync between DuckDB 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.
| DuckDB objects | Dun And Bradstreet objects | How this pairing syncs | |
|---|---|---|---|
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Criteria Search Query companies by firmographic criteria (industry, geography, size) and get back a list of D-U-N-S Numbers to enrich; read-only list building. | Tables is specific to DuckDB and Criteria Search to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Views SQL views used to shape or filter data for downstream consumers. | 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. | Views is specific to DuckDB and Monitoring Notifications to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | 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. | External files (Parquet/CSV/JSON) is specific to DuckDB and Company Information (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | 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. | Attached databases is specific to DuckDB and Principals & Contacts (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Database files is specific to DuckDB and Company Hierarchy & Connections (Family Tree) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | 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 DuckDB and Financial Strength & Risk Insight (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side. |
How changes propagate between DuckDB 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.
DuckDB Dun And Bradstreet Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
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 DuckDB records.
Dun And Bradstreet DuckDB 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 DuckDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
- 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 DuckDB ⇄ Dun And Bradstreet
Connect DuckDB and Dun And Bradstreet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Dun And Bradstreet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB 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 DuckDB or Dun And Bradstreet record.
Observability
Monitoring
Track your DuckDB ⇄ 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 DuckDB and Dun And Bradstreet.
How the DuckDB and Dun And Bradstreet connectors work
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
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 DuckDB 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 DuckDB 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.
DuckDB
connected
Dun And Bradstreet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB 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 · DuckDB ⇄ 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.
DuckDB Dun And BradstreetCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Dun And Bradstreet integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between DuckDB 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.
-
On the Dun And Bradstreet side: Principals & Contacts (Data Block), Company Hierarchy & Connections (Family Tree), Financial Strength & Risk Insight (Data Block), Identity Resolution (Match / cleanseMatch), plus custom fields where Dun And Bradstreet exposes them. On the DuckDB side: Tables, Views, External files (Parquet/CSV/JSON), Attached databases. Stacksync auto-detects both schemas and converts types between the two systems.
-
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 DuckDB. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for DuckDB and Dun And Bradstreet: Query the CRM like a database; Product events onto CRM records; Internal tools without API code. Accounts, contacts, and custom objects from Dun And Bradstreet become tables in DuckDB you can join with application data directly.
-
DuckDB: In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default. Authentication: None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). 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: D&B Direct+ is a reference-data / enrichment API - read and enrich only. You retrieve firmographics, contacts, hierarchy, and risk scores for a D-U-N-S Number; there is no endpoint to write business records back into D&B. DuckDB: DuckDB runs in-process like SQLite; there is no server, so integrations embed the engine or operate on the single-file databases it produces. Stacksync's field mapping accounts for these differences between DuckDB and Dun And Bradstreet without custom code.
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 425 integrations available for DuckDB and Dun And Bradstreet.
Popular · 7 of 425
-
DuckDB ⇄ Salesforce -
DuckDB ⇄ HubSpot -
DuckDB ⇄ Attio -
Dun And Bradstreet ⇄ Amazon Aurora -
Dun And Bradstreet ⇄ Amazon Lightsail -
Dun And Bradstreet ⇄ Apache Cassandra -
Dun And Bradstreet ⇄ Azure Cosmos DB
No integrations match .
