What Traversal reads
Traversal reads each of the following tables withGET /api/now/table/{table}.
Use this table as the source of truth for the read access the ServiceNow integration needs on a standard instance. Traversal needs read access to these tables and no others, and no write access to any of them.
Additional endpoints
Traversal also calls two endpoints outside the Table API:
The Batch API call carries its sub-requests in the request body. Traversal puts one
GET per metric there, in the form:
The Batch API call is an HTTP
POST, but it is still read-only. The method is a POST because ServiceNow’s Batch API takes its sub-requests in the request body, and Traversal only ever puts GET requests there. The call creates and modifies no records.Custom tables
Some ServiceNow instances are customized enough that Traversal needs to read an additional or custom table, such as a database view that replaces a standard table. Traversal identifies any such tables with you during onboarding and adds them to the list above for your deployment. The tables in this page are what a standard ServiceNow instance requires.Before you start
Ask your ServiceNow administrator for:- your ServiceNow instance URL, such as
https://your-instance.service-now.com - your token URL, which is usually
https://your-instance.service-now.com/oauth_token.do - an integration user with read access to the tables listed in What Traversal reads
- if you want ACC metrics, whatever Clotho or ACC permissions your instance requires for metrics access
snc_read_only for general table reads and sn_clotho_user for Clotho metrics access, but ServiceNow roles vary by module, release, and instance customization. Confirm the exact role set with your ServiceNow administrator instead of assuming one universal combination.
Setup
1
Choose how you want to sign in
- OAuth client credentials
- Username and password
Use this option when your administrator gives you a dedicated OAuth application’s Client ID, Client Secret, and token URL.
2
Gather the values Traversal needs
In Traversal, you will enter:
- Instance URL
- Token URL
- either Client ID and Client Secret, or Username and Password
3
Configure in Traversal
Go to Company Knowledge > Integrations, select ServiceNow, and enter:
- Instance URL (e.g.,
https://your-instance.service-now.com) - Auth type — select the option that matches the credentials your administrator provided
- Token URL
- For client credentials: Client ID and Client Secret
- For username and password: Username and Password
- the credentials have read access to every table in What Traversal reads
- the token URL is the correct
oauth_token.doendpoint for your instance or custom domain - the integration user is allowed to use ServiceNow web services
FAQ
Which authentication method should I use?
Which authentication method should I use?
Use OAuth client credentials if your administrator can issue a dedicated OAuth app for Traversal. Use Username and password if your administrator prefers an integration user account. Both methods let Traversal obtain OAuth access tokens automatically, but the operational difference is whether your administrator manages an OAuth app or a user credential.
Does Traversal write to any ServiceNow tables?
Does Traversal write to any ServiceNow tables?
No. Traversal only makes read-only API calls. No records are created, updated, or deleted.One call uses the
POST method: POST /api/now/v1/batch, which Traversal uses to fetch ACC / Clotho metrics. ServiceNow’s Batch API takes its sub-requests in the request body, which is why the call is a POST, and Traversal only puts GET requests there. If your security review flags the method, this is the call it found.What is the minimum access Traversal needs?
What is the minimum access Traversal needs?
Read-only access to the tables in What Traversal reads, plus the additional endpoints if you want attachments and ACC metrics. Traversal needs nothing beyond read access to those. See Before you start for guidance on the roles that grant it.