Help & reference
Bloopbot terms, explained
A quick reference for triggers, nodes, packs, source URLs and dry runs.
3 min readUpdated
| Term | Meaning |
|---|
| Flow | An automation made of connected steps. |
| Node | One step on the canvas: a trigger, condition, action or control. |
| Trigger | The event that starts a flow, such as a chat command or a raid. |
| Condition | A check that decides whether a path should continue. |
| Action | A step that does something, such as sending a message. |
| Template | A reusable starting flow that installs as your own copy. |
| Pack | A group of related flows installed together. |
| Dry run | A simulated execution. Test fire records what would happen without live actions. |
| Term | Meaning |
|---|
| Variable | A named value you declare, such as a death counter. |
| Channel scope | One shared value for the channel. |
| Viewer scope | A separate value for each viewer. |
| Channel data | Information the bot remembers from events, such as the last raid. |
| Insert… | The editor menu for choosing data to use in a field. |
| Cooldown | A time limit on how often a path can run. |
| Term | Meaning |
|---|
| Hosted widget | An overlay designed and served by Bloopbot. |
| Custom widget | Your own HTML overlay connected to Bloopbot. |
| Browser Source | The OBS source type that displays a webpage or widget. |
| Read token / widget key | A private value in a connection URL that allows access to that output. |
| Webhook | A flow’s private URL that an external button or service can call to trigger it. |
| Editor | Someone the owner has allowed to manage the channel in Bloopbot. |
Was this guide helpful?
Thanks. Your answer helps us decide which guides to improve.
