Skip to main content

Flow Event Widget

The Flow Event widget is a container that reveals and animates its child widgets the moment a flow fires an event at it — without waiting for anything else on screen.

It is the twin of the Flow Alert Widget. Everything about designing it is the same; the difference is when it is allowed to appear.

Alert or event?​

An alert waits its turn. An event doesn't.

Alerts are exclusive — one at a time, each waiting for the last. Good for subscriptions, raids and clips, which deserve the screen to themselves.

Events never wait and are never waited on. A Flow Event can appear while a subscription alert is already playing. Reach for it when the reaction matters more than the spotlight: confetti, a screen shake, a sound sting, a counter ticking up.

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​

  1. Add a Flow Event widget to your overlay and give it an Event name
  2. Declare the parameters the flow will send it
  3. Add child widgets inside it
  4. Bind those children using {{flowEvent.<name>}} tokens
  5. In the flow editor, add a Flow Event effect and pick this widget from its dropdown

The widget starts hidden and appears only when an event fires.

Parameters​

Identical to the Flow Alert widget: each parameter has a name and a type (Text, Number, Toggle, Image, Colour), and the name becomes the token — a parameter called intensity becomes {{flowEvent.intensity}}.

Declaring them here is what puts matching inputs on the flow node and matching tokens in the variable picker.

Naming and targeting​

A flow picks this widget by its overlay and its event name together, so duplicating an overlay produces a new target rather than silently inheriting the old one. Leave the name blank and nothing can reach it.

Event names live in their own space: a Flow Alert effect can never reach a Flow Event widget, even if they share a name.

Firing it repeatedly​

Every fire is delivered — repeats are not merged into one. A single widget has one set of children, so firing again restarts this widget's animation rather than layering a second copy over itself. If you want several to appear at once, that is a job for the child widget's own behaviour.

Settings​

  • Event name — how flows address this widget
  • Parameters — the fields flows may send it
  • Animation / Easing / In duration / Display time / Out duration — how it appears and leaves
  • Backdrop — an optional background behind the children

Display time is how long the children stay on screen. Unlike an alert's Hold, nothing else is waiting on it.

See Also​