> 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/workflows/creating-workflows/configuring-connector-thinklet/servicenow-service-catalog.md).

# ServiceNow - Service catalog connector thinklet

Configure ServiceNow - Incident management connector thinklets to take specific actions within your workflow.

## Action: Get service catalog item <a href="#action-get-service-catalog-item" id="action-get-service-catalog-item"></a>

**Get service catalog item** retrieves detailed service catalog item data. This action is utilized in workflows, for instance, to retrieve the internal ID of a service catalog item, which is necessary for other actions related to ordering the service. The Thinklet relies on the [Service Catalog - GET /sn\_sc/servicecatalog/items](https://docs.servicenow.com/bundle/washingtondc-api-reference/page/integrate/inbound-rest/concept/c_ServiceCatalogAPI.html#title_servicecat-GET-items) API endpoint.

Example of Thinklet setup:

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-2c394ac3fde426870abec66b29527595ce575972%2Fimage-20240614-113447.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* **Parameters:** Configure the data used as parameters for this action. Hover over the tooltip icon for more information on how the parameter is mapped and what data is required.
  * **Search text** - Text for searching service catalog items
* **Outputs:** View the outputs of the connector thinklet.
  * **Service catalog item ID** (`ServiceCatalogItemID`)
  * **Name** (`Name`) - Service catalog item name
  * **Short description** (`ShortDescription`) - Service catalog item short description
  * **Availability** (`Availability`) - Service availability
  * **Type** (`Type`)
  * **Class name** (`ClassName`)

Details of API Service thinklet when recreating the connector:

<table><thead><tr><th width="272">Field</th><th>Value</th><th data-hidden></th></tr></thead><tbody><tr><td>Resource Path</td><td>api/sn_sc/servicecatalog/items?sysparm_limit=1&#x26;sysparm_text={{SerachText}}</td><td></td></tr><tr><td>Method</td><td>GET</td><td></td></tr><tr><td>Payload</td><td></td><td></td></tr><tr><td>Outputs</td><td><p>Availability $.result[0].availability</p><p>Name $.result[0].short_description</p><p>ShortDescription $.result[0].short_description</p><p>ClassName $.result[0].sys_class_name ServiceCatalogItemID $.result[0].sys_id</p><p>Type $.result[0].type</p></td><td></td></tr></tbody></table>

## Action: Request service catalog item <a href="#action-request-service-catalog-item" id="action-request-service-catalog-item"></a>

**Request service catalog item** places an order for catalog item which results in the creation of service request ticket. The Thinklet relies on the [POST /sn\_sc/servicecatalog/items/{sys\_id}/order\_now](https://docs.servicenow.com/bundle/washingtondc-api-reference/page/integrate/inbound-rest/concept/c_ServiceCatalogAPI.html#title_servicecat-POST-items-order_now) API endpoint.

Example of Thinklet setup:

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-cd45d0d8f7c1b4b8146b2b9bf5f0ab7579830e70%2Fimage-20240613-160938.png?alt=media" alt=""><figcaption></figcaption></figure>

* **Parameters:** Configure the data used as parameters for this action. Hover over the tooltip icon for more information on how the parameter is mapped and what data is required.
  * **Service catalog item ID** (`ServiceCatalogItemID`) - Service catalog item ID
  * **Requested for user ID** (`RequestedForUserID`) - Requested for user ID
  * **Quantity** (`OrderQuantity`) - Ordered service quantity
* **Outputs:** View the outputs of the connector thinklet.
  * **Request number** (`RequestNumber`)
  * **Request ID** (`RequestID`)

The table below provides the details of the API Service connector when re-creatu:

<table><thead><tr><th width="272">Field</th><th>Value</th><th data-hidden></th></tr></thead><tbody><tr><td>Resource Path</td><td><code>api/sn_sc/servicecatalog/items/{{ServiceCatalogItemID}}/order_no</code></td><td></td></tr><tr><td>Method</td><td><code>POST</code></td><td></td></tr><tr><td>Payload</td><td><code>{"sysparm_requested_for":"{{RequestedForUserID}}","sysparm_quantity":"{{OrderQuantity}}"}</code></td><td></td></tr><tr><td>Outputs</td><td><p><code>RequestNumber $.result.number</code></p><p><code>RequestID $.result.sys_id</code></p></td><td></td></tr></tbody></table>

## Action: Update service catalog request descriptions <a href="#action-update-service-catalog-request-descriptions" id="action-update-service-catalog-request-descriptions"></a>

**Update service catalog request description** updates the service catalog request ticket description and short description fields. The Thinklet relies on the [Table request PATCH](https://docs.servicenow.com/bundle/washingtondc-api-reference/page/integrate/inbound-rest/concept/c_TableAPI.html#title_table-PATCH) API endpoint.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-e176b9208161ee6d79eb6c476d4b949833764a08%2Fimage-20240618-112009.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* **Parameters:** Configure the data used as parameters for this action. Hover over the tooltip icon for more information on how the parameter is mapped and what data is required.
  * **Request ID** (`RequestID`) - Request ID
  * **Description** (`Description`) - Description
  * **Short description** (`ShortDescription`) - Short description
* **Outputs:** View the outputs of the connector thinklet.
  * **Request number** (`RequestNumber`)
  * **Request ID** (`RequestID`)

The table below provides the details of the API Service connector when recreating the connector:

<table><thead><tr><th width="272">Field</th><th>Value</th><th data-hidden></th></tr></thead><tbody><tr><td>Resource Path</td><td>api/now/table/sc_request/{{RequestID}}</td><td></td></tr><tr><td>Method</td><td>PATCH</td><td></td></tr><tr><td>Payload</td><td>{"description":"{{Description}}","short_description":"{{ShortDescription}}"}</td><td></td></tr><tr><td>Outputs</td><td><p>RequestNumber $.result.number</p><p>RequestID $.result.sys_id</p></td><td></td></tr></tbody></table>

Refer to the [Configuring connector thinklets](/user-guide/workflows/creating-workflows/configuring-connector-thinklet.md) documentation for more information about connector thinklets.


---

# 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/workflows/creating-workflows/configuring-connector-thinklet/servicenow-service-catalog.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.