Pipedream runs the code. Screens run the story.
Pipedream connects 2,500+ APIs with serverless code steps in Node, Python, Go or Bash. One step POSTs any workflow's output to your Hangar.Media screens — HMAC-signed, mapped, and rendered as a table or cards.
From any API to any screen, in one workflow
Pipedream workflows trigger on schedules, HTTP events or app events, transform data in real code, and finish with a push to your Hangar.Media inbound webhook. A code step computes the HMAC signature, so delivery uses the strongest verification mode end to end.
What you can do with Screens run the story.
Three capabilities that make this integration essential for your digital signage network.
A code step closes the loop
Finish the workflow with a code step (or the HTTP request action): compose the JSON from any step exports, sign it, and POST to your inbound webhook URL. The full npm/pip ecosystem is available for shaping the payload.
Twenty-five hundred APIs in, one signed push out.
Step exports make every upstream value available to the final push
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
HMAC-signed, replay-protected delivery
The code step computes an HMAC-SHA256 of the body with your integration secret and sends it as X-Webhook-Signature; Hangar.Media verifies in constant time with optional Stripe-style replay protection.
Every push is authenticated before a pixel changes.
HMAC-SHA256 body signing in a code step (recommended)
Optional Stripe-style replay protection
Secret-header mode when you prefer zero code
Four steps to connected screens.
From setup to live content in minutes, not days.
Connect the integration
Add the Pipedream integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add the push step in Pipedream
Add a final code step: build the JSON payload from step exports, compute an HMAC-SHA256 with your integration secret, and POST to your inbound webhook URL with the signature as X-Webhook-Signature.
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.
Deploy + incident boards
Workflows on GitHub and PagerDuty events keep a live engineering status board on the team screen.
RetailConversion pulse tables
Scheduled workflows query analytics APIs and push hourly conversion pulses to the trading screen.
EducationApplication event cards
Workflows on application-platform events push milestone cards to the admissions screen.
HealthcareQueue metric displays
Workflows reading booking APIs push clinic queue metrics to staff screens through the day.
Common questions. Straight answers.
How is the webhook secured
Pushes are HMAC-SHA256-signed in a Pipedream code step with your integration secret and verified by Hangar.Media in constant time, with optional replay protection — the strongest mode the platform supports.
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 Pipedream trigger types work
All of them — schedules, HTTP endpoints, email triggers, and 2,500+ app event sources. The push to Hangar.Media is just the workflow's final step, whatever started it.
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.