Short answer
Before you start
- Windows for the officially supported route
- OBS 28 or later with WebSocket v5 built in
- A Twitch account with reviewed permissions
- A backup of your actions before experimenting
- Unique names for scenes, sources, filters, actions, and triggers
Bring your setup to a 24/7 AI Streamer Coach
Ask Streamer Coach →Get personalized feedback to fix streaming issues and plan your next content.
Step by step
- 01
Install the stable release
Official Streamer.bot installation ↗Download Streamer.bot from its site, extract the ZIP outside synced storage, and open Streamer.bot.exe. Official docs advise against running it as administrator.
What you should see: The app opens from a stable local folder.
- 02
Connect the right account
Official Streamer.bot Twitch documentation ↗Under Platforms > Twitch > Accounts, connect Broadcaster and review permissions. Bot Account is optional and needed only when another account should send messages.
What you should see: Broadcaster shows connected and receives channel events.
- 03
Connect OBS through WebSocket
Nicole, connecting OBS ↗In OBS, enable Tools > WebSocket Server Settings and copy the password. In Streamer.bot, open Stream Apps > OBS and use v5, 127.0.0.1, and matching port and password.
What you should see: Streamer.bot shows the current scene, sources, and OBS status.
Port and password must match the connection created in Streamer.bot. YouTube · 4:58 ↗ - 04
Learn action, trigger, and sub-action
Nicole, action structure ↗The action is the flow. Its trigger decides when it runs. Sub-actions do the work in order. Name the result first, such as Reply with Discord.
What you should see: You can identify the event and response for one action.
The trigger starts the action and its sub-actions run in order. YouTube · 7:26 ↗ - 05
Build one small command
Nicole, Discord command ↗Add an action, then Send Message to Channel with a checked URL. Create a Command Trigger such as !discord and set permissions and cooldown before testing.
What you should see: The command replies once from the selected account.
- 06
Build a reversible effect
Nicole, points and effects ↗Add a disabled camera filter in OBS. In Streamer.bot, play a sound, enable the filter, wait, and disable it. The last step prevents a stuck effect.
What you should see: The redemption enables and disables the effect once.
The sub-action selects the connection, scene, source, filter, and state before the test. YouTube · 14:01 ↗ - 07
Set limits and test failure
Official reward documentation ↗Create the reward in Streamer.bot if it should manage all reward functions. Set cost, per-stream maximum, and cooldown. Disconnect OBS during a test and confirm recovery.
What you should see: The effect respects limits and returns to its initial state after failure.
Cost, maximums, and cooldown contain the effect frequency. YouTube · 15:06 ↗ - 08
Add evidence before large effects
Nicole, reading an action ↗Make the action write a test line or private message before changing OBS. Confirm which user and event triggered it. Then connect the visual sub-actions.
What you should see: You can prove which trigger ran the action and in what order.
- 09
Export before expanding
Official Streamer.bot setup ↗Save a copy of working actions and document scene, source, and filter dependencies. Add one automation at a time and test restarts of OBS and Streamer.bot.
What you should see: You can restore the last working version after a bad import.
If something does not work
- Streamer.bot cannot connect to OBS.
- Check v5, 127.0.0.1, port 4455, matching password, and an enabled server.
- The command replies twice.
- Find duplicate triggers and confirm only one account sends the message.
- The filter stays enabled.
- Add a final sub-action that disables it and test the error path.
- The action controls the wrong scene or source.
- Open each sub-action and select the exact OBS instance, scene, source, and filter. Avoid duplicate names. Run the action manually before testing its trigger.
Test before you go live
- Stable release
- Broadcaster connected
- OBS WebSocket connected
- Command cooldown
- Reversible effect
- Limited reward
- Failure test
Cómo configurar Streamer.bot desde cero: comandos, puntos y efectos en OBS
Watch the full tutorial ↗Common questions
Do I need a separate bot account?
No. It is optional. Broadcaster can receive events and send replies.
Must I install obs-websocket?
OBS 28 and later include WebSocket v5. Check your version before installing an old plugin.
Why create rewards in Streamer.bot?
Rewards owned by the program can use its full state and limit controls.
Can it automate a scene change?
Yes. Use Set Active Scene, limit the trigger, and keep a manual way back.
How do I stop chat from abusing an effect?
Limit user level, cooldown, per-stream maximum, and per-user maximum. Add a path that always returns the source to its initial state.
