Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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:auth_token=<create a secure 20 char token, will be used when configuring webhook in UKG pro - step 5 of Add Subscription "At the Add Free Form Headers fields, enter a custom header key and custom header value">
config:ukgpro_url=https://{tenantId}.{hostname}/personnel/v1/employee-changes/{employeeId} can be changed to any other REST API - see this list
config:auth_username=<webservice account username from UKG> reference - UKG web service account has username, password, and an API key
config:auth_password=<webservice account password from UKG>
config:us_customer_api_key=<webservice account api key from UKG>

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.

image-20240528-164552.png

  • No labels