# ServiceNow Request Catalog connector

The ServiceNow Request Catalog connector provides a secure and configurable integration with the ServiceNow Service Catalog and Employee Profile modules. It enables automated retrieval, validation, and submission of service requests, supporting common use cases such as software provisioning, access changes, and equipment orders. By aligning with existing ServiceNow workflows and approval processes, the connector extends capabilities beyond incident management to include catalog-driven requests, while maintaining ServiceNow as the system of record.

The data provided by this connector is only used by [Spark](/platform/user-guide/spark.md).

## Configuring the Connector credentials

To allow Nexthink to retrieve items from your ServiceNow Request Catalog, you need to set up a dedicated integration account in ServiceNow with the right level of access.

When Nexthink fetches Request Catalog data, it does so by calling the following ServiceNow API endpoint:

`GET /api/sn_sc/servicecatalog/items`

ServiceNow controls which catalog items this API returns based on the permissions of the user making the request. This means the ServiceNow account that Nexthink uses must be correctly configured, not just to authenticate, but also to see the right catalog items.

Follow the steps below to configure the ServiceNow credentials used to fetch the request catalog:

1. Create a dedicated active ServiceNow user account for Nexthink integration in the ServiceNow Admin Console and enable it for API authentication.
2. Assign only the minimum required API access roles, such as `snc_internal`, to the Nexthink integration user in ServiceNow Roles administration.
3. Create a dedicated ServiceNow User Criteria record for the Nexthink connector and include the Nexthink integration user in it. Apply the Nexthink User Criteria at
   * **Catalog level** when Nexthink should ingest all accessible items in a catalog.
   * **Category level** when Nexthink should ingest items only from selected categories.
   * **Catalog item level** when Nexthink should ingest only specific items or when item-level visibility must be explicitly controlled.
4. Configure the Nexthink User Criteria in the **Available For** section of the relevant catalog, category, or catalog item configuration.

Refer to the [Connector credentials](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/connector-credentials.md) documentation for more information about connector credentials.

## Configuring the ServiceNow Request Catalog connector

From the Nexthink web interface:

1. Go to **Administration** > **Inbound connectors**.
2. Click the **New connector** button in the top-right corner of the page.
3. Select **ServiceNow Request Catalog**.

### General tab

* **Name**: A meaningful name for the connector. This name appears on the administration page.
* **NQL ID**: A unique identifier for the connector used when referencing the ServiceNow connector in NQL queries. You can initially modify the suggested NQL ID, but once you save the connector, you can no longer change it.
* **Description**: A short description of the purpose and behavior of the connector.
* **Schedule**:
  * **Recurrence**: Set the execution time and recurrence. Executions start at the scheduled time and distribute over the hour.
* **Connection:**
  * **Credentials**: Select preconfigured credentials from the [Connector credentials](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/connector-credentials.md) page. The credentials must be of a dedicated integration user whose user-criteria assignments mirror a standard employee, ensuring the API returns only the catalog items that are visible to all employees. The connector supports OAuth 2.0, Basic Auth and Bearer authentication methods.

<figure><img src="/files/nl6XVwe5SGGDUrNDY1kf" alt=""><figcaption></figcaption></figure>

### Parameters tab

* **Query (optional)**: A single full-text search string. Examples:
  * Type "keyboard" to fetch catalog items containing the "keyboard" keyword.
  * Type "keyboard OR mouse" to fetch items containing "keyboard" or "mouse" keywords
* **External link**: The ServiceNow hostname, often matching the URL configured in the connector credentials, used to link to the request items.
* **Custom header**: Use a custom header to include additional credential information in OAuth 2.0 authentication methods, such as **Client Credentials** and **Authorization Code**. This is useful when additional authorization methods are needed beyond the default OAuth 2.0 authorization mechanism. Select **Add custom header** to include additional information in either **OAuth 2.0 - Client credentials** or **OAuth 2.0 - Authorization code** authorizations.

<figure><img src="/files/7liSl5m30mtvsXcf85Sv" alt=""><figcaption></figcaption></figure>

## Test results panel

{% hint style="info" %}
The **Test results** panel is available only for supported connectors. Connector availability also depends on your license.
{% endhint %}

Use the **Test results** panel on the right side to run the connector with real data on demand, and inspect responses and errors. The test panel helps with faster debugging and validation during setup, and also with more reliable mappings with less trial and error.

Select the **Run test** button to call the API, validate the credentials, and check connectivity to the targeted endpoint.

<figure><img src="/files/ArSvwSaC2WQbO2lypKSA" alt=""><figcaption></figcaption></figure>

Besides basic information, such as the response status code and time, the panel also shows a sample record of the response at the bottom.

<figure><img src="/files/Z1VrzzOWvFnxIgsOOKqZ" alt="" width="316"><figcaption></figcaption></figure>

In the event of an error, the system displays the API response to aid in diagnosing the issue.

<figure><img src="/files/le130lodDCk1yPY02v87" alt="" width="309"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/connector-for-servicenow-request-catalog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.