<aside> 💡

For an overview of the Workday API migration, check out Workday ATS -> Ashby Recruiting API Migration Guide. For more on syncing Workday positions with Ashby and hired Ashby candidates with Workday, check out Workday. Our FAQ can be found at Workday Integration FAQs

</aside>

Overview

Ashby connects to Workday using several Workday APIs, each of which requires varying user and permission configurations. It is broken down into 3 phases:

1. Configuring Ashby's Integration System User (ISU)
2. Creating the "API Client for Integrations" for Ashby
3. Configuring domain security for Ashby's ISU

In each step, we will advise you to copy down some important information that will need to be  configured within Ashby, in order to connect your Ashby and Workday instances.

Configuring Ashby's Integration System User (ISU)

• Log in to your Workday application using an Administrator account.
• In the application's search box, search for create user and then select Create Integration System User.
• Enter a User Name and Password. As a username we recommend: Ashby_ISU

<aside> 💡

Copy down the username and password for future configuration within Ashby.   Note: Some of Workday's Copy UI can copy unnecessary details of fields, so check that you are copying just the username and password!

</aside>

• Leave the Require New Password at Next Sign In checkbox unchecked as this user will be accessing Workday programmatically
  • Leave the Session Timeout Minutes with its default value of 0, which will prevent the user's sessions from timing out prematurely.
  • Select the option Do Not Allow UI Sessions (this prevents the account from logging into Workday).

<aside> 💡

If possible, make sure the password does not expire. Otherwise, Ashby's sync will stop when the password expires. You can do this by going to the Maintain Password Rules  task and adding Ashby's ISU to the System Users exempt from password expiration  field.

</aside>

Create the "API Client for Integrations" for Ashby

For syncing and mapping certain fields, Ashby needs additional access to the Workday API to run custom reports. We will run this report using WQL (Workday Query Language) via Workday’s  REST API.

Access to the REST API requires a special API client to be configured.