Skip to main content
The Dayforce integration is read-only, and its application feed carries no resumes. These are limits of what Dayforce exposes, not settings in Alex:
  • Nothing Alex produces is written back to Dayforce. No interview report PDF, report link, note, stage move, or rejection reaches a candidate, application, or job record — recruiters read interview results in Alex.
  • No resumes or attachments reach Alex. Applications arrive as report rows, so Resume Screens cannot score a Dayforce application and Talent Match cannot search a Dayforce candidate database. Load resumes into Alex with Upload Resumes to screen those candidates.
  • Custom fields are readable on jobs only. Requisitions expose their Dayforce custom fields; applications and candidates arrive as a fixed set of report columns — no custom fields, no screening-question answers.

​
Overview

Alex integrates with Dayforce through two complementary channels:
  • Jobs sync into Alex through Kombo, our unified integration provider. New job requisitions in Dayforce automatically appear in Alex, where your job workflow configures them into interviews.
  • Applications are pushed from Dayforce to Alex via a scheduled custom report webhook. Each delivery contains the new applications since the last send; Alex creates the candidates and runs your application workflow (for example, automatically inviting each applicant to an interview).
Both channels are read-only — see Integration Limits for what that rules out.

​
Key Features

​
Automated Job Import

When a new job requisition is created in Dayforce, Alex imports it through Kombo and runs your job workflow — generating an interview template from the job’s title and description. Use the New Job from ATS trigger node in your job workflow to configure which Dayforce fields populate the job title, description, and jobs-list columns.

​
Automated Interview Invites

When Dayforce delivers new applications to the webhook, Alex matches each application to its job, creates the candidate with their contact details, and fires the New Applications via Webhook trigger in your application workflow — typically inviting the candidate to an interview by email or SMS.

​
Do-Not-Hire Filtering

Applications marked Do Not Hire in Dayforce are automatically filtered out and are never invited.

​
Integration Limits

​
Step 1: Connect Dayforce via Kombo

  1. In Alex, go to Settings → Integrations and select Dayforce.
  2. Click Connect. A Kombo-hosted connection page opens in a new tab.
  3. Follow the prompts to authorize your Dayforce account.
  4. Back in Alex, the Dayforce card shows Syncing… while Kombo runs its first sync, then Connected. Job import begins automatically once the first sync completes.
If the card shows Needs attention, the connection requires re-authorization — repeat the Connect flow or contact your Alex account team.

​
Step 2: Set Up the Application Report Webhook in Dayforce

Configure a scheduled custom report in Dayforce that delivers new applications to Alex.

​
Report columns

The report must include the following columns, named exactly: One row per contact method is expected — a candidate with a mobile phone, home phone, and email arrives as three rows for the same application. Alex merges them automatically.

​
Delivery settings

  • Endpoint: POST https://api.alex.com/webhook/dayforce
  • Format: JSON array of report rows, Content-Type: application/json
  • Authentication header: x-api-key: <your Alex API key> — the same API key from your Alex dashboard used for the Alex public API. Requests without a valid key are rejected with a 401.
  • Scope: each delivery should contain only the applications that are new since the previous delivery.
Deliveries are safe to retry: Alex deduplicates on Job Posting Application Id, so a redelivered batch never re-invites a candidate who was already processed.

​
Step 3: Configure Your Workflows

  • Job workflow — add the New Job from ATS trigger. Its editor lets you choose which Dayforce fields (including custom fields, once Kombo is connected) populate the job title, description, client name, and location columns.
  • Application workflow — add the New Applications via Webhook trigger as the entry point. Every new application delivered by the report enters the workflow here.

​
How Alex Processes Each Delivery

  • Rows are grouped by Job Posting Application Id — one application per unique id, regardless of how many contact rows it spans.
  • Invalid rows (missing ids, unusable contact cells) never fail a delivery — they are skipped individually and logged, and the rest of the batch processes normally.
  • Applications with Do Not Hire Status of True on any row are excluded.
  • Phone selection prefers Mobile over Home (a valid number is always preferred over an invalid one); when duplicate rows conflict, the latest value wins. US phone numbers are normalized to include the +1 country code automatically; numbers that can’t be validated are passed through (US-shaped ones still gain the +1 prefix) and logged.
  • Applications are matched to jobs by Job Req Id, against either the imported job’s Kombo id or its requisition code. If the job doesn’t exist in Alex yet, the application is skipped and is not automatically redelivered (deliveries are deltas). To avoid this, make sure jobs sync into Alex (via the Kombo connection) before applications for them are sent; if applications were skipped, contact Alex support — every delivery is stored and can be reprocessed.

​
Troubleshooting