Recipes orchestrate. Screens communicate.
Workato recipes automate the enterprise across 1,200+ connectors. Add an HTTP action to any recipe and its data lands on your Hangar.Media screens — mapped, verified, rendered as a table or cards.
Recipe outcomes, made visible
Recipes already coordinate your CRM, ERP, ITSM and HR systems; an HTTP action POSTs any step's outcome to your Hangar.Media inbound webhook. The field mapper shapes it into a live table or announcement cards — governance and audit stay in Workato.
What you can do with Screens communicate.
Three capabilities that make this integration essential for your digital signage network.
The HTTP action makes the push
Add Workato's HTTP connector action: method POST, your inbound webhook URL, JSON body composed from datapills. Batch upstream with list operations, or push per-event with Accumulate mode on.
The recipe's last step is the room's first glance.
Datapills map any prior step's output into 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
Token-verified delivery
The action sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time, fail-closed. Formula mode 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 formula steps
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 Workato integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP action in Workato
In your recipe, add the HTTP connector action: method POST, your inbound webhook URL, JSON body from datapills, 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.
Quote-to-cash boards
Quote-to-cash recipes push stage milestones to finance screens as deals move through the pipeline.
HealthcareITSM incident tables
ITSM recipes keep a live P1/P2 incident table on the service desk screen.
RetailERP exception cards
ERP-sync recipes push exception cards to operations screens when orders need attention.
EducationHR onboarding boards
Onboarding recipes push new-starter milestones to HR screens through induction week.
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. Formula-mode recipes can upgrade 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.
Which Workato edition is required
Any edition that includes the HTTP connector — standard in Workato workspaces. No special tier is required on the Hangar.Media side.
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.