Ceridian Dayforce to Dun And Bradstreet integration — real-time data sync

Yes. Stacksync provides a managed, real-time integration between Ceridian Dayforce 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.

Change detection on Ceridian Dayforce: No CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged. 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 Dun And Bradstreet side: Company Hierarchy & Connections (Family Tree), Financial Strength & Risk Insight (Data Block), Identity Resolution (Match / cleanseMatch), Criteria Search, plus custom fields where Dun And Bradstreet exposes them. On the Ceridian Dayforce side: Employment Status, Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries. 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 Ceridian Dayforce. Field mapping and monitoring work the same as for two-way pairs.

Common patterns for Ceridian Dayforce and Dun And Bradstreet: Where Ceridian Dayforce tracks people the business also engages: contacts stay in sync; New team members provisioned when they are hired; Ownership and territory follow the org chart. A person recorded in Ceridian Dayforce, 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.

Ceridian Dayforce: REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads. Authentication: HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account. 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.