> 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-pushover.md).

# Send data to Pushover

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

## Overview

Onum supports integration with [Pushover](https://pushover.net/).

Pushover is a push notification service that delivers real-time alerts to your devices (Android, iPhone, iPad, and Desktop) from various applications and services. It acts as a bridge, allowing you to receive notifications from sources like IFTTT, network monitoring systems, and other software, all through a single, centralized platform.

## Prerequisites 

The prerequisites for sending  notifications to Pushover are straightforward and revolve around obtaining two unique keys:

* **Application API Key** (called **APP Token** in Onum)
* **User Key** (called **User or Group Token** in Onum)

Save these credentials for use in your sink.

## Onum Setup

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

{% step %}
Double-click the **Pushover** 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 %}
The **APP Token**<mark style="color:red;">**\***</mark> (also called an **Application API Key**) is required to send notifications through Pushover's API. Select it from your [Secrets](https://docs.onum.com/administration/global-settings/organization-settings/secrets-management) or create one.\
\
In **Your Application**, if you have already created an application, click it and find the token in its properties.

<figure><img src="/files/GwOY4z8VBDjTKkv27MYP" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
After connecting to the API, connect to a particular user or group using the **User or Group Token**<mark style="color:red;">**\***</mark>. Select it from your [Secrets](https://docs.onum.com/administration/global-settings/organization-settings/secrets-management) or create one.

When you log in to Pushover, you can see this on your homepage under **Your User Key**.

<figure><img src="/files/5l0XYwTeFsJCSRARzIVx" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **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 `100`.
{% endstep %}

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

* **Scheme**<mark style="color:red;">**\***</mark>
* **Host**<mark style="color:red;">**\***</mark>
* **Port**<mark style="color:red;">**\***</mark>
* **Username**
* **Password**&#x20;
  {% endstep %}
  {% endstepper %}

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

## Pipeline configuration <a href="#pipeline-configuration" id="pipeline-configuration"></a>

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>

<table><thead><tr><th width="170.41796875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Raw message</strong><mark style="color:red;"><strong>*</strong></mark></td><td>Choose the field that contains the data to be sent.</td></tr></tbody></table>

Click **Save** to save your configuration.