Real-time
Two-way sync
Changes in Ceridian Dayforce or Nimble instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Ceridian Dayforce to Nimble integration — real-time, two-way sync
Keep Ceridian Dayforce and Nimble 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 Nimble
Keep the people who own accounts in Nimble 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.
Nimble 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 Deals, Tasks, Activities, Notes in Nimble with Employee Punches & Raw Clock Entries, Employee Schedules, Org Units, Departments, Jobs & Positions, Time Away From Work & Balances 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 Nimble keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Push product usage or billing flags from internal databases into Nimble custom fields so reps have context before outreach.
- 02 Keep deals aligned between Nimble and an accounting system so invoicing starts when a deal closes.
- 03 Two-way sync of Employee and Work Assignment data (position, department, location, org unit) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR keeps editing in Dayforce.
- 04 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.
Common sync patterns
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 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 Nimble, 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 Nimble, so a new rep can start working accounts without waiting on a manual setup ticket.
What you can sync between Ceridian Dayforce and Nimble
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 | Nimble objects | How this pairing syncs | |
|---|---|---|---|
| Employee Schedules Shift and schedule assignments; created and updated through POST and PATCH schedule endpoints and paged with pageSize, used to push schedules from a WFM tool or pull them for analytics. | Tags Segmentation labels that map to list membership or filters in downstream systems | Employee Schedules is specific to Ceridian Dayforce and Tags to Nimble — each maps to any object or custom field on the other side. | |
| Org Units, Departments, Jobs & Positions Configuration reference data; POST creates org units and departments and PATCH updates job, position, department, and org-unit data. Used to resolve and validate XRefCodes when mapping employee writes. | Custom fields Account-defined contact attributes that carry enrichment or internal identifiers | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Custom fields to Nimble — each maps to any object or custom field on the other side. | |
| 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. | Contacts Person records with multi-value fields for email, phone, and social profiles; the primary sync entity | Time Away From Work & Balances is specific to Ceridian Dayforce and Contacts to Nimble — 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 Stored as contact records with a company record type, so they sync through the same contacts resource | Employee (HR / Person Details) is specific to Ceridian Dayforce and Companies to Nimble — 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. | Deals Pipeline records linked to contacts, synced to keep revenue systems aligned with sales activity | Employment Status is specific to Ceridian Dayforce and Deals to Nimble — 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 To-do items tied to contacts, mirrored into work-management tools or reporting tables | Work Assignments is specific to Ceridian Dayforce and Tasks to Nimble — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Nimble
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 Nimble Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Nimble through its API, with automatic retries and rate-limit backoff.
Nimble Ceridian Dayforce Interval-based propagation
DetectionStacksync polls Nimble for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record modification timestamps.
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.
- Nimble: Subject to per-account API request quotas.
What ships with Ceridian Dayforce ⇄ Nimble
Connect Ceridian Dayforce and Nimble for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Nimble connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Nimble 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 Nimble record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Nimble 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 Nimble.
How the Ceridian Dayforce and Nimble 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.
Nimble
- Integration surface
- REST API (JSON)
- Authentication
- API key; OAuth 2.0 available for registered applications
- Change detection
- polling on record modification timestamps
- Capabilities
- read · write
- Rate limits
- subject to per-account API request quotas
How it works
How to connect Ceridian Dayforce to Nimble — 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 Nimble 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
Nimble
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Nimble 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 ⇄ NimbleCustomers 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 NimbleCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Nimble integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Nimble: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Employee Schedules and Org Units, Departments, Jobs & Positions), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Ceridian Dayforce and Nimble records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Ceridian Dayforce and Nimble connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Ceridian Dayforce–Nimble integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Ceridian Dayforce and Nimble. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
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 Nimble: Polling on record modification timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Nimble side: Deals, Tasks, Activities, Notes, plus custom fields where Nimble exposes them. On the Ceridian Dayforce side: Employee Punches & Raw Clock Entries, Employee Schedules, Org Units, Departments, Jobs & Positions, Time Away From Work & Balances. Stacksync auto-detects both schemas and converts types between the two systems.
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 419 integrations available for Ceridian Dayforce and Nimble.
Popular · 7 of 419
-
Ceridian Dayforce ⇄ Folk CRM -
Ceridian Dayforce ⇄ Freshsales -
Ceridian Dayforce ⇄ Freshworks CRM -
Ceridian Dayforce ⇄ Gladly -
Nimble ⇄ Hibob -
Nimble ⇄ Oracle Fusion Cloud HCM -
Nimble ⇄ Smartrecruiters
No integrations match .
