Flow Event
Runs on: Backend — sends the event to your overlay immediately, outside the alert queue.
The Flow Event effect shows something on your overlay right now. It does not queue.
Alert or event?
The difference is one sentence:
An alert waits its turn. An event doesn't.
An alert is exclusive. One is on screen at a time, and the next waits for it to finish. That is what you want for a subscription, a raid or a clip — things that deserve the screen to themselves.
An event never waits and is never waited on. It can fire while an alert is already playing, and two of them can happen at once. That is what you want for a confetti burst, a screen shake, a sound sting, a counter ticking up — reactions that should land the moment they happen.
Because pausing alerts holds the queue, and an event has no turn to hold, Flow Events keep firing while alerts are paused.
How it works
The widget owns the design, and the flow fills it in — exactly as with Flow Alert.
- Add a Flow Event Widget to an overlay and give it a name.
- Declare the parameters it expects — a name and a type for each.
- In your flow, add a Flow Event effect and pick that widget from the Event dropdown.
- The node grows one input per parameter. Wire them up.
- Inside the widget, bind to
{{flowEvent.intensity}},{{flowEvent.colour}}and so on. Those tokens appear in the overlay editor's variable picker automatically.
Flow Alert names and Flow Event names are separate — a Flow Alert effect can never reach a Flow Event widget, even if they share a name, because they travel differently.
Choosing where it fires
The Event dropdown lists every Flow Event widget across your overlays, shown as Overlay › Name. The overlay and the name together are the address, so duplicating an overlay gives you a new target to point at deliberately.
Inputs
| Name | Type | Description |
|---|---|---|
Activate | any | Fires the event. |
| (one per parameter) | matches the parameter's type | The value for that field. Every parameter is optional. |
There is no Hold seconds input, unlike Flow Alert. Nothing is waiting on the event, so how long it shows is purely the widget's own Display time setting.
Firing it repeatedly
Fire the same event several times in quick succession and each one is delivered — they are not merged. A single widget has one set of children, so a repeat restarts that widget's animation rather than stacking a second copy on top of itself.
Example
A confetti cannon. A channel point reward feeds a Flow Event effect pointed at a "Confetti" widget on your gameplay overlay, with one intensity (Number) parameter driving how much lands. Viewers can set it off mid-raid-alert and the confetti appears immediately instead of waiting behind the raid.
See Also
- Flow Alert — the same idea, but it waits its turn
- Flow Event Widget