Skip to main content
Dayforce is a human capital management platform that provides comprehensive solutions for workforce management, payroll, benefits, and talent management. It helps organizations streamline HR processes, manage employee data, and optimize workforce operations.

​
1. Add your Dayforce access

  1. In the Destinations tab, click on the “Add destination” button located on the top right of your screen. Then, select the Dayforce option from the list of connectors.
  2. Click Next and you’ll be prompted to add your access credentials and endpoints. The following configurations are available:
    • Username: Username to authenticate against the Dayforce API.
    • Password: Password to authenticate against the Dayforce API.
    • Company ID: The company ID associated with your Dayforce workspace.
    • Authentication endpoint URL: The auth endpoint URL to generate the access token (e.g., https://your-company-url.dayforcehcm.com/connect/token).
    • API endpoint URL: The API endpoint URL to send data to (e.g., https://your-company-url.dayforcehcm.com/api/cbb/V1/EmployeeRawPunches).
  3. Click Next.

​
2. Select your data to send

  1. The next step is letting us know which data you want to send to the database. Select the layer and then the desired table.
    Tip: The table can be found more easily by typing its name.
  2. Click Next.

​
3. Map your Dayforce data to send

  1. Select the fields from your selected table that you want to send.
  2. For each field selected from the catalog, configure the mapping rules that dictate how incoming data translates to Dayforce fields:
    • Lakehouse Column: The search path to get the value from the incoming stream (e.g., $.last_name, $.email[*].value).
    • Dayforce Field: The field name on Dayforce’s API where the data should be sent. Please note it is case sensitive (e.g., LASTNAME, EMAIL).
    • Default: An optional default value to be used for the field if the lakehouse field is empty or missing. If no default value is provided and the field is not found, an empty value is used.
  3. Click Next.

​
4. Configure your Dayforce data destination

  1. Describe your destination for easy identification within your organization. You can inform things like what data it sends, to which team it belongs, etc.
  2. To define your Trigger, consider how often you want data to be sent to this destination. This decision usually depends on how frequently you need the new table data updated (every day, once a week, only at specific times, etc.).
  3. Click Done.

​
Check your new destination!

  1. Once completed, you’ll receive confirmation that your new destination is set up!
  2. You can view your new destination on the Destinations page. Now, for you to be able to see it on your Dayforce account, you have to wait for the pipeline to run. You can monitor it on the Destinations page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your data should be seen on Dayforce.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!

​
Implementation Notes

  • Authentication Verification: The connector verifies your authentication credentials before sending any records. If the credentials or company ID are incorrect, the sync immediately fails with a clear error, ensuring bad credential issues are caught early instead of being treated as per-record failures.
  • Mapping Defaults: When a mapping rule lacks a default value and the source field is missing, an empty value is sent — the connector guarantees that no spurious string values (such as "None") are accidentally sent to the Dayforce API.