Open-source flows, on-screen results.
Activepieces is the open-source automation platform you can self-host or run in the cloud. Add an HTTP piece to any flow and its data lands on your screens — signed, mapped, and rendered as a live table or announcement cards.
From any Activepieces flow to any screen
Whatever your flow collects — form submissions, CRM events, support tickets, stock alerts — an HTTP piece at the end of it posts the result to your Hangar.Media inbound webhook. Because Activepieces supports code pieces, delivery can be HMAC-signed for the strongest verification, and self-hosters keep the whole pipeline on their own infrastructure.
What you can do with on-screen results.
Three capabilities that make this integration essential for your digital signage network.
An HTTP piece is all it takes
Append an HTTP piece to any flow, point it at your inbound webhook URL, and pass whatever fields the flow has gathered. Multi-step flows can aggregate from several sources before pushing one clean payload to the screen.
If a flow can compute it, a screen can show it.
Any flow trigger works — schedules, app events, inbound webhooks
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
A code piece computes an HMAC-SHA256 of the request body with your integration secret and sends it as the signature header. Hangar.Media verifies it in constant time before accepting the push; optional replay protection rejects stale requests. The simpler secret-header mode is available when you want zero code.
Every push is authenticated before a pixel changes.
HMAC-SHA256 body signing via a code piece (recommended)
Optional Stripe-style replay protection
Secret-header mode for code-free flows
Four steps to connected screens.
From setup to live content in minutes, not days.
Connect the integration
Add the Activepieces integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add an HTTP piece in Activepieces
In your flow, add the HTTP piece: method POST, your inbound webhook URL, JSON body. Sign the body in a code piece, or send the secret in the X-Webhook-Token header.
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.
Self-hosted ops boards
Self-hosted Activepieces flows aggregate internal metrics and push them to office screens without any data leaving company infrastructure.
RetailStock alert cards
Flows watching inventory systems push low-stock alerts as announcement cards on back-office screens.
EducationForm-fed notice boards
Student-services form submissions flow straight onto campus notice screens as rolling announcement cards.
HealthcareOn-call rota tables
Flows reading the rota system push the current on-call list to staff-room screens as a live table.
Common questions. Straight answers.
How is the webhook secured
Best practice with Activepieces is HMAC: a code piece signs the request body with your integration secret (HMAC-SHA256) and Hangar.Media verifies the signature in constant time, with optional replay protection. A simpler secret-header mode is available for code-free flows.
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 self-hosted Activepieces work
Yes — identically. The integration only receives HTTPS requests from your instance; whether it runs on Activepieces cloud or your own server makes no difference to Hangar.Media.
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.