Skip to content
Human resources ⇄ CRM

Ceridian Dayforce to Kustomer integration — real-time, two-way sync

Keep Ceridian Dayforce and Kustomer 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 Kustomer

Keep the people who own accounts in Kustomer 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.

Kustomer 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, Customers, Conversations, Messages in Kustomer with Employee (HR / Person Details), Employment Status, Work Assignments, Compensation Summary & Pay Adjustments 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 Kustomer keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Escalate conversation-derived signals into the CRM as tasks or opportunities
  • 02 Sync customers bi-directionally with the CRM and ERP so agents see deal, billing, and subscription context on the timeline
  • 03 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.
  • 04 Replicate Compensation Summary and pay data into a warehouse for headcount, labor-cost, and compensation reporting without manual BI exports.

Common sync patterns

Deactivate access when someone leaves

When Ceridian Dayforce marks a worker as departed, the matching user in Kustomer 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 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 Kustomer, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

What you can sync between Ceridian Dayforce and Kustomer

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 Kustomer objects How this pairing syncs
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 Organization records group customers and map to CRM accounts. Employee (HR / Person Details) is specific to Ceridian Dayforce and Companies to Kustomer — 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. Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. Employment Status is specific to Ceridian Dayforce and Custom Objects (Klasses) to Kustomer — 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. Users Agent records map conversation ownership to people in other systems. Work Assignments is specific to Ceridian Dayforce and Users to Kustomer — 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. Teams Team assignments support routing parity and reporting. Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Teams to Kustomer — 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. Tags Labels on conversations and customers sync for categorization and analytics. Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Tags to Kustomer — each maps to any object or custom field on the other side.
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. Notes Internal annotations carry context alongside synced conversations. Employee Schedules is specific to Ceridian Dayforce and Notes to Kustomer — each maps to any object or custom field on the other side.

How changes propagate between Ceridian Dayforce and Kustomer

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 Kustomer Sub-second propagation

DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.

DeliveryEach detected change is written to Kustomer through its API, with automatic retries and rate-limit backoff.

Kustomer Ceridian Dayforce Sub-second propagation

DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.

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.
  • Kustomer: Subject to the platform's API rate limits.
What ships with Ceridian Dayforce ⇄ Kustomer

Connect Ceridian Dayforce and Kustomer for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Kustomer connection.

Real-time

Two-way sync

Changes in Ceridian Dayforce or Kustomer instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Ceridian Dayforce or Kustomer 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 Kustomer record.

Observability

Monitoring

Track your Ceridian Dayforce ⇄ Kustomer 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 Kustomer.

How the Ceridian Dayforce and Kustomer 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.
Ceridian Dayforce setup guide

Kustomer

Integration surface
REST API
Authentication
API key used as a bearer token, scoped by role
Change detection
Outbound webhooks on record events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits
How it works

How to connect Ceridian Dayforce to Kustomer — 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.

  1. 01

    Connect your apps

    Authenticate Ceridian Dayforce and Kustomer with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Ceridian Dayforce connected
    Kustomer connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Ceridian Dayforce and Kustomer 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Ceridian Dayforce ⇄ Kustomer
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Ceridian Dayforce Kustomer
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Ceridian Dayforce and Kustomer integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 418 integrations available for Ceridian Dayforce and Kustomer.

Popular · 7 of 418
All Ceridian Dayforce integrations All Kustomer integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own