Bridge // Custom Alerts

Any alert system connected to your screens.

Integrate alerts from campus safety platforms, mass notification systems, building management software, and any custom provider. If it can send a webhook or API call, it can trigger your signage.

API/Webhook Trigger Methods
See Pricing
<5s Alert Latency
API/Webhook Trigger Methods
<5s Alert Latency
Unlimited Alert Sources
Bridge // Overview

Connect any alert source to your signage

Not every alert comes from a federal system or standardized feed. The Third-Party Alerts integration provides a flexible framework for connecting any notification source to your digital signage network. Whether it is a campus safety platform like Rave Mobile Safety, a building management system, or a custom internal tool, Hangar.Media can receive triggers via webhooks, REST API calls, or email parsing.

Receive alert triggers via inbound webhooks, REST API, email, or MQTT messaging
Map incoming alert data to screen templates with custom field mapping
Support for multiple simultaneous alert sources with independent priority levels
Alert routing rules to target specific screen groups based on the source system
Bridge // Key Features

What you can do with connected to your screens.

Three capabilities that make this integration essential for your digital signage network.

Webhook Receiver // 01

Trigger alerts from any system

Hangar.Media provides a unique webhook endpoint for each alert source you set up. When your campus safety system, BMS, or custom application sends a POST request to that endpoint, the alert data is parsed and displayed on targeted screens within seconds.

Our campus safety platform sends a webhook and every building screen shows the alert instantly.

Unique webhook URL per alert source for security

JSON and form-encoded payload support

HMAC signature verification for authenticated triggers

Bridge // Webhook Receiver
Field Mapping // 02

Translate any data format to screen alerts

Every alert system sends data in a different format. The field mapping engine lets you define how incoming fields map to alert title, message body, severity level, affected zones, and display duration. No code changes needed on the source system.

We mapped our BMS alarm fields to screen alerts in about ten minutes without touching the BMS config.

Visual field mapping editor with live preview

Default values for optional fields

Conditional mapping rules based on field content

Bridge // Field Mapping
Multi-Source Priority // 03

Manage competing alert sources

When multiple alert systems are connected, conflicting alerts can arrive simultaneously. The priority engine assigns each source a priority tier so higher-priority systems always take precedence. Lower-priority alerts queue until the screen is available.

Fire alarms always override maintenance notifications, automatically, with no manual intervention.

Priority tiers for each connected alert source

Automatic conflict resolution when alerts overlap

Queue management for lower-priority alerts

Bridge // Multi-Source Priority
Bridge // Setup

Four steps to connected screens.

From setup to live content in minutes, not days.

Step 01

Register an alert source

Create a new alert source in the Hangar.Media dashboard. You receive a unique webhook URL and API credentials for that source.

Step 02

Set up field mapping

Define how the incoming data payload maps to alert fields. Use the visual editor to map title, message, severity, and zone targeting.

Step 03

Set priority and targeting

Assign a priority tier to the source and define which screen groups should receive alerts from this system.

Step 04

Send a test alert

Trigger a test alert from your source system to verify the data mapping, screen targeting, and visual presentation are correct.

Bridge // Questions

Common questions. Straight answers.

What alert systems can I connect

Any system that can send an HTTP webhook, REST API call, email, or MQTT message can be connected. Common sources include Rave Mobile Safety, Alertus, Omnilert, Singlewire InformaCast, building management systems, and custom internal tools.

Can I connect more than one alert system

Yes. There is no limit on the number of alert sources. Each source gets its own webhook endpoint, field mapping, priority tier, and screen targeting rules. All sources operate independently.

What if two alerts arrive at the same time

The priority engine resolves conflicts by displaying the higher-priority alert first. If both are the same priority, the most recent alert takes precedence. Lower-priority alerts queue and display once the higher-priority alert is cleared.

Do I need to modify my existing alert system

In most cases, no. If your system supports outbound webhooks or HTTP notifications, you simply point it at the Hangar.Media endpoint. The field mapping handles data format translation on the Hangar.Media side.

Pricing // Transparent by Design
£0
/screen/month
Industry avg
£8–24
Hangar
£5

One price. The whole platform.

That's how we think signage should work. Content editor, screen management, and 200+ app integrations — all included from day one.

No per-user fees
Unlimited users
Unlimited screens
200+ integrations
150+ templates
Multi-tenancy
Edge caching
Offline playback
REST API
Emergency alerts
Sign Up Now

Chat / Online

Pricing

£5 /screen/month

Everything included. One price.

Speed

Live in five minutes.

Sign up, connect, go.

Hardware

Use the screens you already own.

Fire TV, Android, Tizen, webOS, Pi, browser.

How can we help?

Choose an option to get started