Skip to content
CRM ⇄ Business productivity

Dun And Bradstreet to Notion integration — real-time data sync

Keep Dun And Bradstreet and Notion 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 Dun And Bradstreet and Notion

Flow Dun And Bradstreet data into Notion 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 Notion, so Notion always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Notion holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Common use cases

  • 01 Sync a Notion content-calendar database with Jira or Linear by mapping status and date properties both directions.
  • 02 Read Notion wiki Pages and their Blocks into a database or search index for internal knowledge retrieval.
  • 03 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.
  • 04 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.

Common sync patterns

Where Notion supplies contact or company data

Enriched fields land directly on records in Dun And Bradstreet, and refreshes keep them from going stale.

Where Notion can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Dun And Bradstreet sync into Notion, so people working there have the context without switching tools.

What you can sync between Dun And Bradstreet and Notion

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.

Dun And Bradstreet objects Notion objects How this pairing syncs
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. Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. Criteria Search is specific to Dun And Bradstreet and Properties to Notion — each maps to any object or custom field on the other side.
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. Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. Monitoring Notifications is specific to Dun And Bradstreet and Blocks to Notion — each maps to any object or custom field on the other side.
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. Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. Company Information (Data Block) is specific to Dun And Bradstreet and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side.
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. Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. Principals & Contacts (Data Block) is specific to Dun And Bradstreet and Users to Notion — each maps to any object or custom field on the other side.
Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Comments to Notion — each maps to any object or custom field on the other side.
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. Files and attachments File-property and file-block values. Notion-hosted URLs are temporary and expire, so files are re-fetched or copied at sync time. Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Files and attachments to Notion — each maps to any object or custom field on the other side.

How changes propagate between Dun And Bradstreet and Notion

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.

Dun And Bradstreet Notion 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 written to Notion through its API, with automatic retries and rate-limit backoff.

Notion Dun And Bradstreet Sub-second propagation

DetectionNotion notifies Stacksync of record changes through webhook events. Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created.

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 Notion records.

Rate-limit considerations

  • 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.
  • Notion: Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
What ships with Dun And Bradstreet ⇄ Notion

Connect Dun And Bradstreet and Notion for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–Notion connection.

Real-time

Real-time sync

Changes in Dun And Bradstreet or Notion instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dun And Bradstreet or Notion 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 Dun And Bradstreet or Notion record.

Observability

Monitoring

Track your Dun And Bradstreet ⇄ Notion sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dun And Bradstreet and Notion.

How the Dun And Bradstreet and Notion connectors work

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.

Notion

Integration surface
REST API (api.notion.com/v1)
Authentication
OAuth 2.0 for public integrations, or an internal integration secret (bearer token); every request must send a Notion-Version header
Change detection
Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created; HMAC-SHA256 signed) plus polling on each page's last_edited_time
Capabilities
read · write · webhooks
Rate limits
Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
How it works

How to connect Dun And Bradstreet to Notion — 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 Dun And Bradstreet and Notion 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
    Dun And Bradstreet connected
    Notion connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dun And Bradstreet and Notion 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 · Dun And Bradstreet ⇄ Notion
    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
    Dun And Bradstreet Notion
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dun And Bradstreet and Notion 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
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 488 integrations available for Dun And Bradstreet and Notion.

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

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