Azure orchestrates. Your screens report.
Logic Apps connect the Azure estate and 1,400+ services with visual workflows. Add an HTTP action to any Logic App and its data lands on your Hangar.Media screens — mapped, verified, and rendered as a table, cards, or KPI metrics.
From the Azure estate to the screen estate
Logic Apps trigger on Azure events, schedules, Service Bus messages and SaaS connectors; 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, announcement cards, or KPI numbers on arrival.
What you can do with Your screens report.
Three capabilities that make this integration essential for your digital signage network.
The HTTP action completes the workflow
Add the HTTP action as the workflow's final step: method POST, your inbound webhook URL, a JSON body built with dynamic content. For-each loops can push per-record, or compose an array for one batched push.
What Azure computes, the office can see.
Dynamic content from any prior action composes the body
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 delivery available
Send your integration secret in the X-Webhook-Token header (constant-time compare, fail-closed) — or compute an HMAC-SHA256 of the body with a workflow expression or inline Function and send it as X-Webhook-Signature for the strongest verification.
Every push is authenticated before a pixel changes.
Secret-header mode works with the plain HTTP action
HMAC-SHA256 mode via expressions or an inline Function
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 Azure Logic Apps integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP action in your Logic App
In the designer, 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.
Azure ops dashboards
Logic Apps watching Azure Monitor alerts push incident summaries to the platform team's screen as KPI metrics.
RetailOrder pipeline tables
Service Bus-triggered workflows accumulate order milestones into a live table on operations screens.
HealthcareInterface engine monitors
Logic Apps orchestrating system integrations push nightly run outcomes to the integration team's screen.
EducationApproval flow boards
Approval workflows push decision cards to administrative screens the moment requests clear.
Common questions. Straight answers.
How is the webhook secured
The HTTP action includes your integration secret in the X-Webhook-Token header (constant-time compare, fail-closed); expression-savvy makers can switch the integration to full HMAC-SHA256 signing via X-Webhook-Signature.
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.
How does this differ from the Power Automate integration
Same Microsoft family, different audience: Power Automate is the Microsoft 365 maker tool; Logic Apps is the Azure service for IT and developers, with ARM/Bicep deployment, VNET options, and Azure-native triggers. Both push to Hangar.Media identically.
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.