Skip to main content

Connect Ceridian Dayforce

Import your workers and their job history from Ceridian Dayforce, the HR and payroll platform. You connect Oho to Dayforce once, and Oho creates your workers and keeps them in step with Dayforce on the schedule you choose — so people don't have to be added in two places.

Ceridian Dayforce is in Beta

This connector is still being rolled out. It imports workers and their job history, along with worker status and organisation details. If you hit something unexpected, contact support@weareoho.com.

What you'll end up with

Your Dayforce people in Oho as workers — each ready for credentials to be added and checked — kept in step with Dayforce, without maintaining two lists.

Before you start​

You'll need:

  • Your people already recorded in Dayforce, with the details you want in Oho — their names, contact details, and job history.
  • A Dayforce administrator, or someone who has that access, to provision a web-services account in Step 1.
  • Your Dayforce Company ID — the identifier for your Dayforce environment.

Step 1: Get your auth details​

What you'll need for this step

An administrator who can provision a Dayforce web-services account. The account is created inside Dayforce, not in Oho — if you don't administer Dayforce yourself, loop in whoever does before you start.

Dayforce uses a dedicated web-services account — a non-human account whose only purpose is API access — that Oho signs in as to read worker data over the Dayforce REST API.

  1. Ask your Dayforce administrator to provision a web-services (API) user scoped to read workers and their job history.
  2. Copy the account's username and password.
  3. Copy your Company ID — the identifier for your Dayforce environment.
Technical detail: authentication, environment & permissions

Hand these points to whoever administers Dayforce — a non-technical admin can skip them.

  • Auth mechanism. Oho authenticates to the Dayforce RESTful Web Services with the web-services account's username and password against your Company ID. [Eng to confirm the exact base URL / namespace and whether a separate test vs production host applies.]
  • Least privilege. Scope the web-services account to read-only access to the worker and employment (job-history) data Oho imports, and nothing more. [Eng to confirm the exact Dayforce role/feature access required.]
  • Where secrets live. Oho stores the password encrypted, referenced by a stored secret ref.
Treat these credentials like a password, and rotate them

The web-services account's credentials grant ongoing access to worker PII for as long as they're valid. Never post them in email, chat, or a ticket, scope the account to read-only, and rotate the password periodically and whenever someone with access to it leaves. To rotate without downtime, set the new password in the integration's settings, then retire the old one in Dayforce.

Expected outcome: you have your Dayforce Company ID, username, and password copied, ready to paste into Oho.

Step 2: Connect it in Oho​

In the left menu under Admin, click Integrations, then start a new integration.

The Integrations page in Oho

Pick Ceridian Dayforce from the list of sources.

Choosing a source in Oho

Paste your Company ID, username, and password, then click Next.

Expected outcome: Oho confirms it can reach Dayforce and moves you on to field mapping.

Step 3: Map your fields​

Oho creates one worker per Dayforce employee. It recognises a returning worker by their Dayforce employee ID (XRefCode), carried on source.externalId — so a re-sync updates the existing worker in place rather than creating a duplicate.

Dayforce has its own names for things such as status, location, and job; the setup screen asks you to line each one up with its Oho value before your first sync. For what each field expects, which are required, and how re-syncs avoid duplicates, see the shared Map your fields reference, and the Ceridian Dayforce integration reference for what this connector imports at a glance.

Map every value, or those records won't land where you expect

A Dayforce value you leave unmapped still imports, but Oho can't place it correctly until it's mapped. If a new value appears in Dayforce later, Oho flags it so you can map it.

Expected outcome: every Dayforce value the setup screen lists maps to its Oho equivalent, and each worker carries their Dayforce employee ID as the match key.

Step 4: Set the schedule​

Choose how often the sync runs, then name it and save.

  • Once — a one-off load to get started. You can disable the web-services account in Dayforce afterwards if you don't intend to sync again.
  • Recurring — Oho re-reads Dayforce on a schedule, so new starters, role changes, and terminations flow through automatically. The web-services account must stay active and keep its read access for future runs.

Setting the sync schedule

Expected outcome: the connection is saved and scheduled, and appears in your Integrations list.

Step 5: Run & verify your first sync​

Run it now with Save & Run, or wait for the first scheduled run. Once it's run, confirm your people are in: they appear under All Workers, and each credential you later add is checked against its official source (see One-off verification).

The new connection in your Integrations list

If the run didn't bring everyone in, check the run history and the Common questions below.

Expected outcome: your people are in Oho under All Workers, ready for credentials to be added and checked.

What happens next​

  • Your people appear under All Workers, ready for checks.
  • To keep those checks current, add a verification source for the credential types you hold — synced credentials then verify at the register automatically.
  • If recurring, you don't re-import by hand — change it in Dayforce and Oho picks it up on the next run.

Common questions​

The sync found nothing. Confirm the Company ID, username, and password were copied correctly, and that the web-services account has read access to workers. A wrong Company ID points Oho at the wrong environment.

Some workers didn't import. Oho matches returning workers on their Dayforce employee ID (source.externalId). Check the match key and required fields from Step 3.

I don't see Integrations. This is an admin area — if it's not in your menu, ask an admin in your organisation, or contact support@weareoho.com.