Streamer.bot

The Streamer.bot integration connects Macro Deck to the WebSocket server of Streamer.bot. Your buttons start the actions you built in Streamer.bot, and everything Streamer.bot reports (chat messages, follows, subs, raids, channel point redemptions, timers and custom code events) can start a flow in Macro Deck.

What you can do

• Run a Streamer.bot action. Pick it from the list of your actions and pass optional arguments, which the action reads as %key%.
• Fire a custom code trigger, also with optional arguments.
• Send a chat message through Streamer.bot to Twitch, YouTube, Trovo or Kick, as the broadcaster account or as the bot account. The message can contain Macro Deck variables and event values.
• Read a Streamer.bot global variable, persisted or for the session only, into a Macro Deck variable.
• React to any Streamer.bot event with the Streamer.bot Event trigger. Pick a source, for example Twitch, and an event to narrow it, or leave both empty to react to everything. The flow receives the user, the message and the raw event data as JSON.

Some example setups:

• A Scene: Gaming button that runs a Streamer.bot action and passes the scene name as an argument.
• A Hydrate button with two Send Chat Message actions that post the same reminder on Twitch and on YouTube.
• A flow that runs on a Twitch follow event in Streamer.bot and shows a notification in Macro Deck.
• A button that reads a counter from a Streamer.bot global variable and shows it as its label.

How it behaves

Macro Deck stays connected to Streamer.bot and receives its events as they happen. The variables show whether the connection is up, the Streamer.bot version, the instance name and the broadcaster's name and platform. When Streamer.bot closes or its WebSocket server stops, Macro Deck keeps trying to reconnect, and the Connected and Disconnected triggers let a flow react. The integration has a single configuration.