Real-time
Two-way sync
Changes in Ceridian Dayforce or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Ceridian Dayforce to Twenty CRM integration — real-time, two-way sync
Keep Ceridian Dayforce and Twenty CRM 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 Twenty CRM
Keep the people who own accounts in Twenty CRM 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.
Twenty CRM 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 Custom Objects, Attachments, Workspace Members, People in Twenty CRM 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 Twenty CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Mirror support tickets or tasks between Twenty and an operations tool.
- 02 Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
- 03 Sync time data by posting raw clock entries from a third-party scheduling tool into Dayforce, or pulling Employee Punches and Schedules into a workforce-analytics database.
- 04 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.
Common sync patterns
New team members provisioned when they are hired
When Ceridian Dayforce records a new hire, a matching user or owner is created in Twenty CRM, 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 Twenty CRM update to match, so pipeline stays with the right owner.
Deactivate access when someone leaves
When Ceridian Dayforce marks a worker as departed, the matching user in Twenty CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.
What you can sync between Ceridian Dayforce and Twenty CRM
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 | Twenty CRM 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. | Workspace Members User accounts used for record ownership and assignment mapping. | Time Away From Work & Balances is specific to Ceridian Dayforce and Workspace Members to Twenty CRM — 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. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Employee (HR / Person Details) is specific to Ceridian Dayforce and People to Twenty CRM — 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. | Companies Account-level records that group people and opportunities. | Employment Status is specific to Ceridian Dayforce and Companies to Twenty CRM — 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. | Opportunities Deal records tracked through pipeline stages, synced for forecasting. | Work Assignments is specific to Ceridian Dayforce and Opportunities to Twenty CRM — 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. | Tasks To-dos linked to people, companies, or deals. | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Tasks to Twenty CRM — 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. | Notes Free-form notes attached to records, useful for mirroring activity from other tools. | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Notes to Twenty CRM — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Twenty CRM
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 Twenty CRM Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Twenty CRM through its API, with automatic retries and rate-limit backoff.
Twenty CRM Ceridian Dayforce Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update 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.
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Ceridian Dayforce ⇄ Twenty CRM
Connect Ceridian Dayforce and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Twenty CRM 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 Twenty CRM record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Twenty CRM 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 Twenty CRM.
How the Ceridian Dayforce and Twenty CRM 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.
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Ceridian Dayforce to Twenty CRM — 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 Twenty CRM 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
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Twenty CRM 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 ⇄ Twenty CRMCustomers 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 Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Twenty CRM: 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.
-
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 Twenty CRM: New team members provisioned when they are hired; Ownership and territory follow the org chart; Deactivate access when someone leaves. When Ceridian Dayforce records a new hire, a matching user or owner is created in Twenty CRM, so a new rep can start working accounts without waiting on a manual setup ticket.
-
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. Twenty CRM: GraphQL and REST APIs. Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
-
Twenty CRM: Both GraphQL and REST APIs are generated from the workspace's object schema, so custom objects get the same API surface as standard ones. Ceridian Dayforce: Native Event Notifications (the Dayforce Notification Publisher) cover employee lifecycle events — Hire, Rehire, Terminate (and their cancels) and Workflow Validation — pushed to a receiver service or pulled via unacknowledged-notification queries; the publisher runs about hourly and notifications must be acknowledged. Stacksync's field mapping accounts for these differences between Ceridian Dayforce and Twenty CRM without custom code.
-
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 Twenty CRM records are not retained after a sync operation.
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 435 integrations available for Ceridian Dayforce and Twenty CRM.
Popular · 8 of 435
-
Ceridian Dayforce ⇄ Microsoft Dynamics 365 Sales -
Ceridian Dayforce ⇄ Attio -
Ceridian Dayforce ⇄ Pipedrive -
Ceridian Dayforce ⇄ Zoho CRM -
Twenty CRM ⇄ Ukg Pro -
Twenty CRM ⇄ Greenhouse -
Twenty CRM ⇄ Jobvite -
Twenty CRM ⇄ Lever
No integrations match .
