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 10 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.

Follow instructions here to configure webhook in UKG Pro: https://developer.ukg.com/hcm/docs/ukg-webhooks-user-guide

Then add below config parameters to the webhook mapping in OnLink:

config:auth_scheme=header_token_ukgpro
config:auth_token=<a random 12 character password string that acts as a secure token> Use this string when configuring webhook in UKG pro - specifically, step 5 of Add Subscription asks you to add a free form headers fields. Set the custom header key to x-onlink-key and custom header value to the random password string. Note that this random password is encoded once you save the settings and cannot be retrieved back.

OnLink combines employee demographic data and employment data and makes it available for mapping. Any field supported by UKG Pro API can be mapped in this way.

key:employeeId=customfield_10121
map:firstName=customfield_10065
map:lastName=customfield_10066
map:jobTitle=customfield_10067
map:supervisorId=customfield_10068
map:originalHireDate=customfield_10069

image-20240531-205752.png

  • No labels