A webhook sends each alert to a web address you choose, as JSON. Use it to open a ticket in your help desk, page someone through an on-call service, or feed your own monitoring.

Before you start:

  • You need the admin or owner role.
  • You need an address that accepts HTTPS POST requests. Most help desks and automation tools (such as Power Automate, Zapier or Make) can give you one.

Add a webhook destination

  1. In the menu, select Settings.
  2. In the Alerts panel, select Add alert destination.
  3. Choose Webhook.
  4. In Name, type something like "Help desk".
  5. Paste the address into Webhook address. It must start with https://.
  6. Under Alert me when, tick the events you want.
  7. Select Save, then Send test.

What we send

Each alert is one POST request with Content-Type: application/json and a body like this:

{
  "event": "screen.offline",
  "subject": "Screen offline: Reception",
  "message": "\"Reception\" (Ground floor) stopped checking in 12 min ago. Last known IP: 203.0.113.24.",
  "link": "https://signage.example.com/screens/12",
  "sent_at": "2026-09-27T09:41:05+00:00"
}

The event field tells you what happened:

eventMeaning
screen.offlineA screen went offline.
screen.onlineAn offline screen came back.
media.failedA file couldn't be processed.
update.failedAn app update failed on a screen.
approval.requestedSomething is waiting for approval.
testYou selected Send test.

Your address should answer with any 2xx status within 10 seconds. Any other answer is recorded as failed.

Troubleshooting

"Webhook answered 401" or "403". Your system wants a key or login. Most tools let you put a secret in the address itself, for example https://hooks.example.com/abc?key=…. Custom headers can't be added.

"Addresses on private or internal networks aren't allowed." For security, alerts can only go to public internet addresses. Use a public endpoint, or a relay service your IT team runs.

What's next