If this happens, your screens say so.
IFTTT watches 800+ services for the moments you care about. Add the Webhooks action to any applet and the trigger's ingredients land on your Hangar.Media screens — as announcement cards or a live table.
Any IFTTT trigger becomes screen content
Weather warnings, calendar events, smart-device states, social posts — if IFTTT can trigger on it, the Webhooks action can push it to your screens. Trigger ingredients ride the JSON body; the field mapper shapes them into a table or cards on arrival.
What you can do with your screens say so.
Three capabilities that make this integration essential for your digital signage network.
The Webhooks action completes the applet
Build the applet's "If This" from any service, then choose Webhooks > "Make a web request" as the "Then That": method POST, content type application/json, your inbound webhook URL, and a body composed from trigger ingredients.
Eight hundred services, one screen pipeline.
JSON body templates use {{Ingredients}} from the trigger service
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
IFTTT Pro supports additional headers on web requests — send your integration secret as X-Webhook-Token and Hangar.Media verifies it in constant time before accepting the push. Fail-closed: requests without the token publish nothing.
Every push is authenticated before a pixel changes.
Constant-time secret comparison, fail-closed
Custom headers available on IFTTT Pro plans
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 IFTTT integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add the Webhooks action in IFTTT
In your applet, choose Webhooks > Make a web request: method POST, content type application/json, your inbound webhook URL, a JSON body built from trigger ingredients, 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.
Weather-aware lobby cards
Severe-weather applets push advisory cards to lobby screens so guests see warnings the moment they are issued.
RetailSocial moment boards
Applets watching brand mentions push selected posts to an in-store screen as a rolling card board.
CorporateCalendar-driven notices
Calendar applets push meeting-start announcements to floor screens as they begin.
EducationCampus event cards
Applets triggered by campus feeds push event reminders to hall screens through the day.
Common questions. Straight answers.
How is the webhook secured
On IFTTT Pro, the web request carries your integration secret in the X-Webhook-Token header and Hangar.Media compares it in constant time — non-matching requests are rejected with a 401 and publish nothing.
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 IFTTT Pro
The Webhooks action itself is broadly available, but custom request headers — used to carry the verification token — are an IFTTT Pro capability. We recommend Pro for production signage automations.
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.