Real-time
Real-time sync
Changes in Dun And Bradstreet or Greenhouse instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Dun And Bradstreet to Greenhouse integration — real-time data sync
Keep Dun And Bradstreet and Greenhouse 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 Greenhouse
Flow Dun And Bradstreet data into Greenhouse 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 Greenhouse, so Greenhouse always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
Dun And Bradstreet runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Greenhouse. Greenhouse is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
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 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
- 04 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.
Common sync patterns
Deactivate access when someone leaves
When Greenhouse marks a worker as departed, the matching user in Dun And Bradstreet is flagged or deactivated, so former employees do not keep CRM access after their last day.
One directory of people
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
Where Greenhouse tracks people the business also engages: contacts stay in sync
A person recorded in Greenhouse, such as a candidate or applicant, can create or update the matching contact in Dun And Bradstreet, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
What you can sync between Dun And Bradstreet and Greenhouse
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 | Greenhouse 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. | Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. | Criteria Search is specific to Dun And Bradstreet and Scheduled Interviews to Greenhouse — 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. | Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. | Monitoring Notifications is specific to Dun And Bradstreet and Users to Greenhouse — 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. | Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. | Company Information (Data Block) is specific to Dun And Bradstreet and Departments and Offices to Greenhouse — 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. | Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. | Principals & Contacts (Data Block) is specific to Dun And Bradstreet and Candidates to Greenhouse — 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. | Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. | Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Applications to Greenhouse — 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. | Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. | Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Jobs to Greenhouse — each maps to any object or custom field on the other side. |
How changes propagate between Dun And Bradstreet and Greenhouse
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 Greenhouse 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 Greenhouse through its API, with automatic retries and rate-limit backoff.
Greenhouse Dun And Bradstreet Sub-second propagation
DetectionGreenhouse notifies Stacksync of record changes through webhook events. HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after /.
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 Greenhouse 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.
- Greenhouse: Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
What ships with Dun And Bradstreet ⇄ Greenhouse
Connect Dun And Bradstreet and Greenhouse for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–Greenhouse connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dun And Bradstreet or Greenhouse 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 Greenhouse record.
Observability
Monitoring
Track your Dun And Bradstreet ⇄ Greenhouse 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 Greenhouse.
How the Dun And Bradstreet and Greenhouse 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.
Greenhouse
- Integration surface
- Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import)
- Authentication
- HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user
- Change detection
- HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters
- Capabilities
- read · write · webhooks
- Rate limits
- Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
How it works
How to connect Dun And Bradstreet to Greenhouse — 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 Dun And Bradstreet and Greenhouse with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Dun And Bradstreet
connected
Greenhouse
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dun And Bradstreet and Greenhouse 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 · Dun And Bradstreet ⇄ GreenhouseCustomers 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.
Dun And Bradstreet GreenhouseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dun And Bradstreet and Greenhouse integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Dun And Bradstreet and Greenhouse — 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.
-
Yes — Stacksync ships production-grade connectors for both Dun And Bradstreet and Greenhouse. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection 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. On Greenhouse: HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Dun And Bradstreet side: Financial Strength & Risk Insight (Data Block), Identity Resolution (Match / cleanseMatch), Criteria Search, Monitoring Notifications, plus custom fields where Dun And Bradstreet exposes them. On the Greenhouse side: Applications, Jobs, Offers, Scorecards. 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 Greenhouse. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for Dun And Bradstreet and Greenhouse: Deactivate access when someone leaves; One directory of people; Where Greenhouse tracks people the business also engages: contacts stay in sync. When Greenhouse marks a worker as departed, the matching user in Dun And Bradstreet is flagged or deactivated, so former employees do not keep CRM access after their last day.
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
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 483 integrations available for Dun And Bradstreet and Greenhouse.
Popular · 8 of 483
-
Dun And Bradstreet ⇄ Ukg Pro -
Dun And Bradstreet ⇄ Jobvite -
Dun And Bradstreet ⇄ Lever -
Dun And Bradstreet ⇄ Namely -
Greenhouse ⇄ Freshsales -
Greenhouse ⇄ Freshworks CRM -
Greenhouse ⇄ Gladly -
Greenhouse ⇄ Gorgias
No integrations match .
