Skip to content
Business productivity ⇄ Human resources

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

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

Keep the people, teams, and status that Atlassian 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 Atlassian 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 Confluence Spaces, Jira Issues, Jira Projects, Boards and Sprints in Atlassian with Employment Status, Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries 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 Atlassian within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Atlassian 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 Create Jira issues from records in other systems, such as onboarding tasks generated from a closed-won CRM deal.
  • 02 Keep Jira and a second tracker (for example a customer's Jira instance) aligned during co-delivery projects.
  • 03 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.
  • 04 Two-way sync of Employee and Work Assignment data (position, department, location, org unit) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR keeps editing in Dayforce.

Common sync patterns

Org and team structure kept current

Department, team, and reporting-line changes from Ceridian Dayforce keep the groups, queues, or projects in Atlassian assigned to the right people.

Where Atlassian 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 Atlassian 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 Atlassian with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

What you can sync between Atlassian 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.

Atlassian objects Ceridian Dayforce objects How this pairing syncs
Attachments Files on issues mirrored to paired records where needed. 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. Attachments is specific to Atlassian and Employee Schedules to Ceridian Dayforce — each maps to any object or custom field on the other side.
Custom Fields Instance-specific fields (customfield IDs) that carry most business-specific data in syncs. 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. Custom Fields is specific to Atlassian and Org Units, Departments, Jobs & Positions to Ceridian Dayforce — each maps to any object or custom field on the other side.
Workflows and Statuses Status transitions mapped to stages in the paired system. 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. Workflows and Statuses is specific to Atlassian and Time Away From Work & Balances to Ceridian Dayforce — each maps to any object or custom field on the other side.
Users and Groups Assignees and reporters matched to identities in other tools. 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. Users and Groups is specific to Atlassian and Employee (HR / Person Details) to Ceridian Dayforce — each maps to any object or custom field on the other side.
Confluence Pages Documentation content readable and writable through the Confluence REST API. 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. Confluence Pages is specific to Atlassian and Employment Status to Ceridian Dayforce — each maps to any object or custom field on the other side.
Confluence Spaces Namespaces that scope page syncs and permissions. 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. Confluence Spaces is specific to Atlassian and Work Assignments to Ceridian Dayforce — each maps to any object or custom field on the other side.

How changes propagate between Atlassian 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.

Atlassian Ceridian Dayforce Sub-second propagation

DetectionAtlassian notifies Stacksync of record changes through webhook events. Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill.

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

Ceridian Dayforce Atlassian Sub-second propagation

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

DeliveryEach detected change is written to Atlassian 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 Atlassian ⇄ Ceridian Dayforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Atlassian and Ceridian Dayforce connectors work

Atlassian

Integration surface
REST APIs per product (Jira Cloud and Confluence Cloud)
Authentication
OAuth 2.0 (3LO) for apps or API tokens with basic auth for scripts
Change detection
Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill
Capabilities
read · write · webhooks

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
How it works

How to connect Atlassian 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.

  1. 01

    Connect your apps

    Authenticate Atlassian 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Atlassian connected
    Ceridian Dayforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Atlassian 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.

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

Atlassian and Ceridian Dayforce 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 444 integrations available for Atlassian and Ceridian Dayforce.

Popular · 8 of 444
All Atlassian integrations All Ceridian Dayforce 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