Real-time
Two-way sync
Changes in Ceridian Dayforce or Ironclad instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Business productivity
Ceridian Dayforce to Ironclad integration — real-time, two-way sync
Keep Ceridian Dayforce and Ironclad 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 Ironclad
Keep the people, teams, and status that Ironclad and Ceridian Dayforce share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Ironclad keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Ceridian Dayforce is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Workflow Documents, Workflows, Records, Entities in Ironclad with Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries, Employee Schedules in Ceridian Dayforce bi-directionally and in real time. A person added, moved, or offboarded in Ceridian Dayforce creates or updates the matching user in Ironclad within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Ironclad captures details of its own, such as a corrected contact or a login identity, those can flow back to Ceridian Dayforce in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
Common use cases
- 01 Push Obligations and renewal dates from Ironclad into a finance or task system so post-signature commitments and renewals are tracked and actioned on time.
- 02 Pull executed contract PDFs from Records attachments into a document store or archive as each workflow completes.
- 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
Onboarding: access ready on day one
A new hire recorded in Ceridian Dayforce creates the matching user in Ironclad with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
Offboarding: no standing access after a departure
When someone is marked as leaving in Ceridian Dayforce, the matching account in Ironclad is deactivated or flagged, so departures do not leave open access behind.
One employee directory
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
What you can sync between Ceridian Dayforce and Ironclad
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 | Ironclad 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. | Webhooks Event subscriptions that push workflow, approval, signature, document, and comment changes to Stacksync in near real time; created, listed, and deleted through the API across 40+ event types. | Employee (HR / Person Details) is specific to Ceridian Dayforce and Webhooks to Ironclad — 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. | Workflow Approvals Per-workflow approval requests and their state; read to report approval status and cycle time, and status changes arrive live through the workflow_approval_status_changed event. | Employment Status is specific to Ceridian Dayforce and Workflow Approvals to Ironclad — 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. | Signature Packets The e-signature packets on a workflow (sent, signatures collected, fully signed); read to track signing progress, with packet events delivered by webhook for real-time status. | Work Assignments is specific to Ceridian Dayforce and Signature Packets to Ironclad — 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. | Workflow Documents Draft and executed documents attached to a workflow; retrieved to pull generated or signed files out into a document store or archive. | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Workflow Documents to Ironclad — 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. | Workflows The core unit of Ironclad: a live contract process (NDA, MSA, order form) moving through creation, review, approval, and signature. Launched via POST, updated via PATCH, and read for status, so contract processes move two-way between Ironclad and a database, CRM, or ERP. | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Workflows to Ironclad — 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. | Records The Repository of executed and stored contracts with metadata (value, counterparty, key dates, type) and attachments; full create, read, update, and delete so signed-contract data and PDFs sync to a warehouse, ERP, or CRM. | Employee Schedules is specific to Ceridian Dayforce and Records to Ironclad — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Ironclad
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 Ironclad Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Ironclad through its API, with automatic retries and rate-limit backoff.
Ironclad Ceridian Dayforce Sub-second propagation
DetectionIronclad notifies Stacksync of record changes through webhook events. Native webhook subscriptions (POST /webhooks) fire on 40+ workflow, approval, signature, document, and comment events, and Ironclad retries a failing.
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.
- Ironclad: Limits are enforced per account per minute by endpoint: GET Workflows 400 and POST/PATCH Workflows 40; GET Records 600 and POST/PATCH Records 200; GET Entities 600 and POST/PATCH Entities 200; Webhooks 600; all other endpoints 800. Exceeding a limit returns HTTP 429, and Ironclad recommends exponential backoff with jitter.
What ships with Ceridian Dayforce ⇄ Ironclad
Connect Ceridian Dayforce and Ironclad for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Ironclad connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Ironclad 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 Ironclad record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Ironclad 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 Ironclad.
How the Ceridian Dayforce and Ironclad 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.
Ironclad
- Integration surface
- REST/JSON Public API (CLM API) at https://na1.ironcladapp.com/public/api/v1 (NA1 and EU1 regions plus a demo/sandbox), with a native Webhooks subscription API; described by an OpenAPI 3.1 spec.
- Authentication
- OAuth 2.0 - Authorization Code grant (PKCE for public clients) and Client Credentials grant for server-to-server; access tokens are Bearer, expire after 6 hours, and every endpoint is gated by a resource scope. The legacy static API bearer token was deprecated on 2024-11-22.
- Change detection
- Native webhook subscriptions (POST /webhooks) fire on 40+ workflow, approval, signature, document, and comment events, and Ironclad retries a failing endpoint up to 10 times over about 13.6 hours with exponential backoff. Otherwise poll the list endpoints by last-updated. There is no database change-data-capture log.
- Capabilities
- read · write · webhooks
- Rate limits
- Limits are enforced per account per minute by endpoint: GET Workflows 400 and POST/PATCH Workflows 40; GET Records 600 and POST/PATCH Records 200; GET Entities 600 and POST/PATCH Entities 200; Webhooks 600; all other endpoints 800. Exceeding a limit returns HTTP 429, and Ironclad recommends exponential backoff with jitter.
How it works
How to connect Ceridian Dayforce to Ironclad — 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 Ironclad 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
Ironclad
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Ironclad 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 ⇄ IroncladCustomers 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 IroncladCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Ironclad integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Ironclad: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Employee (HR / Person Details) and Employment Status), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Ceridian Dayforce and Ironclad connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Ceridian Dayforce–Ironclad integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Ceridian Dayforce and Ironclad. 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 Ironclad: Native webhook subscriptions (POST /webhooks) fire on 40+ workflow, approval, signature, document, and comment events, and Ironclad retries a failing endpoint up to 10 times over about 13.6 hours with exponential backoff. Otherwise poll the list endpoints by last-updated. There is no database change-data-capture log. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Ironclad side: Workflow Documents, Workflows, Records, Entities, plus custom fields where Ironclad exposes them. On the Ceridian Dayforce side: Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries, Employee Schedules. 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.
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 511 integrations available for Ceridian Dayforce and Ironclad.
Popular · 7 of 511
-
Ceridian Dayforce ⇄ Atlassian -
Ceridian Dayforce ⇄ Braze -
Ceridian Dayforce ⇄ ConnectWise -
Ironclad ⇄ Ukg Ready -
Ironclad ⇄ BambooHR -
Ironclad ⇄ Success Factors -
Ironclad ⇄ Hibob
No integrations match .
