Alerts & Notifications

Set the time in minutes. If you set it to 5 minutes, you’ll receive a notification when the player has been offline for more than 5 minutes.

Insert one or more e-mail addresses. The e-mail addresses here will receive the notification for both offline and reconnect status.

Activate or deactivate notifications.

Toggle this on if you’d like to receive alerts within a specific time range.

Add webhooks to your alerts.

Send alert events (e.g., screen offline/online) to your own systems via HTTP POST. Define a JSON payload and include dynamic placeholders—like {{screen_name}}—which are replaced with real values at runtime. The body must be valid JSON. All webhook settings are encrypted when stored.

Why use it

• Push alerts to Slack, Teams, or your incident tools (e.g., PagerDuty)
• Trigger automations in Zapier/Make or your internal endpoints
• Centralize fleet status in your monitoring stack

How it works

1. Enter your endpoint URL.
2. Compose the JSON body with placeholders (see the list in the app, e.g., {{screen_name}}, {{status}}, {{timestamp}}).
3. Save and enable.

Example payload

{ "event": "{{status}}", "screen": "{{screen_name}}", "screen_id": "{{screen_id}}", "team": "{{team_name}}", "occurred_at": "{{timestamp}}" }

Notes: Webhooks use HTTP POST only. Keep payloads lean and valid JSON. Placeholders render server-side before delivery; configuration data is stored encrypted.

Set up a Webhook for Slack

Watch the tutorial

1. To integrate a webhook with Slack, you’ll first need to create a Slack app.

• Start by heading to https://api.slack.com/apps and signing in to your Slack account.
• From there, click Create New App, choose From scratch, give your app a name, and select the workspace where it will be installed. Once the app is created, you’ll be taken to the app settings page.

2. Configuring the Slack webhook

• In the app settings, open Incoming Webhooks from the left-hand menu and enable it using the toggle in the top-right corner.
• Once enabled, Slack will reveal additional options. Click Add New Webhook and select the channel where you’d like webhook messages to be delivered.
• After selecting the channel, Slack will generate a webhook URL — keep this handy, as you’ll need it in Play Digital Signage.

3. Configuring the webhook in Play Digital Signage

• In your Play Digital Signage account, go to Alerts, enable alerts for the selected screen, and click the Webhook button for the screen where you want the webhook to be triggered.
• Paste the Slack webhook URL into the dialog. You’ll see an example payload — make sure to change the “message” field to “text”, as this is how Slack recognizes incoming webhook messages.
• Click Test to confirm everything is working. If the setup is correct, a message will appear in the selected Slack channel. Once the test passes, click Save.

That’s it — your webhook is now live and ready to keep you on track with your screen statuses.

If you’d like to dive deeper into Slack webhooks, Slack’s documentation is a great place to start: https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/

Set up a Webhook for PagerDuty

Watch the tutorial

1. Create a service in PagerDuty

• To integrate a webhook with PagerDuty, you’ll first need to create a service that will receive events.
• Start by signing in to your PagerDuty account and navigating to Services.
• Click New Service, give it a name (for example, Play Digital Signage Alerts), and assign an Escalation Policy.
• Select Events API v1 in the next step from the searchable dropdown menu and click Create Service.

2. Configure the PagerDuty Events API integration

• Once the service is created, you’ll be taken to its configuration page.
• PagerDuty will generate an Integration Key and an Integration URL.
• Keep this key handy — you’ll need it when configuring Play Digital Signage.

3. Configure the webhook in Play Digital Signage

In your Play Digital Signage account:

• Go to Alerts
• Enable alerts for the selected screen
• Click the Webhook button for the screen where you want PagerDuty incidents to be triggered
• Paste the PagerDuty Integration URL into the Webhook URL field

Set these keys in your webhook body:

Key                Value
service_key        your PagerDuty integration key
description        e.g. Play Digital Signage screen {{screen_status}} (Will be sent as connected/disconnected)
event_type         use trigger in this case
details            map alert details (e.g. screen name, status, timestamp) into the payload field

Use the Test button to verify the setup. If everything is configured correctly, a new incident will appear in PagerDuty.

Once the test passes, click Save.

4. What happens next

When a screen alert is triggered:

• PagerDuty creates an incident
• The incident follows your escalation policy
• On-call responders are notified via their configured channels (mobile, SMS, email, etc.)

This ensures critical screen issues are surfaced immediately and acted on without delay.

If you’d like to learn more, PagerDuty’s Events API documentation is a great place to start: https://developer.pagerduty.com/docs/events-api-v1-overview

In your profile, you have the option of setting default values for alerts on newly added screens.

Learn more about default values

Yes, you can add any e-mail address. We don’t verify the e-mail addresses used here, so if you need an extra address, you can simply create one, for example at Gmail.

Yes, you can. Set it in your profile under Default Values.

Yes. Click Select at the top of the page, then click Disable Alerts at the bottom of the page.

Go to Alerts and, under each alert, toggle on Only Send Alerts and set a from and to time of day. You can also turn this on and edit it in bulk.