Composer clicks it together. Screens light it up.
MuleSoft Composer is the no-code flow builder for the Salesforce ecosystem. Its HTTP Connector reaches systems without a dedicated connector — including your Hangar.Media inbound webhook, which turns any Composer flow into a screen update.
Salesforce data on glass, without an integration project
Flows that react to Salesforce records, NetSuite transactions, or scheduled checks add one HTTP Connector step: method POST, your webhook URL, JSON from the flow’s data. Pipeline wins, case backlogs, and fulfilment status reach the wall the moment the flow runs.
What you can do with Screens light it up.
Three capabilities that make this integration essential for your digital signage network.
The HTTP Connector is the bridge
Add an HTTP Connector step to your flow: method POST, your inbound webhook URL, JSON body from previous steps’ data. Configure API Key auth with header name X-Webhook-Token and your integration secret.
A record changes in Salesforce; the wall knows before the meeting does.
Flow data posts as JSON — single records or lists
Record-triggered and scheduled flows 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 MuleSoft Composer integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP Connector step
In your Composer flow, add an HTTP Connector step: method POST, your inbound webhook URL, JSON body mapped from flow data, and API Key auth sending X-Webhook-Token with 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.
Pipeline celebration cards
A record-triggered flow on Closed-Won pushes a celebration card to office screens — accumulate mode keeps the recent-wins board rolling.
FinancialCase backlog tables
Scheduled flows push service-case queues by team to the operations screen every quarter hour.
RetailOrder status from NetSuite
Flows watching NetSuite fulfilment push late-order tables to the warehouse screen.
HealthcarePatient-intake KPIs
Flows aggregating Salesforce Health Cloud intakes push daily counts to the admin screen.
Common questions. Straight answers.
How is the webhook secured
The HTTP Connector’s API Key auth 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.
Do I need Anypoint Platform for this
No. The HTTP Connector ships in Composer itself for exactly this case — systems without a dedicated connector. (Anypoint users can of course POST from a Mule flow too; the webhook accepts any HTTPS sender.)
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.