Real-time
Real-time sync
Changes in Docusign or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Docusign to Dun And Bradstreet integration — real-time data sync
Keep Docusign 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 Docusign and Dun And Bradstreet
Flow Dun And Bradstreet data into Docusign 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 Docusign, so Docusign 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 Docusign 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 Push signed Documents and the certificate of completion into a document store or database keyed by Envelope Custom Fields for audit and retrieval.
- 02 Mirror Envelope Custom Fields and Folder placement into a reporting database to analyze agreement volume, cycle time, and stalled signatures.
- 03 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.
- 04 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.
Common sync patterns
Where Docusign can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Dun And Bradstreet sync into Docusign, so people working there have the context without switching tools.
Where Docusign supplies contact or company data
Enriched fields land directly on records in Dun And Bradstreet, and refreshes keep them from going stale.
What you can sync between Docusign 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.
| Docusign objects | Dun And Bradstreet objects | How this pairing syncs | |
|---|---|---|---|
| Envelopes The core container for a signature request — documents, recipients, routing, and status; read status and metadata two-way, and create/send new envelopes. | 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. | Envelopes is specific to Docusign and Financial Strength & Risk Insight (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Recipients Signers, carbon copies, and agents on an envelope, each with a routing order and status; read recipient progress, write recipient lists when an envelope is created. | 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. | Recipients is specific to Docusign and Identity Resolution (Match / cleanseMatch) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Documents The PDF files inside an envelope plus the certificate of completion; read signed output out to a store, or supply source documents on create. | 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. | Documents is specific to Docusign and Criteria Search to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Templates Reusable envelope definitions with predefined recipients and tab placement; read to map fields and referenced by ID to generate new envelopes. | 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. | Templates is specific to Docusign and Monitoring Notifications to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Tabs (form fields) Signature, initial, date, text, and checkbox fields on a document; they carry the data a signer entered and are read out into databases. | 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. | Tabs (form fields) is specific to Docusign and Company Information (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Envelope Custom Fields Text and list metadata used to tag envelopes for reporting; synced to a warehouse or CRM to key and categorize agreements. | 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. | Envelope Custom Fields is specific to Docusign and Principals & Contacts (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side. |
How changes propagate between Docusign 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.
Docusign Dun And Bradstreet Sub-second propagation
DetectionDocusign notifies Stacksync of record changes through webhook events. Docusign Connect webhooks push envelope and recipient status-change events in real time.
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 Docusign records.
Dun And Bradstreet Docusign 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 Docusign through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Docusign: Default 3,000 API requests per hour per account across all integrations, plus a burst limit of 500 calls per 30-second window; usage is exposed via the RateLimit and BurstLimit response headers.
- 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 Docusign ⇄ Dun And Bradstreet
Connect Docusign and Dun And Bradstreet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Docusign–Dun And Bradstreet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Docusign 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 Docusign or Dun And Bradstreet record.
Observability
Monitoring
Track your Docusign ⇄ 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 Docusign and Dun And Bradstreet.
How the Docusign and Dun And Bradstreet connectors work
Docusign
- Integration surface
- eSignature REST API v2.1 (plus Docusign Connect webhooks; separate CLM, Rooms, and Admin APIs)
- Authentication
- OAuth 2.0 — Authorization Code Grant for interactive apps, or JWT Grant (RSA key pair with user impersonation) for server-to-server integrations
- Change detection
- Docusign Connect webhooks push envelope and recipient status-change events in real time; polling is the fallback and is limited to once every 15 minutes per envelope
- Capabilities
- read · write · webhooks
- Rate limits
- Default 3,000 API requests per hour per account across all integrations, plus a burst limit of 500 calls per 30-second window; usage is exposed via the RateLimit and BurstLimit response headers
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 Docusign 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 Docusign 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.
Docusign
connected
Dun And Bradstreet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Docusign 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 · Docusign ⇄ 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.
Docusign Dun And BradstreetCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Docusign and Dun And Bradstreet integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Docusign 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.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Docusign and Dun And Bradstreet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Docusign–Dun And Bradstreet integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Docusign and Dun And Bradstreet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Docusign: Docusign Connect webhooks push envelope and recipient status-change events in real time; polling is the fallback and is limited to once every 15 minutes per envelope. On Dun And Bradstreet: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Docusign side: Documents, Templates, Tabs (form fields), Envelope Custom Fields, plus custom fields where Docusign exposes them. On the Dun And Bradstreet side: Criteria Search, Monitoring Notifications, Company Information (Data Block), Principals & Contacts (Data Block). 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 Docusign. Field mapping and monitoring work the same as for two-way pairs.
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 Docusign and Dun And Bradstreet.
Popular · 8 of 488
-
Docusign ⇄ Kustomer -
Docusign ⇄ Nimble -
Docusign ⇄ Nutshell -
Docusign ⇄ Oracle CX Sales -
Dun And Bradstreet ⇄ Quip -
Dun And Bradstreet ⇄ Smartsheet -
Dun And Bradstreet ⇄ Sysaid -
Dun And Bradstreet ⇄ Wrike
No integrations match .
