Connecting ServiceNow
incident.io connects to ServiceNow using an OAuth app and a Web Service user account. Sync is bi-directional: updates made in ServiceNow flow back to incident.io, not just the other way. Installing our ServiceNow app makes that back-sync real-time, so we recommend it. If you’d rather not, grant the service account theadmin role instead.
If you’re setting up the ServiceNow alert source, make sure you install the ServiceNow app.
Choose an authentication method
incident.io supports two OAuth grants. Pick one before you start, because some steps differ.- Client credentials (recommended): incident.io signs in with the OAuth app’s client ID and secret. Requires ServiceNow Washington DC or later.
- Resource owner password: incident.io signs in with the OAuth app and the service account’s username and password.
- Turn on the client credentials grant with a system property (step 2).
- Set the service account as the OAuth app’s OAuth Application User (step 4).
1. Install the ServiceNow app
Install the incident.io app from the ServiceNow Store. To skip the ServiceNow app installation, grant theadmin role in step 3 instead.
2. Create an OAuth App
Log in to ServiceNow and search for OAuth in the filter navigation:

- Client credentials
- Resource owner password
Select New Inbound Integration Experience.
Click New Integration.
Click OAuth - Client credentials grant.Enter ‘incident.io’ for the name, and leave other options as the defaults. Click Save.
Find the app you’ve just created in the list. Copy the Client ID and Client Secret values: we’ll need them later!ServiceNow turns off the client credentials grant by default. To turn it on, search for



sys_properties.list in the filter navigation and press Enter. Click New, then create a property with these values:- Name:
glide.oauth.inbound.client.credential.grant_type.enabled - Type:
true | false - Value:
true
3. Create a Web Service Account
Any ServiceNow user account can be used so long as it has the relevant roles assigned. However, any actions taken by incident.io in ServiceNow will appear as being taken by this user account, so we strongly recommend creating a user for this purpose only.


x_incident_io.api_user: shipped by the app. Grants incident.io the API access it needs for sync configuration and incident writes.cmdb_read: allows us to read data from your Configuration Management Database.sn_cmdb_user: allows us to read information about users and groups in your ServiceNow account.incident_manager: allows us to sync incident data into ServiceNow incident records.
admin role instead, which gives incident.io full access to your ServiceNow instance.


4. Set the OAuth Application User
Skip this step if you’re using resource owner password.
5. Create ACLs
If you granted the
admin role in step 3, you can skip this step, as admin already covers it.task table, so the service account needs create, read, and write access (the app doesn’t grant access to task itself).
To add ACLs, you first need to elevate your user to Security Admin. Click your profile icon and select Elevate role.




- Type:
record - Operation:
read - Application:
Global - Active: checked
- Decision Type:
Allow If - Admin overrides: checked
- Name: select
taskin the first dropdown, and leave the second as-- None --.

x_incident_io.api_user.

task ACLs assigned to x_incident_io.api_user.
6. Installing the integration
We’re now ready to install the ServiceNow integration in incident.io. Go to Settings → Integrations, and click on ServiceNow, then Connect.
- For Authentication method, choose Client credentials or Resource owner password, to match the method you set up.
- Your subdomain is the part of the URL where you log in to ServiceNow. For example, if your ServiceNow instance is accessed at
hyper-payments.service-now.com, your subdomain ishyper-payments. - Your OAuth Client ID and OAuth Client Secret are the credentials you created in step 2.
- Your Username is the User ID of the service account you created in step 3, such as
incident.io. Don’t enter its display name. - If you’re using resource owner password, your Password is the one you generated in step 3. Client credentials doesn’t ask for a password.
- Click Connect to verify your credentials and complete the connection.
Exporting follow-ups
Follow-ups are created on thetask table, with the follow-up title as short_description, its description as description, and the linked incident’s ticket as parent. A new task starts in state 1 (Open).
The follow-up owner is managed in incident.io, so assigning the ServiceNow task to someone doesn’t change it.
ServiceNow states map back to follow-up statuses in incident.io:
Syncing ServiceNow tables into Catalog
You can sync any ServiceNow table, such as a CMDB class, into Catalog. On the Catalog page, open the dropdown next to Add a custom type, then search for the table under Import another type. Each row becomes a catalog entry, and the type syncs every hour. By default, if the table has anactive column, only active rows are imported.
Filter entries before syncing
Large tables often hold far more rows than you want in Catalog. To import only some of them, edit the catalog type and turn on Filter entries before syncing. Then pick the fields to filter on and the values to keep.- Choice and true/false fields offer the values stored in ServiceNow. Text and number fields take values you type.
- An entry is imported when it matches any of the values for a field, and every field you filter on.
- Reference and date fields can’t be used as filters.

active check. To keep only active rows, add a filter on Active.
If a field you filter on is later removed from the table, the form warns you, and saving removes that field’s filter.
FAQs
Why doesn't changing an incident's severity update its ServiceNow priority?
Why doesn't changing an incident's severity update its ServiceNow priority?
Most ServiceNow configurations calculate Priority from Impact and Urgency. ServiceNow rules can
therefore overwrite a value written directly to Priority. In your incident ticket
template, map the incident severity to both
Impact and Urgency instead. ServiceNow will use those values to calculate the expected priority.

