Two-way sync
Changes in Ceridian Dayforce or Folk CRM instantly reflect in both systems. No stale data, no manual imports.
Keep Ceridian Dayforce and Folk 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.
Folk 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 People, Companies, Groups, Custom fields in Folk CRM 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 Folk CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
When Ceridian Dayforce records a new hire, a matching user or owner is created in Folk CRM, so a new rep can start working accounts without waiting on a manual setup ticket.
When a person changes team, manager, or region in Ceridian Dayforce, their accounts and territory assignments in Folk CRM update to match, so pipeline stays with the right owner.
When Ceridian Dayforce marks a worker as departed, the matching user in Folk CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.
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 | Folk CRM objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Work Assignments is specific to Ceridian Dayforce and Custom fields to Folk 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. | Notes Free-text context attached to people and companies, readable for reporting. | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Notes to Folk 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. | Reminders Follow-up items that can be created from external triggers. | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Reminders to Folk CRM — 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. | People Contact records; the primary entity synced with outreach and enrichment tools. | Employee Schedules is specific to Ceridian Dayforce and People to Folk CRM — 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. | Companies Organization records linked to people and kept aligned with billing or CS systems. | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Companies to Folk CRM — 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. | Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Time Away From Work & Balances is specific to Ceridian Dayforce and Groups to Folk CRM — each maps to any object or custom field on the other side. |
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.
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Folk CRM through its API, with automatic retries and rate-limit backoff.
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
DeliveryEach detected change is written to Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Folk CRM connection.
Changes in Ceridian Dayforce or Folk CRM instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Ceridian Dayforce or Folk CRM data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Ceridian Dayforce or Folk CRM record.
Track your Ceridian Dayforce ⇄ Folk CRM sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Ceridian Dayforce and Folk CRM.
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.
Authenticate Ceridian Dayforce and Folk CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Ceridian Dayforce and Folk 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Folk CRM: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Work Assignments and Compensation Summary & Pay Adjustments), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Ceridian Dayforce and Folk CRM. 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 Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Folk CRM side: People, Companies, Groups, Custom fields, plus custom fields where Folk CRM exposes them. On the Ceridian Dayforce side: Employee (HR / Person Details), Employment Status, Work Assignments, Compensation Summary & Pay Adjustments. 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 Folk 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 Folk CRM, so a new rep can start working accounts without waiting on a manual setup ticket.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 416 integrations available for Ceridian Dayforce and Folk CRM.