Follow instructions in our Webhook documentation to understand how OnLink supports webhooks. Here are the config elements you will need to configure UKG Pro webhooks. This allows OnLink to receive Hire or Termination or Employee Change events from UKG. OnLink then creates Jira issues based on these events:
config:auth_scheme=header_token_ukgpro
config:header_token=<create a secure 20 char token, will be used when configuring webhook in UKG pro>
config:ukgpro_url=https://{tenantId}.{hostname}/personnel/v1/employee-changes/{employeeId}
can be changed to any other REST API - see this listconfig:auth_username=<webservice account username from UKG>
ref - Each web service account is assigned a unique user API key. This user API key along with the web service account username and password is necessary for authentication to an endpoint.config:auth_password=<webservice account password>
config:auth_password=<webservice account api key>
Follow instructions here to configure webhook in UKG Pro: https://developer.ukg.com/general/docs/ukg-webhooks-user-guide#add-a-subscription
Here’s the field mapping
key:employeeId=customfield_10121
map:firstName=customfield_10065
map:lastName=customfield_10066
Any field supported by UKG Pro API can be mapped in this way.