Introduction

Stream Kit automates your stream the same way tools like Streamer.bot do: you wire events to logic without writing a full app.

Actions and handlers

An action is a named automation. Inside it you build a handler chain (also called sub-actions): steps that run top to bottom.

Examples:

• Play a sound file
• Send a Twitch chat message
• Set a variable
• Run a short script
• Send an event to an overlay

See Actions for the editor workflow.

Triggers

A trigger connects an action to an event. When the event happens and conditions pass, the action runs.

Examples:

• Twitch chat message (twitch:twitch:chat:chat-message)
• Hotkey pressed (core:core:input:hotkey)
• OBS scene changed
• Cron schedule
• Bot command executed

One action can have multiple triggers. One trigger can run multiple actions.

See Triggers.

Variables

Variables carry data from triggers and handlers into later steps. Reference them in text fields with \{variableName\} syntax.

Scopes:

See Variables.

Plugins

Plugins add triggers, handlers, settings pages, and integrations. Stream Kit ships with Core, Bot, Rankings, Quotes, Twitch, YouTube, Discord, OBS, TTS, WebSocket, Stream Deck, and Overlay.

Each plugin has a settings page when configuration is required (for example Twitch OAuth or OBS WebSocket URL).

Browse Plugins and the full API Reference catalog of triggers and handlers.

Action queues

By default, matching actions run immediately and in parallel. Assign an action to a queue when runs must not overlap (TTS, media playback, shared resources).

See Action queues.

Next steps

1. Install Stream Kit
2. Set up platforms
3. Create your first action