Real-time
Two-way sync
Changes in Ceridian Dayforce or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Ceridian Dayforce to Nutshell integration — real-time, two-way sync
Keep Ceridian Dayforce and Nutshell 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 Ceridian Dayforce and Nutshell
Keep the people who own accounts in Nutshell in step with the workforce records in Ceridian Dayforce, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.
Nutshell 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 Ceridian Dayforce. Ceridian Dayforce 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.
Stacksync syncs Notes, Products, Tags, Users in Nutshell with Time Away From Work & Balances, Employee (HR / Person Details), Employment Status, Work Assignments in Ceridian Dayforce field by field, in real time, and in both directions. You decide which system owns which fields, so Ceridian Dayforce stays authoritative on roles and org structure while Nutshell keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Write subscription or product data from internal systems into Nutshell so reps see account context.
- 02 Mirror tasks and activities into ops tools for cross-team visibility.
- 03 Push new hires (Employee, Employment Status, Work Assignment) from an ATS or onboarding tool into Dayforce with POST once a candidate is hired, pre-fetching valid XRefCodes for department, position, location, and pay group.
- 04 React to Dayforce Event Notifications for hire, rehire, and terminate to provision or disable IdP and app access and update downstream records as the changes post.
Common sync patterns
Where Ceridian Dayforce tracks people the business also engages: contacts stay in sync
A person recorded in Ceridian Dayforce, such as a candidate or applicant, can create or update the matching contact in Nutshell, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
New team members provisioned when they are hired
When Ceridian Dayforce records a new hire, a matching user or owner is created in Nutshell, so a new rep can start working accounts without waiting on a manual setup ticket.
Ownership and territory follow the org chart
When a person changes team, manager, or region in Ceridian Dayforce, their accounts and territory assignments in Nutshell update to match, so pipeline stays with the right owner.
What you can sync between Ceridian Dayforce and Nutshell
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.
| Ceridian Dayforce objects | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| Time Away From Work & Balances Time-off requests and accrual balances read per employee; pulled into scheduling, payroll, or absence-reporting databases and used to reconcile leave against downstream systems. | People Individual contacts, kept consistent with marketing and outreach tools | Time Away From Work & Balances is specific to Ceridian Dayforce and People to Nutshell — each maps to any object or custom field on the other side. | |
| Employee (HR / Person Details) Core worker record keyed by XRefCode; GET Employees returns matching XRefCodes, then a per-employee GET fetches full HR details. New hires are added with POST and edits made with PATCH, so it is read and write. | Companies Account records that group people and leads for account-level syncs | Employee (HR / Person Details) is specific to Ceridian Dayforce and Companies to Nutshell — each maps to any object or custom field on the other side. | |
| Employment Status Effective-dated employment status and type (active, leave, terminated) that drives active/terminated state for downstream provisioning; read, and writable as new dated status records. | Activities Logged calls, meetings, and emails used for engagement reporting | Employment Status is specific to Ceridian Dayforce and Activities to Nutshell — each maps to any object or custom field on the other side. | |
| Work Assignments Effective-dated position, department, location, and org-unit assignment; the most-synced record for org charts, provisioning, and analytics. Read and updatable via PATCH. | Tasks Rep to-dos mirrored into external work-management or reporting systems | Work Assignments is specific to Ceridian Dayforce and Tasks to Nutshell — each maps to any object or custom field on the other side. | |
| Compensation Summary & Pay Adjustments Compensation Summary returns pay rate and frequency for reporting; Employee Pay Adjustments are written as effective-dated records via PATCH to post pay changes back to Dayforce. | Notes Free-text history attached to leads and contacts, replicated for a full timeline | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Notes to Nutshell — each maps to any object or custom field on the other side. | |
| Employee Punches & Raw Clock Entries Time-and-attendance punches; raw clock entries are added with POST and punches removed with DELETE, so time data flows both ways between Dayforce and scheduling or workforce tools. | Products Line items attached to leads, used to sync sold products into billing | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Products to Nutshell — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Nutshell
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.
Ceridian Dayforce Nutshell Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Nutshell through its API, with automatic retries and rate-limit backoff.
Nutshell Ceridian Dayforce Sub-second propagation
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Ceridian Dayforce: Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
- Nutshell: Subject to the platform's API rate limits.
What ships with Ceridian Dayforce ⇄ Nutshell
Connect Ceridian Dayforce and Nutshell for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Nutshell connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Nutshell 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 Ceridian Dayforce or Nutshell record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Nutshell sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Ceridian Dayforce and Nutshell.
How the Ceridian Dayforce and Nutshell connectors work
Ceridian Dayforce
- Integration surface
- 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.
- Change detection
- 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.
- Capabilities
- read · write · webhooks
- Rate limits
- Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
Nutshell
- Integration surface
- JSON-RPC API over HTTPS; a newer REST API is also offered
- Authentication
- HTTP Basic with account email and API key
- Change detection
- webhook subscriptions for record events, with polling as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Ceridian Dayforce to Nutshell — 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 Ceridian Dayforce and Nutshell with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Ceridian Dayforce
connected
Nutshell
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Nutshell 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 · Ceridian Dayforce ⇄ NutshellCustomers 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.
Ceridian Dayforce NutshellCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Nutshell integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Nutshell: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Time Away From Work & Balances and Employee (HR / Person Details)), map fields visually, and changes propagate both ways 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 Nutshell: Webhook subscriptions for record events, with polling as fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Nutshell side: Notes, Products, Tags, Users, plus custom fields where Nutshell exposes them. On the Ceridian Dayforce side: Time Away From Work & Balances, Employee (HR / Person Details), Employment Status, Work Assignments. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Ceridian Dayforce and Nutshell: 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 Nutshell, 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. Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Stacksync manages authentication, retries, and rate limits on both sides.
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 420 integrations available for Ceridian Dayforce and Nutshell.
Popular · 7 of 420
-
Ceridian Dayforce ⇄ SugarCRM -
Ceridian Dayforce ⇄ Twenty CRM -
Ceridian Dayforce ⇄ Veeva CRM -
Ceridian Dayforce ⇄ Vtiger CRM -
Nutshell ⇄ Success Factors -
Nutshell ⇄ Hibob -
Nutshell ⇄ Oracle Fusion Cloud HCM
No integrations match .
