Your agents watch the world. Your screens show it.
Huginn runs agents on your own server — watching sites, feeds, prices, and events around the clock. A Post Agent forwards whatever they find to your Hangar.Media screens as a live table or announcement cards.
From agent event to screen, on your infrastructure
Huginn's agent graph collects and transforms events; a Post Agent at the end of the chain POSTs them to your Hangar.Media inbound webhook. Everything upstream runs on your own server — the screens simply render what your agents emit, with mapping and transforms applied on arrival.
What you can do with Your screens show it.
Three capabilities that make this integration essential for your digital signage network.
The Post Agent is the bridge
Wire a Post Agent to receive events from any other agents — website watchers, RSS readers, price monitors, schedule emitters — and point it at your inbound webhook URL. Each event becomes a push; each push becomes screen content.
Anything an agent can emit, a screen can display.
Merge events from multiple agents through a single Post Agent
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
Token-verified delivery
The Post Agent sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time and rejects anything else. Fail-closed by design — a misconfigured agent cannot publish to your screens.
Every push is authenticated before a pixel changes.
Constant-time secret comparison, fail-closed
Secret rotation without touching the agent graph
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 Huginn integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add a Post Agent in Huginn
Create a Post Agent receiving events from your source agents: method POST, your inbound webhook URL, payload_all true (or a custom payload), and a header X-Webhook-Token with your integration secret.
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.
Competitive watch boards
Website-watcher agents track competitor pages and push changes to a strategy-room screen as a rolling card board.
RetailPrice monitor tables
Price-watch agents track supplier pages and accumulate changes into a live table on the buying team's screen.
EducationResearch feed displays
RSS and site-watch agents follow journals and funding pages, pushing new items to a faculty common-room screen.
HealthcareStatus page monitors
Agents watching supplier status pages push incident cards to the IT office screen the moment something degrades.
Common questions. Straight answers.
How is the webhook secured
The Post Agent includes your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time and rejects non-matching requests with a 401. Combined with Huginn's self-hosted nature, the entire pipeline stays under your control.
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 Hangar.Media need access to my Huginn server
No. The integration is receive-only — your Huginn instance pushes outbound HTTPS requests to Hangar.Media and nothing connects back to your server.
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.