Pabbly moves the data. Screens make it visible.
Pabbly Connect automates 1,000+ apps with unlimited operations on every plan. Add an API/webhook action to any workflow and the data lands on your Hangar.Media screens — mapped, verified, rendered as a table or cards.
Any Pabbly workflow becomes screen content
Finish any Pabbly Connect workflow with the API by Pabbly action posting JSON to your Hangar.Media inbound webhook. Form entries, payment events, CRM changes — the field mapper shapes whatever arrives into a live table or announcement cards.
What you can do with Screens make it visible.
Three capabilities that make this integration essential for your digital signage network.
The API action is the final step
Add API by Pabbly as the workflow's last action: method POST, your inbound webhook URL, JSON body mapped from previous steps. Each run becomes a push; each push becomes screen content.
The workflow ends where your audience is looking.
Works on every Pabbly plan — webhook actions are unmetered
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 action sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time, fail-closed. Rotate the secret any time from the integration page.
Every push is authenticated before a pixel changes.
Constant-time secret comparison, fail-closed
One-click secret rotation
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 Pabbly Connect integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Add the API action in Pabbly Connect
In your workflow, add API by Pabbly: method POST, your inbound webhook URL, JSON body composed from step data, 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.
Lead flow boards
Form and ad-platform workflows push new leads to the sales-room screen as a rolling card board.
RetailPayment milestone cards
Payment-gateway workflows push settled-payment cards to the office screen in real time.
EducationWebinar signup tables
Registration workflows accumulate signups into a live table on the events team's screen.
HospitalityOrder notification streams
Online-order workflows push notification cards to kitchen-office screens as orders arrive.
Common questions. Straight answers.
How is the webhook secured
The API by Pabbly action 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 — nothing unverified reaches a screen.
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 webhook pushes count against Pabbly task limits
Pabbly Connect famously does not meter internal/webhook operations on its plans — but check your plan's current terms. On the Hangar.Media side there is no per-push charge.
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.