People approve. Screens announce.
Relay.app builds playbooks where automation and human approvals mix. An HTTP step pushes any playbook's outcome to your Hangar.Media screens — mapped, verified, and rendered as a table or announcement cards.
Playbook outcomes, broadcast instantly
Relay.app playbooks pause for human input and approvals, then continue automatically. An HTTP step at the end POSTs the result to your Hangar.Media inbound webhook — so the moment a person clicks approve, the outcome is on screen.
What you can do with Screens announce.
Three capabilities that make this integration essential for your digital signage network.
An HTTP step finishes the playbook
Add Relay.app's HTTP request step as the final action: method POST, your inbound webhook URL, a JSON body composed from playbook data. Approval steps upstream mean the push only fires when a human has signed off.
Approved at a desk, announced on the wall.
Compose the JSON body from any playbook step's output
JSON payloads of any shape — single records or lists
Screens update within seconds of the push arriving
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
Token-verified delivery
The HTTP step sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time, fail-closed, and rejects anything else with a 401.
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
Four steps to connected screens.
From setup to live content in minutes, not days.
Connect the integration
Add the Relay.app integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP step in Relay.app
In your playbook, add the HTTP request step: method POST, your inbound webhook URL, JSON body, and a header X-Webhook-Token with your integration secret.
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.
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.
Built for every sector.
See how different industries use this integration to drive results.
Announcement approvals
Comms playbooks route announcements through approval, then push the approved card straight to office screens.
RetailPromotion go-lives
Promotion playbooks push a confirmation card to staff screens the moment a campaign is approved to start.
HospitalityEvent sign-off boards
Event playbooks push confirmed run-sheets to staff screens once managers sign off.
EducationNotice approvals
Student-notice playbooks publish to campus screens only after the approval step clears.
Common questions. Straight answers.
How is the webhook secured
The HTTP step includes your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time and rejects non-matching requests with a 401 — only the playbook's approved pushes are accepted.
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.
Why use approvals before a screen push
Screens are public. Relay.app's human-in-the-loop steps mean a person confirms wording and timing before the playbook's HTTP step fires — governance built into the automation itself.
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.