Boomi runs the backbone. Screens show the pulse.
Boomi processes already move data between your ERP, CRM, and warehouse systems. Add an HTTP Client step to any process and the same run that syncs the systems also pushes the numbers to your Hangar.Media screens.
The integration platform your data already flows through
Wherever a Boomi process touches data worth seeing — order volumes, shipment exceptions, sync results — an HTTP Client connector step POSTs it to your Hangar.Media inbound webhook. Scheduled and event-driven processes keep wallboards current without a separate reporting pipeline.
What you can do with Screens show the pulse.
Three capabilities that make this integration essential for your digital signage network.
The HTTP Client step is the bridge
Add an HTTP Client connector step to your process: method POST, your inbound webhook URL, JSON body from the process document. Define the X-Webhook-Token request header in the operation and the process delivers to the screen on every run.
The process that syncs the systems also feeds the wall.
Process documents post as JSON — single records or batches
Scheduled and event-triggered processes both work
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
Your sending step includes the integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time, fail-closed, and rejects anything else with a 401.
Every push is authenticated before a pixel changes.
Constant-time secret comparison, fail-closed
One-click secret rotation
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 Boomi integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP Client step in Boomi
In your process, add an HTTP Client connector step: method POST, your inbound webhook URL, JSON body. Define a request header X-Webhook-Token in the operation and set your integration secret.
Map fields to the display
Choose Data Table, Content Cards, or KPI Metrics, 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.
ERP KPIs on the leadership wall
Processes aggregating NetSuite and SAP data push revenue and order KPIs to executive screens on every scheduled run.
RetailSupply-chain exception boards
Integration processes reconciling warehouse feeds push delayed-shipment tables to the operations screen.
HealthcareInterface status dashboards
Processes moving HL7 and claims data push sync health to the IT operations wall — failures surface before the phone rings.
FinancialReconciliation status
End-of-day processes push match rates and exception counts to the back-office screen as each batch completes.
Common questions. Straight answers.
How is the webhook secured
The HTTP Client operation sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time and rejects non-matching requests with a 401 — fail-closed, with no anonymous path.
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.
Does this need a new Boomi licence
No. The HTTP Client connector is part of the core platform, so any existing process can add a push step — including on Boomi’s self-service Pay-As-You-Go edition.
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.