> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/administration/ai-resources/managing-request-catalogs.md).

# Managing Request catalogs

Configure Request catalogs for Nexthink Spark to autonomously process common requests, grounded in your organization's list of active, orderable IT services. Import the list of catalog items as CSV files, or connect to a live external system, then classify and manage each source from one central location.

{% hint style="info" %}
Request catalogs configuration is available only for **Spark.** Refer to for information on how Spark uses request catalogs.
{% endhint %}

## Accessing Request catalogs

Select **Administration > Request catalogs** from the navigation panel.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2F8uIznACZHErbi1aPEWuA%2Faccess_request-catalogs_2026-09-09_11-02-47.png?alt=media&#x26;token=7979503f-b263-407a-99bd-aacde6c68b4e" alt=""><figcaption></figcaption></figure>

## Connecting Nexthink to request catalogs

To connect Nexthink to request catalogs, follow one of these options:

* Configure an **inbound connector** to connect to a live external system.
* **Import request catalogs** from a CSV file.

Refer to the procedures described on this page for details.

### Connecting to a live external request catalog

From the top right corner of the **Request catalogs** page, use **New request catalog** **connector** to connect to a live external system, such as ServiceNow. The system navigates to the **New connector - ServiceNow Request Catalog** page where you can provide your configuration details.

Optionally, create a new inbound connector directly from the [Inbound connectors management page](/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors.md).

Refer to [ServiceNow Request Catalog connector](/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/connector-for-servicenow-request-catalog.md) for connector setup.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2F9McGKAOThUiLORVBJi4S%2Fnew_request_catalog_2026-09-09_13-34-09.png?alt=media&#x26;token=e5d8d360-0c54-4b14-9ba5-a35004c7d69d" alt=""><figcaption></figcaption></figure>

### Importing a request catalog from a CSV file

Each imported CSV file is treated as an independent request catalog and is processed independently. Multiple request catalogs can coexist.

The following procedure uses ServiceNow as an example; however, on a high level, the process is similar in other ITSM platforms.

{% stepper %}
{% step %}

#### Identify data to export from your ITSM

1. Open the list of catalog items in your ITSM. In this case, ServiceNow's Service Catalog.
2. Select catalog items by applying these filters:
   * Published items only
   * Items available to your service desk users.
   * Exclude translated versions of the same item.
   * Include every item you want to import.

{% hint style="warning" %}
Spark indexes every uploaded item regardless of ITSM permissions.
{% endhint %}
{% endstep %}

{% step %}

#### Export data from your ITSM

Export data from your ITSM, in this case ServiceNow, by performing a standard CSV export:

After you configured the desired filters, personalize the items list by including the following columns in the CSV. Use the exact case-sensitive column names listed in the table below.

{% hint style="warning" %}
Ensure the file is UTF‑8 encoded. If your ServiceNow instance is not configured to perform UTF-8 exports by default, convert the file to UTF-8 afterward.
{% endhint %}

<table><thead><tr><th width="212.16668701171875">Column name</th><th>Description</th></tr></thead><tbody><tr><td><code>number</code></td><td>Identifier of the request catalog item.<br>Example: 67429650877bcd1029c687f60cbb3563</td></tr><tr><td><code>name</code></td><td>Title of the request catalog item.<br>Example: Keybaord and Mouse</td></tr><tr><td><code>short_description</code></td><td>Short description of the request catalog item.<br>Example: <code>"Request Keyboard and Mouse"</code></td></tr><tr><td><code>description</code></td><td><p>Description of the request catalog item.</p><p><code>Example: "Provide any relevant details, including whether you need a standard wired set, a wireless set, or an ergonomic alternative."</code></p></td></tr><tr><td><code>category</code></td><td>Category of the request catalog item.<br>Example: <code>Hardware</code></td></tr></tbody></table>
{% endstep %}

{% step %}

#### Upload the CSV file to Nexthink

In Nexthink, **Import** request catalogs from the top-right corner of the **Request catalogs** page.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fcnis9Nhrsc993F6CgsDu%2FiMPORT-REQUEST-CATALOG-2026-09-10_10-59-12.png?alt=media&amp;token=845612da-7494-4698-841d-64f27761e6f0" alt=""><figcaption></figcaption></figure>

<details>

<summary>Enter the source URL</summary>

Provide a full, parameterized URL that links to individual items in your ITSM, including a placeholder for the item identifier. Root-only hostnames aren't supported: `https://example.company.com/path/to/item/{number}`

URL example for ServiceNow: `https://<instance>.service-now.com/sp?id=sc_cat_item&sys_id={number}`

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FKIb8Uo8f8YlLtoqaKoXD%2Fimporting_RC_2026-09-10_11-00-05.png?alt=media&amp;token=f42a4bf9-2bfd-427a-afbd-0dadcfaa83b7" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary>Upload the CSV file</summary>

Drag and drop your CSV file into the upload area, or **Choose file** to browse—up to 100 MB per file. Each row in the file represents one request catalog item.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FDWrmcsywCg028em37uf2%2Fuploading_RC_2_2026-09-10_11-00-25.png?alt=media&amp;token=b0952500-9ce7-4cd8-a4f2-08f7c8ec4f41" alt=""><figcaption></figcaption></figure>

After choosing a CSV file, the dialog displays the file name and size.

If an error occurs during import, the dialog displays a warning message. Check your file and retry the import.

{% hint style="success" %}
Once the import succeeds, the system validates the file and displays a confirmation indicator.
{% endhint %}

</details>

File processing occurs asynchronously and may take up to 15 minutes for large request catalogs.

{% hint style="warning" %}
Manual uploads are not incremental. When uploading a new CSV file into Nexthink, the new content replaces the previous content.
{% endhint %}
{% endstep %}
{% endstepper %}

#### Updating manually imported request catalogs

To ensure Nexthink Spark always has a request catalog available, even when the system is processing a new version of a request catalog file, Nexthink recommends the following order:

1. Upload the updated request catalog file while still leaving the old one in the system.
2. Once the new request catalog file is processed, delete the old file.

{% hint style="info" %}
Nexthink recommends the following best practices to improve the selection of request catalog items:

* Keep items current and up to date.
* Include key information in the item description.
  {% endhint %}

***

## Managing request catalog sources

The **Request catalogs** page lists every imported or connected catalog source. Each table row shows:

* **Name:** the CSV file name or connector name.
* **Origin:** how the source was added. Imported and connected sources both show as **Custom**.
* **Type:** **Connector** or **File**, depending on how the source was added.
* **Size**: the number of articles in the CSV. The system can also display the following statuses:
  * **Failed**: if the file cannot be processed, for example, if it contains a syntax error. In this case, hover over the error message to see more details and a remediation proposal.
  * **Processing**: if the file contains many articles, it may take the system time to process.
* **Last update:** when the source was last imported or synced—helps to assess if an article is up to date.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FqxOF2R4zQ6jAlxREK5xC%2Fmanaging_RC_2026-09-10_10-59-31.png?alt=media&amp;token=1bd6f9d7-732f-4f1b-9445-b1762f90f630" alt=""><figcaption></figcaption></figure>

### Request catalog actions

From the table, hover over a request catalog to reveal the action menu on the right side of the row. Depending on the request catalog type, you can:

* **Edit:** update the settings of an existing request catalog.
* **Export**: Download the original CSV file corresponding to the last successful import. Each request catalog CSV file can be exported only individually.
* **Delete**: Permanently remove a previously uploaded CSV and all request catalog items associated with it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexthink.com/user-guide/administration/ai-resources/managing-request-catalogs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.