Jitterbit joins the systems. Screens join the team in.
Jitterbit Harmony operations already orchestrate your ERP, CRM, and EDI traffic. Point an HTTP target at your Hangar.Media inbound webhook and any operation’s result lands on screen — signed, if you let the standard HMAC-SHA256 plugin do its one job.
The operation result, promoted to wallboard
Wherever a Harmony operation produces numbers worth watching — sync totals, EDI exceptions, API health — an HTTP target POSTs them to your inbound webhook. A Jitterbit script with the platform’s HMAC-SHA256 Generator plugin signs the body, or skip the script and send the token header.
What you can do with Screens join the team in.
Three capabilities that make this integration essential for your digital signage network.
The HTTP target is the bridge
Add an HTTP target to your operation: method POST, your inbound webhook URL, JSON body from the transformation. Add the X-Webhook-Token request header — or sign the body in a script and send X-Webhook-Signature.
The operation that moves the data also lights the wall.
Transformation output posts as JSON — single records or batches
Scheduled and API-triggered operations 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
HMAC-signed delivery
Sign the request body with your integration secret (HMAC-SHA256) and send the digest as X-Webhook-Signature; Hangar.Media recomputes and compares in constant time, fail-closed. The simpler X-Webhook-Token header mode is available too.
The body itself is proven authentic — not just the sender.
HMAC-SHA1/256/512 accepted, SHA-256 recommended
Constant-time comparison, fail-closed
Token-header mode available as the simple alternative
Four steps to connected screens.
From setup to live content in minutes, not days.
Connect the integration
Add the Jitterbit integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP target in Harmony
Add an HTTP target to your operation: method POST, your inbound webhook URL, JSON body. Add a header X-Webhook-Token with your secret — or compute an HMAC-SHA256 with the HMAC-SHA256 Generator plugin in a script and send it as X-Webhook-Signature.
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 sync scoreboards
Operations syncing Salesforce and SAP push record counts and error totals to the integration-team screen on every run.
RetailEDI exception tables
Operations processing supplier EDI push rejected-document tables to the supply-chain screen before the morning stand-up.
HealthcareClaims pipeline status
Operations moving claims batches push throughput and rejection KPIs to the revenue-cycle wall.
PublicService-integration health
Operations bridging citizen-service systems push API health tables to the operations centre screen.
Common questions. Straight answers.
How is the webhook secured
Two modes: sign the body with HMAC-SHA256 via the standard Generator plugin and send X-Webhook-Signature (recommended), or send the integration secret in the X-Webhook-Token header. Both are compared in constant time, fail-closed.
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 Jitterbit agents does this work with
Both cloud agent groups and private agents — the push is a plain outbound HTTPS POST from wherever the operation runs, and the HMAC-SHA256 Generator plugin ships as a standard platform plugin on both.
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.