ServiceNow Integration

The following document will capture the available integration points with ServiceNow and how to configure them.

Vendor: ServiceNow

Integration Type:

 

Authentication

OAuth2.0

Please follow the following steps to get new access token which can be used in Oomnitza API pre-sets and SaaS User Role block.

  1. Please follow the documentation to create an OAuth2.0 app and keep your Subdomain, Client ID and Client Secret to be used later in configuring your credential setup within Oomnitza (Step 8)
  2. Go to Oomnitza "Settings" page and select "Credentials"
  3. Click the '+' icon in the top right corner to add a new credential. A pop-up will appear: mceclip0.png
  4. Type the 'Name' which helps you identify the credential, example ‘ServiceNow OAuth2.0’
  5. Enter the 'Owner' of the credential (optional), possibly the creator of this credential.
  6. Click the "Authorization" tab and select "OAuth 2.0" from the ‘Authorization type’ dropdown.mceclip0.png
  7. Select your ‘Saas’, "ServiceNow" from the SaaS dropdown
  8. Type the Subdomain, Client ID and Client Secret you created in your OAuth2.0 App (Step 1 above)
  9. Click "Authenticate" button which will prompt you to log into 'ServiceNow' and authorize the request
  10. Type a useful "Description" which will help you identify the credential (optional)
  11. Click the "Create" button
  12. Finally, you should see the credential you created in the credentials list

Documentation Links:

 

SaaS User Role Block 

Please work through the following steps to configure the SaaS User Role Block for ServiceNow. Configuration of this SaaS User Role block will allow you to capture the ServiceNow "User Role" and the "Last Login" date (coming from your ServiceNow account) within Oomnitza.

 

Pre-requirements:

1. A ServiceNow Credential is added using OAuth2.0 Authentication method as described above.

2. Your ServiceNow SaaS and Contract details with Users are already available within Oomnitza 

 

Steps:

1. Navigate to "Software>Workflow>SaaS Users" as per screenshot below.

mceclip0.png

2. From the SaaS Users Workflow page, select the "Add" button in the top right of your screen, above the grid.

mceclip1.png

3. Give your new Workflow a "Workflow name" (mandatory) and a "Workflow description" (optional) before selecting "Add Item" to create it.

4. From the "Tools" section on the left, drag the "SaaS User Role retrieval block" onto the "Sandbox" section.

Note: All workflows must start with the "Begin" block. The configuration for SaaS User Role blocks can be found here: https://oomnitza.zendesk.com/hc/en-us/articles/360053185893

5. To configure the "SaaS User Role retrieval block", you simply select "Edit" on this block.

6. You will be presented with a two step wizard. Search for the SaaS of choice, in this case, 'ServiceNow'. Select your SaaS using the '>' arrow control as high-lighted below to proceed with the configuration.

mceclip0.png

7. The "Name", "Description" and "Doculink" are all provided for you. You need to select the 'Credential' you created previously for ServiceNow, using the OAuth2.0 authentication method. 

8. Also with the case of ServiceNow, you must also enter your 'Subdomain' 

mceclip1.png

Note: With "Deactivated User" selected, we will automatically reconcile deactivated users from your SaaS system (ServiceNow) back into Oomnitza.

9. Finally, select "Save" and your "SaaS User Role retrieval block' configuration is complete.

10. Your new workflow is ready to run, based off the "Actions" selected if the "Begin" block or else you can run it manually from here.

 

ServiceNow "User Role" and "Last Login" date

Now that your SaaS User Role block has been setup and the workflow has run, you will be able to get the "User Role" and "Last Login" details from your ServiceNow integration.

 

Steps:

1. Navigate to "Software>SaaS" and select your software entry for ServiceNow. Note, that we are continuing to use Zoom for illustrative purposes.

2. From the dialog, navigate to "Users"

mceclip2.png

3. From within "Users", the "Role" and "Last visit" information will be populated directly from your SaaS account (via the SaaS User Role block workflow).

mceclip3.png

 

 

Documentation Links:

 

API block (Presets)

The following ServiceNow API block Presets are available:

  • ServiceNow Delete User

ServiceNow Delete User

Using this setup outlined below, you can create a workflow that would automatically delete a ServiceNow user account within your ServiceNow SaaS which was deactivated from within Oomnitza. 

 

Prerequisites:

1. A ServiceNow Credential is added using OAuth2.0 Authentication method as described above.

2. Your ServiceNow SaaS and Contract details with Users are already setup within Oomnitza 

3. You have run a workflow similar to above which would populate Oomnitza with the actual ServiceNow User Role and Last Login date from your ServiceNow SaaS. 

 

Steps:

1. Navigate to "Software>Workflow>SaaS Users" as per screenshot below.

mceclip0.png

2. With "Workflow: SaaS Users" now selected, you can select the "Add" button in the top right of your screen, above the grid.

mceclip1.png

3. Give your new Workflow a "Workflow name" (mandatory) and a "Workflow description" (optional) before selecting "Add Item" to create it.

4. From the "Tools" section, drag the "API block" onto the "Sandbox" section.

5. To configure the "API block", you simply select "Edit".

6. Select "Show Presets" from the API block dialog. 

mceclip0.png

7. Search for you Vendor, in this case "ServiceNow"

8. "Apply" the Preset you wish to use, "ServiceNow Delete User" in this example.

mceclip1.png

9. A confirmation message will appear on screen your and the URL will be populated on the dialog.

10. You can update the current "Name" on the dialog before moving onto the "Authorization" tab

11. Set the "Type" to "OAuth2.0" and select the "Credentials" that you have previously created as part of the OAuth2.0 authentication method.

mceclip2.png

12. Finally, select "Save" and your "API block' configuration is complete.

13. Your new workflow is ready to run, based off the configuration of the "Begin" block or else you can run it manually from here.

 

Notes:

  • No additional amendments to Parameters, Headers, Body are required for this API Preset to work

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk