Skip to content
Human resources ⇄ Database

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

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

Put your workforce data where your apps can reach it: Dynamo DB and Ceridian Dayforce share the same people, positions, and org structure in real time.

Ceridian Dayforce is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Dynamo DB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Employee (HR / Person Details), Employment Status, Work Assignments, Compensation Summary & Pay Adjustments in Ceridian Dayforce need to exist as queryable Partition and Sort Keys, Global Secondary Indexes, DynamoDB Streams, Global Tables in Dynamo DB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Partition and Sort Keys, Global Secondary Indexes, DynamoDB Streams, Global Tables in Dynamo DB with Employee (HR / Person Details), Employment Status, Work Assignments, Compensation Summary & Pay Adjustments in Ceridian Dayforce field by field, in real time. You decide which system owns which fields — Ceridian Dayforce typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Consolidate multi-region Global Tables data into a single reporting store.
  • 02 Replace ad-hoc export scripts with continuous sync driven by DynamoDB Streams.
  • 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

Mirror people records into the database

Records maintained in Ceridian Dayforce land as queryable Partition and Sort Keys, Global Secondary Indexes, DynamoDB Streams, Global Tables in Dynamo DB, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Employee (HR / Person Details), Employment Status, Work Assignments, Compensation Summary & Pay Adjustments replicate into Dynamo DB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

What you can sync between Ceridian Dayforce and Dynamo DB

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 Dynamo DB objects How this pairing syncs
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. Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Global Secondary Indexes to Dynamo DB — 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. DynamoDB Streams Ordered item-level change records consumed for incremental sync. Employee Schedules is specific to Ceridian Dayforce and DynamoDB Streams to Dynamo DB — 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. Global Tables Multi-region replicas relevant when syncs must read from a specific region. Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Global Tables to Dynamo DB — 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. Tables The top-level containers a sync targets; each table is addressed independently. Time Away From Work & Balances is specific to Ceridian Dayforce and Tables to Dynamo DB — 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. Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. Employee (HR / Person Details) is specific to Ceridian Dayforce and Items to Dynamo DB — 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. Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. Employment Status is specific to Ceridian Dayforce and Attributes to Dynamo DB — each maps to any object or custom field on the other side.

How changes propagate between Ceridian Dayforce and Dynamo DB

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 Dynamo DB Sub-second propagation

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

DeliveryEach detected change is applied to Dynamo DB as a row-level write, with types converted between the two schemas.

Dynamo DB Ceridian Dayforce Sub-second propagation

DetectionChanges in Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.

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.
  • Dynamo DB: Throughput is governed by the table's provisioned or on-demand capacity mode.
What ships with Ceridian Dayforce ⇄ Dynamo DB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Ceridian Dayforce and Dynamo DB 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

Dynamo DB

Integration surface
Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries
Authentication
AWS IAM credentials with SigV4 request signing
Change detection
Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration
Capabilities
read · write · CDC
Rate limits
Throughput is governed by the table's provisioned or on-demand capacity mode
How it works

How to connect Ceridian Dayforce to Dynamo DB — 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 Dynamo DB 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
    Dynamo DB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Ceridian Dayforce and Dynamo DB 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 ⇄ Dynamo DB
    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 Dynamo DB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Ceridian Dayforce and Dynamo DB 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 450 integrations available for Ceridian Dayforce and Dynamo DB.

Popular · 7 of 450
All Ceridian Dayforce integrations All Dynamo DB 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