Integrations
Tevyr plugs into the rest of your show stack without proprietary glue. Fire your existing cue console, broadcast every timer event to your automation tools, drive Slack and Discord from your rundown, or run a saved HTTP request mid-show — all from one room. Four primitives, no plugins required.
New in this release: the Integrations Library + Macros now drive Slack, Discord, Notion, OpenAI, Anthropic, Resend, WLED, Philips Hue, and vMix HTTP from a visual flow builder — no code, no Zapier middleman. Pair them with the Webhooks you already have for the complete picture. See the Macros marketing page for an animated walkthrough of how integrations + macros choreograph a single cue.
Four ways anything talks to Tevyr
Pick whichever your tool already speaks. Most operators end up using two or three together.
HTTP API (inbound)
Any tool that can fire a URL — QLab Network Cues, a Stream Deck button, a curl one-liner — can drive Tevyr. 60+ GET-style endpoints control timers, sessions, messages, and effects.
Webhooks (outbound)
Tevyr fires a webhook on every meaningful event — timer warnings, session starts, blackouts, Q&A submits. Point them at OBS, vMix, QLab, Zapier, or anything that listens for HTTP.
Integrations + Macros (NEW)
Saved encrypted connections to Slack, Discord, Notion, OpenAI, Resend and more, driven by a visual macro builder. Branch on timer state, schedule sends, retry on failure — all in the room you already work in.
WebSocket (real-time sync)
The same WebSocket that powers multi-screen sync. Connect from a custom dashboard or hardware controller for sub-second bidirectional updates.
Which one should I use?
Three honest comparisons — pick the path that matches what your tool can do, not what sounds fanciest.
- You want Tevyr to drive your tool → Macros + Integrations (if a connection template exists) OR Webhooks (for everything else, including tools on your local network).
- You want your tool to drive Tevyr → HTTP API. Map your console's network cue to a Tevyr URL.
- You want bi-directional, low-latency sync → WebSocket. Anything sub-second + custom UI lives here.
Integrations Library
Saved HTTP connections you set up once in Settings → Integrations, then call from any macro via the flow.http_request step. Credentials are encrypted at rest; OAuth tokens auto-refresh.
Plan limits (saved connections per account): Starter 0 · Basic 5 · Premium 50 · Enterprise unlimited.
Variable interpolation: every URL, header, and body field on an integration step supports {{ctx.*}} placeholders that resolve at fire time — session title, timer remaining, event name, etc. See the Macros context-variable reference for the full list.
Slack
OAuth into your workspace, post to #channels from any macro. The bot can chat in public channels without being invited (chat:write.public scope).
Discord
Paste a webhook URL — post messages, embeds, and @mentions to a Discord channel from a macro step. No bot setup, no OAuth.
Notion
Paste a Notion integration token. Append paragraphs, update page properties (status flips, completion timestamps), or query a database mid-show.
OpenAI
Paste an API key. Send a prompt mid-macro and capture the response in a downstream step — e.g. generate a live tease for the next session.
Anthropic
Paste an Anthropic key (x-api-key). Same shape as OpenAI — drive Claude from inside your rundown for on-air copy generation.
Resend
Paste a Resend API key. Send transactional email from a macro — speaker notifications, post-event recaps, scheduled cues.
WLED
Paste your WLED device URL (must be tunnel-exposed for cloud reach). Set color, brightness, effect, or trigger a saved preset on a cue.
Philips Hue
Hue Remote API bearer token. Set scenes and light state across your bridge from anywhere — no LAN exposure required.
vMix HTTP API
Paste your vMix HTTP URL (with inline basic auth if used). Cut to input, QuickPlay, start/stop recording, start streaming from a cue.
Zapier
Paste a Zapier catch-hook URL. Fire a Zap from any macro step and feed 7,000+ downstream apps — Calendly, HubSpot, Sheets, anything. Branch in Zapier on event name.
Make
Paste a Make webhook URL. Fire a scenario from any macro step — visual scenario builder, 2,000+ integrations, multi-branch routing. Branch in Make on event name.
n8n
Paste an n8n webhook URL (cloud or self-hosted). Fire a workflow from any macro step. Fair-code license, 500+ nodes, self-host so payload data never leaves your infra.
Generic HTTP
Fallback for anything not pre-templated. Set method, headers, body manually — covers Make.com, n8n, IFTTT, custom internal APIs, and any REST endpoint.
Don't see your tool in the library yet? Use the Generic HTTP template — it covers IFTTT, custom internal APIs, and anything else that listens for an HTTP webhook. Paste the URL, set method + headers + body, fire it from a macro step. We add new dedicated templates as demand grows.
The Macros recipes show 3 end-to-end orchestrations using 7–9 integrations each — a 1,500-attendee SaaS conference changeover, an esports BO5 grand final, and a multi-service church Sunday. Same templates, real-world choreography with per-screen targeting, ad-hoc timers, lifecycle thresholds, and sub-macros.
Webhooks (the path you already had)
Webhooks still ship with Tevyr and still work the same way — fire-and-forget event broadcasts when timers warn, sessions start, blackouts trigger, or Q&A submits land. Use webhooks when:
- The receiving tool is on your local network (OBS WebSocket, DMX consoles, audio mixers) and you've routed its public URL through a tunnel or a reverse proxy.
- Your tool listens, not asks. Webhooks are one-way push; macros are explicit step-by-step actions.
- You want everyone subscribed. A single webhook can fan out to OBS + vMix + Zapier + your logging endpoint simultaneously.
Macros and webhooks complement each other — most production stacks use both. Webhooks broadcast "the keynote just started" to your streaming rig; a macro fires a Slack message + Notion log + lighting cue in a single guarded sequence.
Per-tool setup guides
Step-by-step recipes for the tools event teams use most. Each guide has copy-paste examples for the common cues.
QLab (Theater)
Drive Tevyr from a QLab cue list using Network Cues. One GO button advances lights, sound, and Tevyr — no second operator needed.
Bitfocus Companion
Map Tevyr actions to Stream Deck buttons. Also the bridge for OBS / DMX / MIDI / OSC tools — Companion translates them into HTTP calls Tevyr understands.
OBS Studio
Embed Tevyr screens as browser sources, switch OBS scenes from Tevyr webhooks, control recording from a cue. (For real-time OBS control, bridge via Companion.)
vMix
Add Tevyr as a browser-source overlay or full input. For driving vMix back from Tevyr, use the vMix HTTP integration template or webhook subscriptions.
Zapier
Wire Tevyr into 7,000+ apps without writing code. Use webhooks for Tevyr → Zapier; use the Generic HTTP integration template for Zapier catch-hooks fired from a macro.
Zoom & Teams
Show a Tevyr timer as a webcam tile in Zoom, Teams, Meet, Webex — visible even when others share their screen.
Don't see your tool?
If your tool can fire a URL, receive a webhook, accept an HTTP request, or open a WebSocket, it can talk to Tevyr. Three honest starting points:
- They have an API and you want Tevyr to call them → create a Generic HTTP connection (Settings → Integrations) and reference it in a macro step. Works for anything REST.
- They listen for webhooks → subscribe a Tevyr webhook to the event you care about. Done in 30 seconds.
- They speak a non-HTTP protocol (OSC, MIDI Show Control, NDI, LTC, OBS-WebSocket, DMX/Art-Net) → bridge through Bitfocus Companion. Companion translates dozens of protocols into HTTP calls Tevyr understands.
For direct programmatic control, the API documentation lists every endpoint — every action you can take in the controller has a matching URL.