Make builds the scenario. Your screens close it.
Make's visual scenarios connect 2,000+ apps with drag-and-drop modules. Add an HTTP module to any scenario and its data lands on your Hangar.Media screens — mapped to display columns and rendered as a live table or announcement cards.
Any Make scenario becomes screen content
Whatever the scenario assembles — CRM events, spreadsheet rows, e-commerce orders, aggregated API data — an HTTP module at the end POSTs it to your Hangar.Media inbound webhook. Make's mapping panel composes the JSON body from any earlier module's output; Hangar.Media's field mapper shapes it on arrival.
What you can do with Your screens close it.
Three capabilities that make this integration essential for your digital signage network.
One HTTP module finishes the scenario
Add HTTP > Make a request as the final module: method POST, your inbound webhook URL, body type JSON. Iterators and aggregators upstream can turn many records into one push — or one push per record.
Two thousand apps in, one screen out.
Aggregators batch many bundles into a single list payload
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 module sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time and rejects anything else — fail-closed, no anonymous path. Rotate the secret any time without touching the scenario.
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 Make integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP module in Make
In your scenario, add HTTP > Make a request: method POST, your inbound webhook URL, body type JSON composed from earlier modules, 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.
Pipeline boards
CRM scenarios aggregate the day's pipeline movement and push it to sales-floor screens as a live table.
RetailOrder celebration cards
New-order scenarios push celebration cards to the back-office screen with product and value.
HospitalityGuest feedback streams
Review-platform scenarios accumulate fresh guest feedback onto staff screens as a rolling card board.
EducationHelpdesk queue tables
Ticket-system scenarios keep a live IT-helpdesk queue on the support office screen.
Common questions. Straight answers.
How is the webhook secured
The HTTP module carries your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time and rejects non-matching requests with a 401 — fail-closed, with no anonymous path.
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.
Can one scenario push many records at once
Yes — use a Make aggregator to combine bundles into one JSON array; each record becomes a row or card. Or push per-bundle and enable Accumulate mode for a rolling board.
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.