A node-based logic engine that lets any capability of the system be controlled, triggered and scheduled programmatically. Wire workflows together visually: events, schedules and external triggers in; routing, comms, recording and notifications out.
Our node-based logic engine lets any capability of the system be controlled, triggered and scheduled. Wire tally events, schedules and external triggers into logic, and out to routing, comms, recording and notifications.
Every workflow is the same shape: something happens, you decide what it means, the system acts.
Tally over TSL 5, schedules, GPI and external input — anything that can start a sequence.
Combine and branch on state visually. “If CAM 1 is live and we’re past 18:00…”
Set routes, change comms, start an ISO record, log to Grafana, fire a notification — any capability in the system.
The same editor covers a one-line tally rule and a show-wide sequence. These are the parts.
An action node calls any module command you hold the right to, or sends through any connection. An HTTP request node reaches systems outside.
Compare, maths, string, type convert, parameter filter, toggle, delay and variable nodes. Enough to branch, hold and shape a value without leaving the graph.
Save a graph as a template and expose only the ports and fields that matter. Drop it into other automations as a single node.
An automation runs with the rights of the user who saved it. On federated servers, place each one on this server, the leader only, or all servers.
Modules bring their own nodes: comms key trigger, recall shot, phone tally, and replay triggers such as clip created and recording started.
Outbound webhooks deliver events with retry and signing, as JSON or formatted for Slack and Teams. A built-in assistant reads system state and proposes changes for a person to apply, using your own model, and an MCP server serves external agents. Both are off by default.
Book a walkthrough with the engineers who built it, or wire up a node graph in the live demo.