Setting an Alert Notification Channel
  • 19 Jul 2022
  • 3 Minutes to read
  • Dark

Setting an Alert Notification Channel

  • Dark

By default, your users are notified via their email addresses registered with Sisense. In addition, Sisense supports a variety of workflows by sending notifications across multiple applications and services. For example, your users can receive notifications through the Sisense mobile application, Zapier, Slack, and other 3rd services via webhooks.

To define how users are notified:

  1. For Build Alerts, select the tab.

  2. For Data Alerts, select Advanced Options > .


  3. In the Notifications area, select the relevant channel for your notification. The default channel, Email, is already selected.

    You can select one or more of the following channels:

    • Email
    • Mobile
    • Slack
    • Zapier
    • Webhook
  4. Click Save.

Sisense Mobile

Sisense Mobile enables users to view Sisense dashboards through their mobile devices. You or your users can receive notifications through Sisense Mobile. After selecting the users you want to notify, any users with a Sisense user account and Sisense Mobile will receive a notification when an alert is triggered.



Slack is a real-time team collaboration messaging platform that allows you to receive incoming Webhooks from external sources such as Sisense. To send notifications through Slack, you need to enter the URL and optionally, your Slack channel or username, where the notification is to be displayed.

You can obtain these details by adding the Incoming WebHooks app into your Slack configuration.

For a quick walkthrough of configuring Pulse notifications in Slack, see the tutorial below.

To obtain a Webhook URL and channel from Slack:

  1. Add the Incoming WebHooks app to Slack. You can find this app in Slack’s App Directory.

  2. In the Incoming WebHooks app page, click Add Configuration.

  3. After you add the Incoming WebHooks app, you can select which channel to post the notifications to. The channel name is optional and displays the notification in the channel associated with your WebHook URL. In the Post to Channel area, select the channel where the notification is to be displayed and click Add Incoming WebHooks integration.


  4. In the Setup Instructions the Webhook URL is displayed. Copy the Webhook URL.


  5. In Sisense when sending notifications through Slack, in the URL field, enter the URL copied in the previous step and in the #channel/@username field, enter the channel name if you have defined one.


Zapier is an online service that lets you create automated actions connecting disparate business apps and services such as Sisense. To receive notifications through Zapier, you must create a Zap and provide Sisense with the relevant URL when configuring your alerts’ notifications.

When an alert is triggered, Sisense sends the notification to the Webhook you define in Zapier.

To obtain a Webhook URL from Zapier:

  1. Log in to Zapier and click Make a Zap. The Trigger App page is displayed.

  2. From the Trigger App page select Webhooks. The Connect to Webhooks by Zapier page is displayed.

  3. In Step 1 > Set Up Webhook, click Copy to clipboard to copy the Webhook URL you need to provide to Sisense.


  4. In Sisense, when sending notifications through Zapier, in the URL field, enter the URL copied in the previous step.


Webhooks are a system of automated notifications that indicate that an event occurred, in this case an alert being triggered. To send notifications through additional 3rd party channels, you can select Webhook and enter the Webhook name and URL.

Your Webhook server listens for incoming messages from Sisense across the URL specified in the URL field.

When Sisense sends notifications to your custom Webhook, they are sent within a JSON payload. Your Wehbook provider must interpret the payload and display the notification to your users. The following exampleof notifications sent in a JSON payload and a description of the contents of the payload:

{ type: 'kpi',name: 'Total Sales',message: 'Hello World',originDashboardLink: '58128745677f52dc0f000019',measure: 'Revenue',value: 39759625.51502721,condition: 'none',filters:[ { asDimension: false,title: 'Category',value: 'Include all',jaql: [Object],panel: 'scope' }, { asDimension: false,title: 'Gender',value: 'Include all',jaql: [Object],panel: 'scope' } ]

Data EventsBuild Events
{ type: 'kpi',
name: 'Total Sales',
message: 'Hello World',
originDashboardLink: '58128745677f52dc0f000019',
measure: 'Revenue',
value: 39759625.51502721,
condition: 'none',
  [ { asDimension: false,
title: 'Category',
   value: 'Include all',
  jaql: [Object],
      panel: 'scope' },
    { asDimension: false,
      title: 'Gender',
    value: 'Include all',
jaql: [Object],
 panel: 'scope' } ]

{ type: 'build',

name: 'Success Event',

measure: null,

value: 1,condition: 'none',filters: null }

TypeStringType of alert. ‘kpi’ for data events and ‘build’ for build events.
NameStringName of the alert.
MessageStringNotification message.

Dashboard ID provided by Sisense. You can find the dashboard ID from the URL of the dashboard.

For example, the ID of the dashboard below if:



For data events when a threshold condition is applied, this is the value of the threshold.

For build events, the value is 0 for failed builds and 1 for successful builds.

conditionStringType of condition that generated the alert.
filtersObjectObject that defines filters applied to the dashboard.

Was this article helpful?