---
title: "Webhook Support for Sensor Notifications"
slug: "sensor-notifications-webhook-support-for-sensor-notifications"
updated: 2026-10-16T14:44:45Z
published: 2026-10-16T14:44:45Z
canonical: "documentation.lakesidesoftware.com/sensor-notifications-webhook-support-for-sensor-notifications"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhook Support for Sensor Notifications

Webhooks allow interaction between web-based applications through the use of custom callbacks. The use of webhooks allows web applications to automatically communicate with other web-apps.

SysTrack supports webhooks for activated sensor notifications in addition to setting up email and webhook notifications.

Notifications can have both webhooks and email addresses.

When a sensor notification threshold is reached, SysTrack sends an HTTP request with information about the notification to a third party.

Multiple notifications can go to the same webhook and you can set up webhooks on a per notification basis. However, two webhooks cannot share the same name.

For information about integrating with Qualtrics, see [Operational Pulse Integration with Qualtrics](/documentation/docs/operational-pulse-integration-with-qualtrics).

[Sensor Notifications with Webhooks](https://player.vimeo.com/video/902262047?h=501e56ea2c&badge=0&autopause=0&player_id=0&app_id=58479)

## Set Up Webhooks in SysTrack

> [!NOTE]
> **NOTE:** In SysTrack On-Premises, webhook setup has no **Notification Type** row, and the master server must be connected to the internet. See [Webhooks for Sensor Notifications](/documentation/docs/onpremises-configure-differences-from-cloud#webhooks-for-sensor-notifications) in Differences in Configure for On-Premises.

After you create a webhook, you can reuse it for subsequent notifications.

1. Add a recipient. See [Sensor Notification Recipients](/documentation/docs/sensor-notification-recipients).
2. In **Recipient Type**, select **System** and enter a name.
3. In **Connection**, select **Webhook**.
4. In **Notification Type**, select **Sensor Notification**. For more information on Anomaly Notifications, see [Anomalies](/documentation/docs/systrack-ai-anomalies#system-notifications-for-webhooks).
5. Enter the URL. This URL will come from the third-party system that is receiving the webhook.
6. In **Request Method**, select one of the following:
  - POST: creates a new resource in the third-party application where the webhook is being sent.
  - PUT: updates a resource in the third-party application where the webhook is being sent.

> [!NOTE]
> **NOTE:** The POST and PUT settings will depend on the third-party you integrate with.

1. In **Authentication**, select one of the following options:

> [!NOTE]
> **NOTE:** Existing webhooks created with the previous **Off** option will continue to work. When editing these webhooks, the Specify **Authentication via a Header** option will appear selected.
  - **Basic Auth**: Enter the username and password associated with the third-party system. Both username and password are required for this authentication method.
  - **Signed Secret**: Manually enter your own secret text or click **Generate New** to automatically create one. This field is required for this authentication method.

The secret is passed in a webhook header so that the receiving system knows it is coming from a valid source. For details, see [Signed Secret Authentication for Webhooks](/documentation/docs/signed-secret-authentication-for-webhooks).

> [!WARNING]
> **IMPORTANT:** The secret is only shown in the UI at this time. Make sure that you store the secret somewhere safe.
  - **Specify Authentication via a Header**: Authenticate using a custom header, such as an API key or bearer token, instead of Basic Auth or a signed secret.

> [!NOTE]
> **NOTE:** This option does not enforce adding a header, but it is recommended for production environments.
2. In **Headers**, select the plus sign to add multiple, unique headers. Headers are optional.

> [!NOTE]
> **NOTE:** If you select the **Sensitive** checkbox, when you save, the value for that header will not be shown in the interface again.
3. In **Body**, enter a custom template for the content of the webhook payload. A default JSON body template displays in this section for you to use as a starting point for the webhook body. For more information, see [Sensor Notification Webhook Body Templates](/documentation/docs/sensor-notification-webhook-body-templates).
4. Click **Add Recipient**.

![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/webhooks111.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A44%3A58Z&se=2026-11-08T17%3A44%3A58Z&sr=c&sp=r&sig=hvCPw6UATet%2B1YCbNFIxmNryfhr8jn4LJWBRc9yNmAM%3D)

For more information about using third-party applications and webhooks, see the following:

- [Configure Webhook Reception in Teams](/documentation/docs/configure-webhook-reception-in-teams)
- [Configure Webhook Reception in ServiceNow](/documentation/docs/configure-webhook-reception-in-servicenow)
- [Configure Webhook Reception in Slack](/documentation/docs/configure-webhook-reception-in-slack)
- [Configure Webhook Reception in PagerDuty](/documentation/docs/configure-webhook-reception-in-pagerduty)