UKG Pro (UltiPro) Integration for Identity Provisioning
HR and payroll integration
Use UKG Pro workforce data as a source for user provisioning in downstream systems through NIM.
At a glanceDirect link to At a glance
The UKG Pro (UltiPro) integration collects workforce data into Tools4ever NIM so you can use HR records to drive account provisioning in systems such as Active Directory. The connector provides read access to collections including person_details, employment_details, company_details, and employee_phoneNumbers.
Before you start: Prepare a dedicated UKG Pro service account, the Tenant URL, Client Access Key, User Access Key, Username, and Password. Follow the connection guide for the required permissions and settings.
Verify success: Test company-details retrieval, then collect and inspect the person and employment records needed for your process. A successful company-details test does not establish that every employee collection is accessible.
Example: use HR records to provision directory accountsDirect link to Example: use HR records to provision directory accounts
Use this pattern when UKG Pro is the authoritative source for the workforce population you want NIM to manage:
- Collect the required UKG Pro person and employment data. Confirm how multiple employment records are associated with each person before selecting the provisioning population.
- Choose a stable person identifier present in the HR data and the target account data. Configure an inter-system relation using those fields. Do not assume that two fields with similar names contain the same value.
- Build a filter that includes only the records approved for provisioning. Define how your organization's employment status and effective dates affect that selection.
- Configure a target-system mapping for the intended account change. For example, create an AD account for one eligible person who has no matching account, then use a separate update mapping for approved attribute changes.
- Evaluate the job with a limited test population, verify matching and target attributes, and inspect the resulting directory account before scheduling recurring runs.
For example, an HR person identifier of E1001 should match the directory field holding E1001, even if the person's name changes. The identifier and destination attribute are choices for your deployment, not predefined field mappings supplied by the connector.
Check the first workforce collectionDirect link to Check the first workforce collection
| Check | What to confirm |
|---|---|
| Person records | The expected test person appears once in the selected population, with a usable identity key. |
| Employment records | The records relate to the correct person, and your filter handles multiple or future-dated employment records as intended. |
| Field access | The service account can read each collection and attribute used by the mappings. |
| Downstream behavior | A missing, duplicate, or unmatched identity is handled deliberately before a target account is created or changed. |
Solutions This Integration SolvesDirect link to Solutions This Integration Solves
Downstream user provisioning
Use UKG Pro workforce data as a source for user provisioning in downstream systems through NIM.
- Makes workforce data available to filters and mappings
- Keeps downstream identities aligned with source records
GuidesDirect link to Guides
Connector repository
Browse the UltiPro UKG Pro connector repository on GitHub.
Supported operationsDirect link to Supported operations
Filter tables by supported operation
Showing 10 of 10 tables| Table | Read | Create | Update | Delete |
|---|---|---|---|---|
| company_details | ||||
| employee_phoneNumbers | ||||
| employment_details | ||||
| job_families | ||||
| job_groups | ||||
| jobs | ||||
| locations | ||||
| org_levels | ||||
| person_details | ||||
| user_defined_fields |