Here’s a sample workflow to demonstrate the use of the Onelogin Orchestration app to automate employee onboarding in an organization.
Create an event when a Service request is raised.
Followed by the condition to ensure the Service request is Employee Onboarding for Onelogin.
You can then pull in the App Node which will have the following configurations:
App Name: Onelogin - Orch
App Action: Get User Details
Notes when Configuring Inputs:
username: It is the user’s OneLogin account username.
To validate the existence of a user, a condition node is added with system_message does not exist.
Next, pull in and configure Reader Node to read the ‘Group and Role Mappings’ to get group_id and role based on the Department and Location selected in Service Request Form.
Note: For the above Reader Node field we have used a Custom Object named Group and Role Mappings. Below is the description of the same.
The object ‘Group and Role Mappings’ will be used to store group_id and roles based on the Department and Location that the employee is joining. Here are the fields:
Next, pull in an action node for adding a note to the ticket for the group_id selected based on Department and Location.
You can then pull in the App Node which will have the following configurations:
App Name: Onelogin - Orch
App Action: Create User
Notes when Configuring Inputs:
email - It is the user’s Onelogin account email address.
firstname - It is the user’s first name.
lastname - It is the user’s last name.
username - It is the user’s username.
company - It is the user’s company or organization name.
department - It is the user’s department name.
group_id - It is the Id of the group in which the user needs to be added. You can get it from the reader node via Readers placeholder.
To validate whether the user-created or not a condition node is added with the status code is 200.
If the user creation is successful you can then pull in the App Node which will have the following configurations:
App Name: Onelogin - Orch
App Action: Add User Roles
Notes when Configuring Inputs:
username - It is the user’s OneLogin account username. You can get it in the response of Create User action and pass it via placeholder as shown below.
role - It is the name of the role to be given which is to be assigned to the User. You can get it from the reader node via Readers placeholder.
To validate whether the user-created or not a condition node is added with the status code is 200.
If the workflow is successfully executed add a note using an action node.
