Power Automate flows, visible to everyone.
Power Automate reaches everything in Microsoft 365 and 1,000+ connectors beyond. Add an HTTP action to any cloud flow and its data lands on your Hangar.Media screens — mapped, verified, and rendered as a table or cards.
From the Microsoft estate to the screen estate
Cloud flows trigger on SharePoint changes, Forms submissions, Dynamics events, approvals and schedules; an HTTP action POSTs the outcome to your Hangar.Media inbound webhook. Dynamic content composes the JSON body; the field mapper shapes it into a live table or announcement cards.
What you can do with visible to everyone.
Three capabilities that make this integration essential for your digital signage network.
The HTTP action completes the flow
Add the HTTP action as the flow's final step: method POST, your inbound webhook URL, a JSON body built with dynamic content. Apply-to-each loops can push per-record, or compose an array for one batched push.
What the flow approves, the screen announces.
The HTTP action is a premium connector on the Microsoft side
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 action sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time, fail-closed. Flows with expression skills can alternatively compute a full HMAC signature.
Every push is authenticated before a pixel changes.
Constant-time secret comparison, fail-closed
HMAC mode available via flow expressions
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 Power Automate integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP action in Power Automate
In your cloud flow, add the HTTP action: method POST, your inbound webhook URL, a JSON body from dynamic content, 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.
Approval status boards
Approval flows push decision cards to department screens the moment requests clear.
EducationForms-fed notice screens
Microsoft Forms submissions flow onto staff-room screens as rolling announcement cards.
HealthcareSharePoint list tables
Flows on SharePoint list changes keep operational checklists live on ward office screens.
RetailTeams-to-floor announcements
Selected Teams channel posts flow to back-of-house screens so floor staff see HQ updates without checking Teams.
Common questions. Straight answers.
How is the webhook secured
The HTTP action 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. Expression-savvy makers can switch the integration to full HMAC signing.
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.
Is the HTTP action available on my Power Automate plan
The HTTP action is a premium connector in Power Automate — most business plans include it, but check your licence. On the Hangar.Media side no special tier is required.
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.