Enterprise workflows, on every floor.
Tray.ai orchestrates enterprise integration at scale. An HTTP Client step pushes any workflow's output to your Hangar.Media screens — mapped, verified, and rendered as a live table or announcement cards.
From the integration layer to the screen layer
Tray workflows already move data between your business systems; an HTTP Client step at any point POSTs a slice of it to your Hangar.Media inbound webhook. Governance stays in Tray — the screens simply render what the workflow sends.
What you can do with on every floor.
Three capabilities that make this integration essential for your digital signage network.
The HTTP Client step makes the push
Add the HTTP Client connector: method POST, your inbound webhook URL, JSON body composed with Tray's data mapper. Push from main flows, scheduled jobs or error handlers — anywhere visibility helps.
The integration layer finally has a face.
Tray's data mapper composes the body from any prior step
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 step sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time, fail-closed. Script steps 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 a script step
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 Tray.ai integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP Client step in Tray
In your workflow, add the HTTP Client connector: method POST, your inbound webhook URL, JSON body, 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.
Integration health boards
Error-handler branches push failure cards to the platform team's screen the moment a sync degrades.
RetailSupply chain tables
Order-orchestration workflows push fulfilment exceptions to operations screens as a live table.
HealthcareSystem sync monitors
Interface workflows push nightly sync outcomes to the integration team's screen.
HospitalityGroup booking flows
Event-orchestration workflows push confirmed group bookings to sales-office screens.
Common questions. Straight answers.
How is the webhook secured
The HTTP Client step 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. Script steps can upgrade 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.
Where does Tray fit beside the generic Webhooks integration
Use this tile when Tray is your orchestration layer — the setup help speaks Tray's language. Under the hood both ride the same verified inbound pipeline.
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.