How to get started with ServiceNow in Qlik Application Automation
This article provides information on how to get started with the ServiceNow connector in Qlik Application Automation. The connector for ServiceNow is making use of Basic Authentication. To connect you will also need the name of your instance.
Authentication and Authorization
When you connect to ServiceNow in Qlik Application Automation you will be presented with the following screen. You can obtain the instance name from the URL that you use to access ServiceNow. You can use your username / password of your account provided it has enough privileges for what you aim to do. It is recommended to create a service account for integrations and limit it's roles to what is necessary.
The following data types have easy to use blocks for all CRUD operations: • Incident • Change Task • Problem • Change Request
Furthermore it is possible to work with user objects, listing journal items, audit lines, obtaining and adding attachments. When modifying or deleting objects from the Table API, make sure to be using the "sys_id" field of objects as the identifier.
Custom API blocks
With the blocks "get table content by id", "create table content", "delete table content", "update table content", "list table content", it is possible to work with every object through the use of the Table API. These blocks also allow you to look up the name of a table with the "do lookup" functionality. As this lookup obtains information from the sys_db_object table in ServiceNow, it's possible that this lookup does not work due to your permissions.
There is also a "Raw API Request" available. This block allows providing your own sub path starting from the Base URL of ServiceNow, HTTP method and optionally a JSON body. This can be used to contact other API groups than the Table API of ServiceNow as well as custom scripted API's.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.