Bridge // Data Import

Five file formats in. One live table out.

Point the connector at a hosted data file — CSV, TSV, JSON, XML, or XLSX — and its rows render as a live data table on your screens, re-fetched on the sync schedule. Pricing lists, rosters, schedules: if it exports to a file, it displays.

CSV · JSON · XML · XLSX File Formats
See Pricing
Hosted URL Scheduled Fetch
CSV · JSON · XML · XLSX File Formats
Hosted URL Scheduled Fetch
Authenticated Protected Sources
Bridge // Overview

The file your team already maintains, on screen

Many teams keep operational data in exported files. Host the file at an HTTP(S) URL (your site, a share link, an export endpoint) and the connector fetches and parses it on schedule: delimiter and header options for CSV/TSV, a data path for JSON, a root path for XML, first-worksheet parsing for XLSX. The parsed grid publishes as the canonical data table for the Live Data Table widget.

CSV/TSV with configurable delimiter, encoding, and header row
JSON (dot-notation data path), XML (root path), and XLSX (first worksheet) parsing
Header, API-key, and Basic authentication for protected file locations
Column mapping, type hints, row cap, and sorting before publish
Bridge // Key Features

What you can do with One live table out.

Three capabilities that make this integration essential for your digital signage network.

Format Coverage // 01

Real parsers for real exports

CSV and TSV honour your delimiter, encoding and header settings. JSON exports drill to the records via a data path. XML feeds use a root path. XLSX workbooks parse natively — shared strings, first worksheet — with no spreadsheet software involved.

The export your system already produces is the integration.

Delimiter, encoding, and header-row controls

Dot-notation JSON data path; XPath-style XML root path

Native XLSX parsing

Real parsers for real exports
Scheduled Fetch // 02

Update the file, the screens follow

The connector re-fetches the URL on the sync schedule; when your team updates the file, screens reflect it at the next fetch. Authentication headers cover protected locations, and last-good data stays up through transient failures.

Set the URL once; ownership stays with the data.

HTTP(S) sources with auth header, API key, or Basic credentials

Last-good data on fetch failure

Row cap and sorting keep tables screen-sized

Update the file, the screens follow
Shaping // 03

Columns the screen deserves

Map and rename columns, hint types for correct alignment, sort by the column that matters, and cap rows to what is readable at a distance. The published table is the curated version, not the raw dump.

A spreadsheet for the wall, not a wall of spreadsheet.

Column mapping and renaming

Type hints for numbers and dates

Sort column and direction

Columns the screen deserves
Bridge // Setup

Four steps to connected screens.

From setup to live content in minutes, not days.

Step 01

Host the file

Put the CSV/TSV/JSON/XML/XLSX file at an HTTP(S) URL — your web server, an export endpoint, a share link.

Step 02

Connect and configure

Add the integration, set the URL, format options, and authentication if the location is protected.

Step 03

Shape the table

Map columns, set types, sorting, and the row cap.

Step 04

Bind and schedule

Bind the Live Data Table widget to the feed in the Content Designer; the file re-fetches on the sync schedule.

Bridge // Questions

Common questions. Straight answers.

What file formats are supported

CSV and TSV (configurable delimiter, encoding, header row), JSON (with a dot-notation path to the records), XML (with a root path), and XLSX (first worksheet, parsed natively). Files must be reachable over HTTP or HTTPS.

Can it fetch protected files

Yes — header, API-key, and Basic authentication are supported, with credentials stored encrypted. FTP/SFTP file servers are covered by the separate FTP/SFTP integration in Cloud Storage, which imports into the media library.

How fresh is the data on screen

The file re-fetches on the integration's sync schedule, and screens update at the next render. A failed fetch keeps the last good table on screen rather than blanking it.

How large can the file be

Parsing caps at the configured maximum rows — keep display tables modest (tens of rows) for readability; the row cap and sorting pick the slice worth showing.

Pricing // Transparent by Design
£0
/screen/month
Industry avg
£8–24
Hangar
£5

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.

No per-user fees
Unlimited users
Unlimited screens
200+ integrations
150+ templates
Multi-tenancy
Edge caching
Offline playback
REST API
Emergency alerts
Sign Up Now

Chat / Online

Pricing

£5 /screen/month

Everything included. One price.

Speed

Live in five minutes.

Sign up, connect, go.

Hardware

Use the screens you already own.

Fire TV, Android, Tizen, webOS, Pi, browser.

How can we help?

Choose an option to get started