Skip to main content

How to Obtain Outcome Data Status via-flat-file Integration

This guide covers how Dayforce pushes outcome data to Sapia.ai via flat-file (CSV), ensuring application statuses stay up to date automatically.

E
Written by Elbert Pranoto
Updated today

For Dayforce, application status change data (Outcome Data) collection is collected via flat-file data transfer.
Clients can automate this through Dayforce reporting system or any other export service, with files transferred to Sapia.ai on a regular schedule via sFTP.

For sFTP setup instructions, refer to: https://help.sapia.ai/en/articles/12394560-importing-data-via-sftp


CSV Specification

Column Header

Required?

Description

externalTenantID

Required

This value is provided by Sapia.ai and remains constant across all records.

externalCandidateID

Required

Maps to candidateAssessmentGuid in Dayforce.
This value is sent to Sapia.ai through the assessment integration)

applicationStatus

Required

The Candidate status name as configured in your Dayforce tenant (e.g. Manager Review, Hired, Pre-Offer, Offer Accepted).

Contact Sapia.ai to configure the mapping between your Dayforce status names and the corresponding Sapia.ai stages:
APPS_APPLICATION_NEW
APPS_APPLICATION_LONGLISTED
APPS_APPLICATION_SHORTLISTED
APPS_APPLICATION_INTERVIEW
APPS_APPLICATION_DECLINED
APPS_APPLICATION_OFFERED
APPS_APPLICATION_HIRED
APPS_APPLICATION_WITHDRAWN

Candidate status names must be provided to Sapia.ai verbatim and case-sensitive

date

Required

Format: yyyy-MM-dd

Timestamp when the status change occurred

comment

Optional

Free-text field for additional information about the status change

Note on column order and headers: Column headers and their order do not need to match this specification exactly. Sapia.ai supports configuration mapping, so columns can be mapped to the correct fields during setup.

Below is the sample file:

Did this answer your question?