Data and integrations

Digital signage integrations that keep screens on live data.

The departures list, the lunch menu and the sales figures already live somewhere. Copies typed onto slides by hand are slow to make and soon out of date. In Wallboard a datasource connects once to the system that holds the data. Every piece of content bound to it then shows the current values on each refresh.

How it works

From source system to screen.

  1. Pick a datasource type

    Choose the type that matches where the data lives, then enter its URL, credentials or file.

  2. Set how often it refreshes

    Pick an interval in seconds or a cron expression with a time zone. Cache images locally if you want faster playback.

  3. Check the preview

    The editor shows the returned data as JSON. Query filters apply before the data reaches any screen.

  4. Bind content to it

    Point a widget in a slide or playlist at the datasource. The screen changes when the data does.

Where the data can come from.

Files and sheets

Google Sheets, Microsoft workbooks and files fetched from a URL.

Databases and APIs

Any JSON or XML endpoint. SQL databases connect over JDBC, which we set up with you as a services project.

Feeds and the web

RSS feeds, website screenshots, and a web scraper that turns a page into data from a written prompt.

Calendars

Google and Microsoft calendars, read-only or writable from content.

Business systems

Toast, Power BI, SharePoint lists and news, Notion databases, Meta pages, Active Directory, Amadeus events, CAP alerts and weather.

Tables you keep in Wallboard

When Wallboard itself should hold the data, build a typed table or a free-form JSON store inside it.

Edits from people without a login

A shared link lets a store manager update prices in a browser or on a phone. Locked rows stay locked.

Every source in one editor.

Every external type opens in the same full-screen editor. On the left sit the settings for that type. The middle panel holds the advanced options for refresh, caching and error handling, and the right panel previews the data once you save. Status badges in the header show whether the datasource is active. They also show whether it will switch off by itself when nothing uses it, which happens after 7 days without an online screen playing it, or after 25 failed refreshes in a row. Teams decide who can see and edit each one.

Bring one data source to the demo.

Share a sheet, a feed or an API endpoint your screens should show. In the demo we’ll connect it and bind a slide to it. If no built-in type fits, our support team can scope a custom datasource with you.