ServiceNow
- 27 Jun 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
ServiceNow
- Updated on 27 Jun 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Review the sections below to connect Ushur to ServiceNow.
Authentication Details
Available Operations and Key Data Points
Authentication Details
Authenticate the Service Now Instance URL, Client ID, and Client Secret details. Follow the steps below:
Copy the ServiceNow Instance URL from your browser’s address bar after logging into your instance.
.png "image(760).png")
You must create an OAuth application to obtain the ClientID and ClientSecret. Log in to your ServiceNow account, click All > Filter Navigation, and type Application Registry.
.png "image(761).png")
The menu of Application Registries is displayed. Click New.
.png "image(763).png")
Provide the required details. You can use https://auth.tray.io/oauth2/token as your redirect URL.
.png "image(764).png")
Search the Application name you added previously and copy the Client ID and Client Secret values as shown below.
.png "image(765).png")
.png "image(760).png")
.png "image(761).png")
.png "image(763).png")
.png "image(764).png")
.png "image(765).png")
Connecting Ushur to ServiceNow
Click on the ServiceNow solution and select Click to Setup.
.png "image(766).png")
Provide the authentication name, Instance URL, Client ID, and Client Secret information, and click Create.
.png "image(767).png")
After specifying the authentication details, select Allow to connect ServiceNow account to gain access.
.png "image(768).png")
Click Finish after authentication is completed.
.png "image(770).png")
ServiceNow is connected to Ushur.
.png "image(771).png")
.png "image(766).png")
.png "image(767).png")
.png "image(768).png")
.png "image(770).png")
.png "image(771).png")
Available Operations and Key Data Points
Operations | Fields | Values |
Create Incident | Entity* | Incident |
Request Key | N/A | |
Request Data* | short_description(mandatory) | |
Response Data | externalId | |
Auto-Suggestion available for External System Entity | No | |
Auto-Suggestion available for Data Fields | No | |
Get Incident | Entity* | Incident |
Request Key* | Number(mandatory) | |
Request Data | N/A | |
Response Data | short_description, externalId | |
Auto-Suggestion available for External System Entity | No | |
Auto-Suggestion available for Data Fields | No | |
Update Incident | Entity* | Incident |
Request Key* | externalId (mandatory) | |
Request Data | short_description | |
Response Data | short_description, externalId | |
Auto-Suggestion available for External System Entity | No | |
Auto-Suggestion available for Data Fields | No | |
Create User | Entity | user |
Request Key | N/A | |
Request Data* | Mandatory and must be specified in the order mentioned here. firstname, lastname, gender | |
Response Data | sys_id, name, email, phone, | |
Auto-Suggestion available for External System Entity | Yes | |
Auto-Suggestion available for Data Fields | Yes |
Was this article helpful?