Emit List
Runs on: Shared — pure logic, runs on the Community backend or inside a chatbox overlay.
The Emit List node outputs a preconfigured list every time it receives any input. The actual input data is ignored — it only serves as a trigger. Unlike the Static List data node (which is pulled lazily, only when a downstream node reads it), Emit List lives in the execution path, so use it to push a fixed list forward at a specific step — after a trigger, a then, or a Sequence branch.
Inputs
| Name | Type | Description |
|---|---|---|
Trigger | any | Any incoming value. The data is ignored; receiving input causes the node to emit its configured list. |
Outputs
| Name | Type | Description |
|---|---|---|
output | Array<string>, Array<number>, Array<boolean>, Array<hex>, or Array<Custom:YourType> | The configured list. The array type matches the chosen item type. |
Configuration
- Item Type: Whether the list holds text, numbers, booleans, colors, or objects of one of your custom types. Changing the type clears all existing items.
- Items:
- Text, Number, Boolean, and Color lists edit inline on the node — add a row with + Add Item, remove one with its × button, or open Edit as Sheet for a spreadsheet-style editor (paste a row, column, or block of cells straight from Excel or Google Sheets).
- Custom-type lists show a compact preview and an Edit N Items button that opens the same spreadsheet editor, one row per object. New items are filled in with each field's default value.
- If the node's custom type is later deleted, the node shows a "Custom type deleted" notice and its output becomes disconnected until you pick a new type.
Example
A !queue reset chat command should replace the current raid queue with three seeded slots. Connect the command trigger to an Emit List node configured with item type Text and entries "Slot 1", "Slot 2", "Slot 3", then connect that to a Set Variable node targeting the queue flow variable. Every time the command fires, the queue resets to those three slots.