Skip to main content
Fabl’s automation connects your production content to your studio hardware. Events in a show — an item going on air, a value changing, a device reporting a new state — drive actions that control your gear and your prompter, with no operator having to push the button each time.

​
The pieces

Rules

A trigger → condition → action engine. Rules decide what happens when a production or device event occurs.

Devices

The hardware and software you control — switchers, playout, audio, lighting, and media players.

Agents

On-premises services that connect to your devices and execute commands locally.

Studio mode

The live control surface whose cues drive your rules during a show.

​
How it fits together

A rule listens for a trigger — such as a rundown item going on air or a device changing state. When the trigger fires and the rule’s conditions are met, its actions run. An action can send a command to a device, update a block value on a page, or control the prompter. Actions that target physical devices are carried out by an agent — the on-prem service running in your facility — so the commands reach your gear over the local network with no cloud round-trip on air. Start with Rules to see how to build automations, then connect your hardware in Devices and Agents.