FishriftDocs Dashboard

Streamer.bot

Run your Streamer.bot actions from Fishrift events: a donation, a raid, a channel point reward or a bot command. Set it up under Integrations > Streamer.bot.

How it connects

Your Fishrift overlay inside OBS talks to Streamer.bot on the same computer. No ports to open, no tunnels.

  1. In Streamer.bot, open Servers/Clients > WebSocket Server, turn it on and note the port (8080 by default). Leave authentication off.
  2. On Fishrift's Streamer.bot page, turn the integration on and enter the host (127.0.0.1) and port.
  3. Keep a Fishrift overlay open in OBS. The status dot shows whether your overlay can reach Streamer.bot.

When several overlays are open, only one of them runs each action, so it fires once.

Mappings

A mapping connects Fishrift events to one Streamer.bot action.

  1. In Streamer.bot, right click the action and choose Copy Action Id.
  2. In Fishrift, make a mapping and paste the action ID (or type the action name).
  3. Add up to 10 triggers. The action runs once when any trigger matches.

Put mappings in groups. Switching a group off switches all its mappings off.

Events

Ko-fi donation, external donation, Ko-fi subscription, follow, subscribe, resub, gift sub, bits, raid, hype train begin, channel points, bot command, and any event.

Conditions

ConditionMatches
AnyAlways
Amount rangeAn amount between a minimum and maximum
Exact amountOne amount
Minimum amountAt least an amount
RewardOne channel point reward
CommandOne bot command, without the !

Arguments

Your action gets these arguments. Use them in Streamer.bot as %user%, %amount% and so on.

ArgumentContains
userThe viewer's name
amountThe amount, as text
currencyYour currency
messageThe viewer's message
event_typeThe event, like bits or kofi_donation
platformtwitch, kick, youtube, kofi or external
reward_titleThe channel point reward
commandThe bot command
sourceThe name of an external donation site

Testing

Each mapping has a Test button that sends a test follow from "FishriftTest", and Diagnose to check every step: matching, sending, whether an overlay is open and whether Streamer.bot is reachable.

Real test alerts from the editor don't fire Streamer.bot.