Understanding integration types

Connect supports a full catalog of integration types, each designed for a different production tool. They span cloud graphics, broadcast software, native graphics, streaming platforms, and generic HTTP, and reach their targets through one of three connection routes.

Connection routing

Every integration talks to its target through one of three routes:

• Direct: your browser calls the external API directly. Used for cloud services and local software reachable on the same network.
• Edge Function: your browser calls the API through a Supabase Edge Function that acts as a CORS proxy. Used when an API blocks direct browser calls (for example, the Generic HTTP integration).
• Middleware: commands route from your browser through Supabase Realtime to Helmo Middleware (a local desktop app) and on to local software. Used for software that can only be reached on the local network.

Cloud graphics

Viz Flowics

Connects to Viz Flowics via their REST API (Direct). Requires a Graphics Token from your Viz Flowics account. Supports overlay control, field editing, lists, timers, and Google Sheets sync.

Singular.live

Connects to Singular.live compositions via their REST API (Direct). Requires an App Token. Supports IN and OUT commands, with PATCH support in progress.

Broadcast software

OBS Studio

Connects to OBS via WebSocket 5.x. Runs Local (browser to OBS on the same network) or through Helmo Middleware. Supports scene switching, source show/hide/toggle, audio, filters, streaming, and recording control.

vMix

Connects to vMix via its HTTP API. Runs Local or through Helmo Middleware. Supports overlay control, transitions, text updates, streaming, and recording.

CasparCG

Connects to CasparCG playout via the AMCP protocol over TCP (port 5250). Requires Helmo Middleware, because the AMCP/TCP protocol cannot be reached directly from the browser.

Meld Studio

A local broadcast production app controlled via the Qt WebChannel protocol over WebSocket (port 13376). Runs Local or through Helmo Middleware. Supports scene, layer, audio, and streaming control.

Native graphics

Helmo Graphics

Helmo's built-in graphics engine. Connects natively over Supabase Realtime, with no external credentials or middleware required.

Streaming platforms

YouTube Live, Twitch, Kick, and Restream connect over their REST APIs using OAuth (Direct, cloud). You authorize your account through the platform's login flow and control streams, chat, and engagement from Helmo Control and Action Sequences.

Generic HTTP

A generic REST integration that sends HTTP requests to any endpoint with variable substitution. Routes through a Supabase Edge Function that proxies the call to avoid CORS issues. Great for custom APIs, webhooks, or third-party services.

Credential security

All credentials (API keys, tokens, and OAuth tokens) are encrypted at rest with pgp_sym_encrypt and masked in execution logs.