Bridge // No-Code Automation

Albato automations, broadcast on screen.

Albato connects 800+ apps without code. Add an outgoing-webhook action to any automation and its data appears on your Hangar.Media screens — mapped to display columns and rendered as a live table or announcement cards.

800+ Albato App Connections
See Pricing
Secured Token-Verified Push
800+ Albato App Connections
Secured Token-Verified Push
Tables · Cards · KPIs Display Targets
Bridge // Overview

Any Albato automation becomes screen content

Albato's outgoing-webhook action posts JSON to any URL — point it at your Hangar.Media inbound webhook and the automation's data lands on screen. CRM deals, e-commerce orders, form entries: whatever the automation carries, the field mapper shapes it into a table or cards.

Works with every Albato trigger app — the webhook action is available on all plans
Map any payload field to display columns with dot-notation paths, defaults, and per-column transforms
Three display targets: live data table, announcement cards (with rolling accumulation), or KPI metrics
Accumulate mode keeps a rolling board of the most recent pushes instead of replacing on every update
Outbound events included: screens can trigger your automations back (offline/online, sync errors, emergency alerts) with a signed envelope
Bridge // Key Features

What you can do with broadcast on screen.

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

Instant Push // 01

The outgoing-webhook action does the work

Add Albato's webhook action as the final step of an automation, POST to your inbound webhook URL with a JSON body, and the payload is on screen seconds later. No intermediate services, no polling.

The last step of the automation is your screen.

Use Albato data mapping to compose the JSON body from any trigger fields

JSON payloads of any shape — single records or lists

Screens update within seconds of the push arriving

Bridge // Instant Push
Field Mapping // 02

Shape the payload into screen content

Point display columns at payload fields with dot-notation paths, set defaults for missing fields, and apply per-column transforms — uppercase, lowercase, truncate, prefix, suffix. The same mapping engine powers every automation platform integration, so a recipe built once is portable across tools.

Your automation sends data; the mapping decides how it reads on screen.

Dot-notation paths reach nested payload fields

Defaults fill gaps so screens never show blanks

Transforms tidy values without touching the automation

Bridge // Field Mapping
Verified Delivery // 03

Token-verified delivery

Albato sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time and rejects anything that does not match — fail-closed, with no anonymous path. Rotate the secret at any time from the integration page.

Every push is authenticated before a pixel changes.

Constant-time secret comparison, fail-closed

One-click secret rotation

Unknown senders receive 401 and publish nothing

Bridge // Verified Delivery
Bridge // Setup

Four steps to connected screens.

From setup to live content in minutes, not days.

Step 01

Connect the integration

Add the Albato integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.

Step 02

Add a webhook action in Albato

In your automation, add the outgoing-webhook action: method POST, your inbound webhook URL, JSON body, and a header X-Webhook-Token with your integration secret.

Step 03

Map fields to the display

Choose Data Table or Content Cards, then map payload fields to display columns with the field mapper. Defaults and transforms are optional.

Step 04

Push and publish

Run the automation. The payload renders in the bound widget on your screens within seconds — enable Accumulate for a rolling board of recent pushes.

Bridge // Questions

Common questions. Straight answers.

How is the webhook secured

Albato sends your integration secret in the X-Webhook-Token header with every push. Hangar.Media compares it in constant time and rejects non-matching requests with a 401 — nothing unverified ever reaches a screen.

What payload shape does Hangar.Media expect

Any JSON. A single object becomes one row or card; an array of objects becomes one row or card per record. With a field mapping configured, only the mapped fields are displayed; without one, the raw fields are shown as a key-value table.

Can one push update several screens

Yes. The push lands in the integration's data feed; every design widget bound to that feed updates, wherever those designs are scheduled — one push can update one screen or the whole estate.

Which Albato plan do I need

Any plan that includes the outgoing-webhook action — it is part of Albato's standard toolkit. No special tier is required 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