Trigger: Create ServiceNow Users from Greenhouse Users to Provision New Hires

Open

How it works

• Get the Greenhouse users to provision new hires through a webhook trigger.

• Add the output meta for the same.

• Now create the users on ServiceNow, by adding the details of new hires such as user name, first name, last name, title, department, user password, active, email id, mobile phone no, and roles.

• These details can be added through an output meta and can be visible in the dataslot section.

Following are the steps that will help to configure the automation:

Steps to configure

1. Click on start and the below form will appear on the screen.

2. Now add the name “trigger create user”, provide a description as “starting node, select webhook from the configuration.

3. Now add a URL into the input field. A webhook is a lightweight API that powers one-way data sharing triggered by events. Together, they enable applications to share data and functionality, and turn the web into something greater than the sum of its parts. APIs and webhooks both allow different software systems to sync up and share information.

   Open

   

4. Now add the output meta for fetching the details of users from Greenhouse. Output metadata is the type resolution for the result of a component. Each component can provide either static or dynamic metadata for the payload and attributes, isolated from each other. Click on browse, and add the metafile in a JSON format in the file name.

5. Click on ServiceNow and the below form will appear on the screen.

6. Enter the connection name as “ServiceNow connection”. For more details please visit https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585

7. Now, mention the action as “create users”. Action steps in ServiceNow require subject matter expertise with application tables, fields, and business logic.

8. Now click on data for adding and reviewing the details of the new hires.

9. Add an user name. An username is an identification used by a user to access the ServiceNow automation. The username can be a combination of formulas based on the requirements.

10. Now add the first name and last name of the candidates. It can be a combination of formulas.

11. Mention the title, a title is a text that is displayed under the username in posts, threads, profile and on the member list. It can be mentioned in a formula format based on the requirements.

12. Provide the details about the candidate department. It can be mention in a formula format.

13. Now provide the user password. The requirement of user passwords is to protect your sensitive information's. It’s can be generated with a unique combination of numerical and alphabetic characters.

14. Fill the active status for the automation. If you use active=true, you do not need to include "state is one of" that's the whole point of the active field.

15. Now provide the email id and mobile phone no of the candidate.

16. Add the roles of the candidate. It can be mention in the formula format.

17. Add an output meta if required from the below-mentioned field. An output metadata is the type resolution for the result of a component. Each component can provide either static or dynamic metadata for the payload and attributes, isolated from each other.

18. Click on the dataslot, and view the details of output meta from the tenant variables for provision of new hires, it will appear in the below format.

19. Now save the configuration for executing successful automation.