Skip to content
Human resources ⇄ Database

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

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

Put your workforce data where your apps can reach it: Citus 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. Citus is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries, Employee Schedules in Ceridian Dayforce need to exist as queryable Sequences, Distributed tables, Reference tables, Local tables in Citus 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 Sequences, Distributed tables, Reference tables, Local tables in Citus with Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries, Employee Schedules 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 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
  • 02 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • 03 Replicate Compensation Summary and pay data into a warehouse for headcount, labor-cost, and compensation reporting without manual BI exports.
  • 04 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.

Common sync patterns

Reporting and analytics on current data

Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries, Employee Schedules replicate into Citus where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Ceridian Dayforce stay consistent in Citus, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in Citus write onto the matching record in Ceridian Dayforce where those fields are writable, keeping the people system enriched.

What you can sync between Ceridian Dayforce and Citus

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 Citus 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. Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Work Assignments is specific to Ceridian Dayforce and Reference tables to Citus — 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. Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Local tables to Citus — 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. Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Schemas to Citus — 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. Views Curated projections over distributed data, often used as read-only sync sources. Employee Schedules is specific to Ceridian Dayforce and Views to Citus — 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. Sequences Key generators that matter when external writes must not collide with application inserts. Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Sequences to Citus — 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. Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Time Away From Work & Balances is specific to Ceridian Dayforce and Distributed tables to Citus — each maps to any object or custom field on the other side.

How changes propagate between Ceridian Dayforce and Citus

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 Citus Sub-second propagation

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

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

Citus Ceridian Dayforce Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

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.
What ships with Ceridian Dayforce ⇄ Citus

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC
How it works

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

    Choose tables

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

Ceridian Dayforce and Citus 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 432 integrations available for Ceridian Dayforce and Citus.

Popular · 7 of 432
All Ceridian Dayforce integrations All Citus 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