Skip to content
Human resources ⇄ CRM

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

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

  • 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 Streak CRM

Keep the people who own accounts in Streak CRM in step with the workforce records in Ceridian Dayforce, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Streak 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 Organizations, Tasks, Email threads, Custom fields in Streak CRM with Employee Punches & Raw Clock Entries, Employee Schedules, Org Units, Departments, Jobs & Positions, Time Away From Work & Balances 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 Streak CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Hand off closed-won boxes to billing or fulfillment systems and sync status back into the pipeline
  • 02 Keep contacts aligned between Streak and email marketing or enrichment tools
  • 03 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.
  • 04 Replicate Compensation Summary and pay data into a warehouse for headcount, labor-cost, and compensation reporting without manual BI exports.

Common sync patterns

Deactivate access when someone leaves

When Ceridian Dayforce marks a worker as departed, the matching user in Streak CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.

One directory of people

A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.

Where Ceridian Dayforce tracks people the business also engages: contacts stay in sync

A person recorded in Ceridian Dayforce, such as a candidate or applicant, can create or update the matching contact in Streak CRM, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

What you can sync between Ceridian Dayforce and Streak CRM

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 Streak CRM objects How this pairing syncs
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. Tasks To-dos attached to boxes for follow-up tracking. Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Tasks to Streak 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. Email threads Gmail threads linked to boxes, since the CRM lives inside the inbox. Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Email threads to Streak 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. Custom fields Per-pipeline field definitions that determine what data a box can hold. Employee Schedules is specific to Ceridian Dayforce and Custom fields to Streak 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. Pipelines Define the process and the custom field schema that boxes in them carry. Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Pipelines to Streak 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. Boxes The core record (a deal, hire, or project) tracked through pipeline stages. Time Away From Work & Balances is specific to Ceridian Dayforce and Boxes to Streak CRM — 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. Stages Pipeline steps whose transitions are the usual trigger for downstream syncs. Employee (HR / Person Details) is specific to Ceridian Dayforce and Stages to Streak CRM — each maps to any object or custom field on the other side.

How changes propagate between Ceridian Dayforce and Streak CRM

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 Streak CRM Sub-second propagation

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

DeliveryEach detected change is written to Streak CRM through its API, with automatic retries and rate-limit backoff.

Streak CRM Ceridian Dayforce Interval-based propagation

DetectionStacksync polls Streak CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling against pipeline, box, and contact endpoints.

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.
  • Streak CRM: Subject to the platform's API rate limits; quotas are not prominently published.
What ships with Ceridian Dayforce ⇄ Streak CRM

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Streak CRM

Integration surface
REST API
Authentication
API key issued per user
Change detection
Polling against pipeline, box, and contact endpoints; Streak's automations can send outbound webhooks on higher plans
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits; quotas are not prominently published
How it works

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

    Choose tables

    Pick the Ceridian Dayforce and Streak 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Ceridian Dayforce ⇄ Streak CRM
    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 Streak CRM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Ceridian Dayforce and Streak CRM 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.

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 421 integrations available for Ceridian Dayforce and Streak CRM.

Popular · 7 of 421
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.