Configuration Guide: Employee onboarding - Workday
The configuration options on this page are only accessible to administrators.
Refer to the Usage guide: Employee onboarding - Workday to use library content as a standard user.
Prerequisites
This library pack contains content from the following required expansion products:
Included content and dependencies
This library pack contains the following content and dependencies:
Workflow
Employee onboarding - Workday
A customisable workflow to check pre-requistes on a new employee's device before launching a welcome campaign with a redirection to Workday to start the onboarding process.
Remote action
Get ZScaler status
This Remote Action provides information about the connectivity status of Zscaler.
Start ZScaler
Creates a scheduled task on the target system to start the Zscaler main service (ZSAService) in a given time provided by an input parameter.
Campaign
Onboarding - Zscaler authentication - workflow invoke
Asks the employee to (re)authenticate with ZScaler, with brief instructions.
Onboarding welcome - workflow invoke
Welcomes the employee to the organization and provides them with a link to Workday.
Configuring "Employee onboarding pack"
Follow these steps to install and configure content:
Before configuration - Install library pack content from Nexthink Library
Step 1 - Configure remote action(s)
From the main menu, navigate to the Remote Actions > Manage remote action page.
Review and edit your remote actions.
Nexthink recommends the following configurations for these remote actions:
Get Zscaler status
Triggered by the workflow
Start Zscaler
Triggered by the workflow
TaskSchedulerTimeDelay
StartZscalerScheduledCampaignID (Tick the checkbox for "Allow the user to enter a custom value")
Step 2 - Edit campaigns
From the main menu, navigate to the Campaigns > Manage Campaigns page.
Review and edit your campaigns. For each installed campaign:
Customize the sender name and image.
Review and adjust questions.
Publish the campaign when you are ready to use it.
Nexthink recommends the following configurations for these campaigns:
Onboarding - Zscaler authentication - workflow invoke
zscaler_authentication
Asks the employee to (re)authenticate with ZScaler, with brief instructions.
Onboarding welcome - workflow invoke
onboarding_welcome
Welcomes the employee to the organization and provides them with a link to Workday.
Step 3 - Configure ITSM API connector credentials
The configuration of connector credentials is essential for enabling API calls.
From the main menu, navigate to the Administration > Connector credentials page.
Choose the HTTPS option from the Protocol drop-down.
Paste the root
https://
of the ITSM into the URL address field.Choose the Basic option from the Authorization drop-down.
Enter a Username and Password to connect to the third-party tool.
Save the credential.

After configuring the connector credential for the ITSM API:
From the specific workflow, fill in each Service/API thinklet dropdown field for Credentials.
When the workflow is installed or copied from the Library, this field will be blank as it is a local setup of each environment and is not included in the Library.

Step 4 - Configure Microsoft Teams communication channel
This workflow uses Microsoft Teams messages as the communication channel with end users, which is called a Message thinklet. To learn more about the Message thinklet, see the documentation.
For the Message thinklets to work correctly in this workflow, please complete the configuration steps described on this documentation page.
Step 5 - Set up a registered Microsoft Entra ID app and configure Microsoft Graph API connector credentials
Refer to the following documentation page to register the Microsoft Entra ID application and configure the appropriate connector credentials in Nexthink: Entra ID integration for workflows.
For this workflow, the registered Entra ID application must be granted the following permissions:
Application or Delegated
User.Read.All Directory.Read.All Mail.Send
This workflow has been tested using the Application permission type. Different environments require different permissions. You should assign permissions according to your environment and know the risks involved.
Refer to the Graph REST API documentation from Microsoft for more information.
RELATED TOPICS
Last updated
Was this helpful?