Conditions.
Conditions are the rules in a flow. They decide whether the run keeps going and which path it follows. A condition has a true path and a false path, and the run takes exactly one of them based on the answer.
Branching
A condition looks at a value and follows its true branch when the rule passes, or its false branch when it does not. You connect whatever should happen to the matching branch. Leave a branch unconnected and that outcome simply ends the run.
The kinds of condition
A quick read on each: Check a condition compares one value against another (equals, greater or less than, at least, contains). Check multiple conditions combines several checks with AND or OR. Within a time window watches for a number of events inside a rolling window. Switch on a value routes to a different path per value instead of just true or false. Random chance takes the true path a set percentage of the time.
Counting in a window
A time window condition is how you react to a burst rather than a single event. It counts matching events inside a rolling window (and can sum quantities, so a gift bomb of seven counts as seven), fires once the moment the threshold is crossed, then stays quiet until the window clears so you do not get a flood.
Random chance
The random chance condition is a slider from 0 to 100. At 50, about half of events follow the true path; at 100 every event does, at 0 none do. Use it to keep a sound or a shout-out from firing every single time, so it stays a treat.
A condition reads best as a yes or no question. If you can phrase it as "is the message longer than 200 characters?", it maps cleanly onto a true and a false branch.
Checking a viewer
Seven conditions look specifically at the person behind the event, or the channel around it:
- Check watchtime compares tracked watch time (in hours) against a threshold. Defaults to the person who caused the trigger.
- Check followage looks at how long they have followed (in days). "At least 0 days" is a quick way to ask "do they follow at all?".
- Check account age looks at how old their Twitch account is, in days.
- Check user level checks a minimum role: subscriber, VIP, moderator or broadcaster. Only meaningful on chat-triggered flows.
- Check subscription tier checks for any paid tier, or a specific Tier 1, 2 or 3.
- Check if live is true while you are live, optionally only once you have been live past a minimum uptime.
- Check time of day is true inside a time window you set (it can wrap past midnight), read in your Bot Settings timezone, with an optional set of weekdays.
Cooldown reads like a condition but you will find it grouped with the controls (next to Wait and Repeat). It gates how often a flow may proceed, per user or channel-wide, and gives you a separate exit to run when a viewer is still cooled down.