Skip to content

Build commands as flows you can read

A flow is a trigger, the checks you want and the actions that follow, connected on a canvas in your browser. Start from a ready-made one, then change any step.

On your phone? Sign up now. Pebble sets up your bot with you on your computer in about five minutes.

Nothing to install. Flows run on Bloopbot’s servers, even when your PC is off.

Flows · !queue
Three steps on the flow canvas — Chat command, Check song request limits and Chat message — each with a tray of values under it. An amber dashed wire runs from the Queue length value of Check song request limits to the Message field of Chat message, whose summary names it as Check song… › Queue length, and a blue dashed wire runs from the trigger’s Who typed it value to the same field, which carries a user badge.
Pebble, the Bloopbot mascot

Three parts

PartQuestion it answersExample
TriggerWhen should this start?Someone types !hello
CheckShould it carry on?The viewer is a moderator
ActionWhat should happen?Send a chat message

A straight line of steps can stay in the Simple form. Switch to Canvas when you want branches, extra checks or loops. Both edit the same flow.

The flow canvas with a Chat command trigger connected to a Chat message action. Under the trigger, a tray of the values it hands on — Who typed it, After the command, Word 1, Word 2 and a +1 more button; under the Chat message, its Message field with a user badge, with a dashed data wire into it from Who typed it. The node palette is on the left, Test fire and Save are in the top bar, and the Tidy up button is in the canvas toolbar.
The canvas: a Chat command trigger for !hello connected to a Chat message action, with the values the trigger hands on in the tray underneath. Click to enlarge.

Start from something that works

You don’t have to start from a blank canvas. Marketplace on the Flows page lists ready-made packs for everyday commands, alerts, moderation, music and more, and every flow on its own; each one you add is your own copy to change. Community packs from other streamers sit there too.

The Flows page with Add to Flows docked on its right, the list and its + New flow and + Add buttons beside it: Search flows and packs, the All, Packs and Flows filters, then Packs, with Starter, Pack · 12 flows marked Installed and Alerts, Pack · 8 flows with Add, and more packs below.
Add to Flows: packs first, then every flow on its own. Click to enlarge.

Grow it one step at a time

Test before it goes live

Press Test fire and the flow runs as a dry run: the Run log shows which steps ran, which check stopped it and which actions would have happened, without posting to chat or changing a real value. A flow that starts on a Twitch event, such as a raid or a poll, test-fires with a realistic example of that event.

When a flow is live, the Run log keeps showing what each real run did, so a command that didn’t answer tells you why.

Where your flows run

Flows run on Bloopbot’s servers, not on your computer. There is nothing to install, you build them in any browser, and your commands and filters keep answering chat when your PC is off. Overlays still show through OBS, as Browser Sources.

The same flows run on Kick. Sign in with Kick, or add Kick to your Twitch channel, and Kick chat, commands, follows, subs and KICKs start them; a reply goes back to the chat the command came from. Steps that only exist on Twitch, such as Shoutout or a poll, are marked so you keep them in flows that start from Twitch. Use Bloopbot on Kick lists what works where.

Try one flow on your next stream.

Sign in with Twitch or Kick, install the Starter pack and change one step.

Pebble is ready to help