Wire the flow. Light the screen.
Node-RED is the flow tool of the IoT world — MQTT, Modbus, serial, HTTP, all wired visually. A Function node plus an HTTP Request node push any flow's output to your Hangar.Media screens, HMAC-signed.
From the factory floor to the screen on the wall
Node-RED flows already speak to your sensors, brokers and PLCs. Wire a Function node to shape msg.payload, sign it, and POST it to your Hangar.Media inbound webhook — the data renders as a live table or alert cards on any screen, with mapping and transforms applied on arrival.
What you can do with Light the screen.
Three capabilities that make this integration essential for your digital signage network.
Function node + HTTP Request node
A Function node composes the JSON payload from flow messages (and computes the signature with Node's crypto module); the HTTP Request node POSTs it to your inbound webhook URL. Batch with join nodes or push per-message with Accumulate mode on.
The dashboard your control room actually looks at.
Join nodes batch sensor readings into one 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
HMAC-signed, replay-protected delivery
The Function node signs the body with HMAC-SHA256 using your integration secret (require("crypto")) and sets msg.headers["X-Webhook-Signature"]. Hangar.Media verifies in constant time, with optional replay protection — right for unattended industrial flows.
Every push is authenticated before a pixel changes.
HMAC-SHA256 signing in a Function node (recommended)
Optional Stripe-style replay protection
Secret-header mode for minimal flows
Four steps to connected screens.
From setup to live content in minutes, not days.
Connect the integration
Add the Node-RED integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Wire the push nodes in Node-RED
Wire a Function node into an HTTP Request node: the Function shapes msg.payload, signs it with HMAC-SHA256, and sets the signature header; the HTTP Request POSTs to your inbound webhook URL.
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.
Facility condition boards
Flows reading building sensors push temperature, air quality and occupancy to facilities screens as a live table.
RetailCold-chain alert cards
Fridge-sensor flows push threshold-breach cards to the manager's screen the moment a unit drifts.
HealthcarePlant-room dashboards
Flows monitoring plant-room equipment keep an estates dashboard live on the engineering office screen.
EducationEnergy display boards
Metering flows push consumption summaries to public screens for sustainability programmes.
Common questions. Straight answers.
How is the webhook secured
Recommended setup signs every push in the Function node — HMAC-SHA256 of the body with your integration secret, verified by Hangar.Media in constant time with optional replay protection. A secret-header mode exists for flows without code.
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 Node-RED push sensor data continuously
Yes — throttle with a delay/trigger node to a sensible cadence (the screen is read by humans), or batch with join nodes. Accumulate mode keeps a rolling window of recent readings on screen.
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.