Configure Dayforce imports into JSM Assets using OnLink

Use this guide to import workers, organizations, projects, and other Dayforce attributes into Jira Service Management Assets through OnLink.

Prerequisites

Access to OnLink from Manage your apps in Jira.
Dayforce API credentials and permissions for the worker, organization, project, and attribute data you want to import.
A JSM Assets object schema and object types ready for imported data.
Target Assets attributes created for each Dayforce field you plan to map.

1. Configure the Dayforce connection

In Jira, go to Manage your apps > OnLink > Connections.
Create or edit the Dayforce connection.
Enter the required Dayforce API details and credentials.
Save the connection and confirm it connects successfully.

For Dayforce connection details, see Connections and System Triggers.

2. Create the Assets import configuration

Review the Assets import setup instructions here.
Open OnLink from Manage your apps.
Create an Assets import configuration for the target object schema and object type.
Select the Dayforce connection created in the previous step.
Save the configuration before adding field-level mappings.

3. Configure field-level mapping

Add one mapping rule per line. Use key: for the unique identifier OnLink uses to match and update existing Assets objects. Use map: for standard field mappings from Dayforce to Assets.

The following example maps Dayforce worker fields to Assets attributes. Any field available in the Dayforce Employee Details API can be mapped to an Assets attribute.

key:EmployeeNumber=WorkerID
map:FirstName=Name
map:Email=JiraUser
map:DisplayName=Email
map:WorkAssignments.Items.0.Position.ShortName=Title
map:EmployeeManagers.Items.0.ManagerXRefCode=ManagerName
map:OriginalHireDate=HireDate

The mapping format is:

Mapping item	Purpose

Mapping item	Purpose
`key:EmployeeNumber=WorkerID`	Uses the Dayforce employee number as the unique key and maps it to the Assets `WorkerID` attribute. OnLink uses this key to create new objects or update existing objects.
`map:FirstName=Name`	Maps the worker first name from Dayforce to the Assets `Name` attribute.
`map:Email=JiraUser`	Maps the worker email address to the Assets user attribute, typically used to link the object to a Jira user.
`map:DisplayName=Email`	Maps the Dayforce display name to the selected Assets attribute. Update the target attribute name if your schema uses a different field.
`map:WorkAssignments.Items.0.Position.ShortName=Title`	Maps the worker's primary position short name to the Assets `Title` attribute.
`map:EmployeeManagers.Items.0.ManagerXRefCode=ManagerName`	Maps the worker's manager reference code to the Assets manager attribute.
`map:OriginalHireDate=HireDate`	Maps the worker's original hire date to the Assets `HireDate` attribute.

Use the exact Dayforce source field path on the left side of the mapping and the exact Assets attribute name on the right side.

Here’s an exhaustive list of supported fields which can also be found in Dayforce API docs:

BadgeNumber string
BirthDate string($date-time)
BirthCountry string
BirthState string
BirthCity string
ClockSupervisor boolean
EligibleForRehire string
EmployeePin string
EntitlementOverrideDate string($date-time)
EstimatedReturnDate string($date-time)
ExportDate string($date-time)
FederatedId string
Gender string
HireDate string($date-time)
HomePhone string
IsAboriginal string
IsVisibleMinority string
EligibleForOnDemandPay boolean
EligibleForDFWalletPayCard boolean
Nationality string
NewHireApproved boolean
NewHireApprovedBy string
OriginalHireDate string($date-time)
PPACAOverrideDate string($date-time)
RegisteredDisabled string
SeniorityDate string($date-time)
SocialSecurityNumber string
SSNCountryCode string
SSNExpiryDate string($date-time)
StartDate string($date-time)
TaxExempt boolean
TaxpayerId string
TerminationDate string($date-time)
VeteranSeparationDate string($date-time)

4. Test the import

Open the import configuration in OnLink.
Click Get Data.
Review the job logs and wait for the message: No more pending records. Data will be imported on next Import run.
Click Import.
Verify that the expected Assets objects were created or updated.

5. Configure automation and production schedule

After testing is successful, enable the production schedule for the import. OnLink production runs are automated based on the schedule you choose.

Troubleshooting and notes

If records are not updated, confirm the key: mapping points to a stable unique identifier.
If an attribute is empty, confirm the Dayforce source field path is available in the API response.
If a Jira user is not linked, confirm the mapped email matches the user's Jira account email.
Use job logs to confirm whether the issue occurred during Get Data or Import Data.

Dayforce to JSM Assets