Real-time
Two-way sync
Changes in Agiloft or Ceridian Dayforce instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Human resources
Agiloft to Ceridian Dayforce integration — real-time, two-way sync
Keep Agiloft and Ceridian Dayforce 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 Agiloft and Ceridian Dayforce
Keep the people, teams, and status that Agiloft 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 Agiloft 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 Companies, People, Attachments, Approvals in Agiloft with Org Units, Departments, Jobs & Positions, Time Away From Work & Balances, Employee (HR / Person Details), Employment Status 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 Agiloft within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Agiloft 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 Two-way sync Contracts between Agiloft and an ERP or warehouse so value, renewal dates, and status stay current without manual re-keying.
- 02 Push generated documents and executed PDFs into Agiloft Attachments from a document system, or pull signed contracts out for archival.
- 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
Where Agiloft routes or assigns work by person: assignments follow the org
When someone changes teams or managers in Ceridian Dayforce, the queues, ownership, or approvals in Agiloft update to match, so work reaches whoever holds the role now.
Onboarding: access ready on day one
A new hire recorded in Ceridian Dayforce creates the matching user in Agiloft 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 Agiloft is deactivated or flagged, so departures do not leave open access behind.
What you can sync between Agiloft and Ceridian Dayforce
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.
| Agiloft objects | Ceridian Dayforce objects | How this pairing syncs | |
|---|---|---|---|
| Companies Records for every organization - counterparties, vendors, customers - linked to contracts and people; read and written to keep account master data aligned with a CRM or ERP. | 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. | Companies is specific to Agiloft and Employee Punches & Raw Clock Entries to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| People Parent table for individuals, split into Employees (internal users) and Contacts (external company contacts); synced to map signers, approvers, and account owners to CRM or HR records. | 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 is specific to Agiloft and Employee Schedules to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Attachments File records holding the executed contract PDFs and supporting documents linked to a contract; read to pull signed files out, or written to push generated documents in. | 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. | Attachments is specific to Agiloft and Org Units, Departments, Jobs & Positions to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Approvals Per-record approval instances generated from Approval Templates and Workflows; read to report approval status and cycle time, or written to trigger and record decisions. | 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. | Approvals is specific to Agiloft and Time Away From Work & Balances to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Tasks Assigned action items with owners, due dates, and states tied to contracts or projects; synced two-way to surface Agiloft work inside a PM or operations system. | 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. | Tasks is specific to Agiloft and Employee (HR / Person Details) to Ceridian Dayforce — each maps to any object or custom field on the other side. | |
| Clause Library Reusable, approved contract clauses with metadata and categories; read to feed clause content into other systems or reporting, or maintained from an external source of truth. | 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. | Clause Library is specific to Agiloft and Employment Status to Ceridian Dayforce — each maps to any object or custom field on the other side. |
How changes propagate between Agiloft and Ceridian Dayforce
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.
Agiloft Ceridian Dayforce Sub-second propagation
DetectionAgiloft notifies Stacksync of record changes through webhook events. Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL.
DeliveryEach detected change is written to Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.
Ceridian Dayforce Agiloft Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Agiloft through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Agiloft: Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.
- 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.
What ships with Agiloft ⇄ Ceridian Dayforce
Connect Agiloft and Ceridian Dayforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Agiloft–Ceridian Dayforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Agiloft or Ceridian Dayforce 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 Agiloft or Ceridian Dayforce record.
Observability
Monitoring
Track your Agiloft ⇄ Ceridian Dayforce sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Agiloft and Ceridian Dayforce.
How the Agiloft and Ceridian Dayforce connectors work
Agiloft
- Integration surface
- REST API (/ewws/rest/{kb}) and SOAP/EWS v2 web services (EWWSv2Service WSDL), plus a native Webhooks subscription API
- Authentication
- OAuth 2.0 via OAuth2 Client Setup - Authorization Code with PKCE for user-delegated apps and Client Credentials for machine-to-machine; also JWT tokens or Basic Auth with a session token from POST /ewws/rest/{kb}/login
- Change detection
- Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL; otherwise poll each table by its Date Updated / modified-time fields. Agiloft has no database change-data-capture log.
- Capabilities
- read · write · webhooks
- Rate limits
- Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.
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.
How it works
How to connect Agiloft to Ceridian Dayforce — 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 Agiloft and Ceridian Dayforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Agiloft
connected
Ceridian Dayforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Agiloft and Ceridian Dayforce 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 · Agiloft ⇄ Ceridian DayforceCustomers 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.
Agiloft Ceridian DayforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Agiloft and Ceridian Dayforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Agiloft and Ceridian Dayforce: authenticate both systems, choose the objects to sync (such as Agiloft's Companies and People), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Agiloft: Native webhooks fire on record create, edit, or delete, and Agiloft verifies the callback URL with a GET handshake before delivering events; register them via POST /ewws/webhooks. Ceridian Dayforce: Delta sync uses filterUpdatedStartDate and filterUpdatedEndDate plus filterUpdatedEntities (EmploymentStatuses, WorkAssignments, and others) to pull only records changed within a window. Stacksync's field mapping accounts for these differences between Agiloft and Ceridian Dayforce 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 Agiloft and Ceridian Dayforce records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Agiloft and Ceridian Dayforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Agiloft–Ceridian Dayforce integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Agiloft and Ceridian Dayforce. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Agiloft: Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL; otherwise poll each table by its Date Updated / modified-time fields. Agiloft has no database change-data-capture log. 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 407 integrations available for Agiloft and Ceridian Dayforce.
Popular · 7 of 407
-
Agiloft ⇄ Paylocity -
Agiloft ⇄ Ukg Ready -
Agiloft ⇄ BambooHR -
Ceridian Dayforce ⇄ Quip -
Ceridian Dayforce ⇄ Smartsheet -
Ceridian Dayforce ⇄ Sysaid -
Ceridian Dayforce ⇄ Wrike
No integrations match .
