HR to ITSM
Dayforce to Ivanti integration: employees and service requests on hire, transfer and termination
With an integration between Dayforce and Ivanti Neurons for ITSM, every employee from Dayforce is an employee in Ivanti, with location, department and manager, and a hire, transfer or departure in Dayforce sets up a service request from the right template. Ivanti has no Dayforce connector; KoppelHet reads the Dayforce REST API and writes through the Ivanti REST API.
What the integration does
Organisations with Dayforce as HR and payroll system and Ivanti Neurons for ITSM as service desk often fill employees in Ivanti from Active Directory, so only once the account exists. The manager then fills in the onboarding request in the portal, with data HR already had in Dayforce.
- Every morning KoppelHet asks Dayforce for hires with a start date within the onboarding window.
- For each employee KoppelHet fetches work assignment, organisation and manager, with the start date as reference date.
- KoppelHet creates or updates the employee in Ivanti and stores the RecID.
- A service request from the onboarding template is submitted for that employee, with the location and time zone of the work assignment.
- A termination produces an offboarding request; after the end date the employee is set to inactive.
What to watch for with Dayforce and Ivanti
- Ivanti does not list Dayforce among its inbound connectors. KoppelHet uses the REST API on both sides, with a Dayforce user that only reads and an Ivanti REST API key restricted to the IP address of the KoppelHet platform.
- A service request in Ivanti needs the RecID of an existing employee. KoppelHet searches Dayforce on a range of hire dates, creates the employee as soon as the start falls within the onboarding window and only then submits the request.
- The request needs the offset from UTC in minutes. Dayforce knows the work location per work assignment; KoppelHet determines the offset per location, so a start date in Toronto does not appear in Ivanti as the day before.
- The employee list from Dayforce only contains XRefCodes, and Ivanti returns at most one hundred employees per query. The nightly comparison therefore fetches the details per XRefCode and reads Ivanti in blocks of one hundred.
- A transfer is in Dayforce with an effective date. KoppelHet requests the employee with that date as reference date, only updates the Employee Location in Ivanti on that day and submits the request for access at the new location straight away.
- Dayforce only returns names if the API user's role has the right to personal information and field filtering is set up. If the name is missing, KoppelHet does not create an empty employee in Ivanti but reports the permission problem.
- Dayforce filters on termination dates. A departure HR records weeks ahead immediately produces an offboarding request with the last working day; the employee is only set to inactive in Ivanti after that day, so the laptop can still be returned in their name.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Does Ivanti have a Dayforce connector?
Not in the list of inbound Neurons connectors. KoppelHet uses the REST API of both systems.
Which templates does the integration use?
The published templates you already have in the catalogue. Per event in Dayforce we record which template and which fields are filled.
Does pay data go to Ivanti?
No. KoppelHet only requests name, contact details, work assignment, organisation and manager.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the REST API at /api/{clientName}/v1/Employees with FilterHireStartDate and FilterHireEndDate, FilterTerminationStartDate and FilterTerminationEndDate, FilterUpdatedStartDate and FilterUpdatedEndDate; then Employees/{XRefCode} with expand (WorkAssignments, Contacts, EmployeeManagers) and ContextDate. Names require the Employee Personal Information right.
- Ivanti through the OData REST API at /api/odata/businessobject/employees (POST, PATCH on RecID, $top at most 100). Service requests through POST /api/rest/ServiceRequest/new with subscriptionId from /api/rest/Template/{RecID}/_All_, strUserId, strCustomerLocation, localOffset and parameters par-{RecID}; all fields in the example are mandatory. Authorisation with a REST API key in its own key group.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Ivanti | Notes |
|---|---|---|
XRefCode | Personeelsnummer op de employee | Lookup key |
FirstName, LastName | Voornaam en achternaam | |
Werkadres uit Contacts | E-mail van de employee | |
Job uit WorkAssignments | Functie | |
Location uit WorkAssignments | Employee Location en strCustomerLocation | |
OrgUnit | Afdeling | |
EmployeeManagers | Leidinggevende | Must already be an employee |
Tijdzone van de locatie | localOffset in minuten |
Related
Ashby → Dayforce
Ashby to Dayforce integration: have Dayforce validate the hire first, then save it
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce
Dayforce → 4PS Construct
Dayforce to 4PS Construct integration: technicians and site managers from Dayforce in 4PS, with cost centre and end date