> For the complete documentation index, see [llms.txt](https://docs.onum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onum.com/data-sinks/data-sink-integrations/send-data-to-servicenow.md).

# Send data to ServiceNow

{% hint style="info" %}
See the changelog of the **ServiceNow** Data sink type [here](/data-sinks-changelog/servicenow-data-sink.md).
{% endhint %}

## Overview

Onum supports integration with [ServiceNow](https://www.servicenow.com/).

ServiceNow is a cloud platform that offers an array of services and applications designed for IT and workflow management. Incidence integration allows Onum to create an instance in ServiceNow when a problem has been detected or to create alerts and possible incidents.

## Prerequisites 

To use the ServiceNow Data sink, you must first create a personal developer instance. ServiceNow offers free [Personal Developer Instances](https://developer.servicenow.com/dev.do#!/guides/washingtondc/developer-program/pdi-guide/obtaining-a-pdi), which you can use to test incidents. 

## Onum Setup

{% stepper %}
{% step %}
Log in to your Onum tenant and click **Data Sinks> New Data sink**.
{% endstep %}

{% step %}
Double-click the **ServiceNow** Sink.
{% endstep %}

{% step %}
Enter a **Name** for the new Data Sink. Optionally, add a **Description** and some **Tags** to identify the Sink.
{% endstep %}

{% step %}
Decide whether or not to include this Data sink info in the metrics and graphs of the [**Home**](/home.md) area.
{% endstep %}

{% step %}
Add your custom **ServiceNow Instance URL**<mark style="color:red;">**\***</mark> or script instance URL.&#x20;

In ServiceNow, go to **Manage > My Instance** to find it. You can also find the URL in your Development Dashboard link. All ServiceNow instances follow the naming convention `https://<INSTANCE NAME>.service-now.com`
{% endstep %}

{% step %}
Enter the credentials to **Authenticate** your connection.

* **Username**<mark style="color:red;">**\***</mark> used to connect to the server
* Create or add a **Password**<mark style="color:red;">**\***</mark> from your [Secrets](/settings/tenant.md).
  {% endstep %}

{% step %}
In the [Secrets](/settings/organization-settings/secrets-management.md) area, **New secret** to create a new one:

* Give the secret a **Name**.
* Turn off the **Expiration date** option.
* Click **Add new value** and paste the corresponding value.
* Click **Save**.

<figure><picture><source srcset="/files/NeeWsSQzoChVxRIY76Nt" media="(prefers-color-scheme: dark)"><img src="/files/1oTccyPmgZJ1laY7IhZH" alt=""></picture><figcaption></figcaption></figure>

{% hint style="info" %}
Learn more about secrets in Onum in [this article](/settings/organization-settings/secrets-management.md).
{% endhint %}

You can now select the created secrets in the configuration.
{% endstep %}

{% step %}
Establish a limit for the **Maximum requests per second**<mark style="color:red;">**\***</mark>. The minimum value is `1` and the maximum value is `10`.
{% endstep %}

{% step %}
If you are using a proxy to establish the connection, toggle on the **Proxy configuration** button and enter the details here.
{% endstep %}
{% endstepper %}

Click **Finish** when complete. Your new Data sink will appear in the **Data sinks** area list.

## Pipeline configuration

When it comes to using this Data sink in a [Pipeline](https://docs.onum.com/the-workspace/pipelines), you must configure the following output parameters. To do it, simply click the Data sink on the canvas and select **Configuration**.

### Output configuration <a href="#output-configuration" id="output-configuration"></a>

You can define the Pipeline fields to be used as **Incident** or **Event** fields in ServiceNow.

#### **Incident**

An unplanned interruption or reduction in the quality of the service. Choose the required input fields for the following categories:

* **Caller ID**
* **Short Description**
* **Category**
* **Correlation Label**
* **Correlation ID**
* **Impact**
* **Description**
* **Severity**
* **Subcategory**
* **Urgency**
* **Additional Comments**

#### **Event**

A notification or signal that something has changed in the system. Choose the required input fields for the following categories:

* **Source**
* **Node**
* **Type**
* **Resource**
* **Metric Name**
* **Source**
* **Message**
* **Severity**
* **Description**
* **Additional Info**

Click **Save** to save your configuration.