Variables

Variables let handler chains use data from triggers and earlier steps.

Interpolation syntax

In handler text fields, wrap names in braces:

Hello \{username\}! You said \{message\}

Resolution order (highest wins for duplicates):

1. Action-scoped variables (set earlier in the same run)
2. User variables (per chatter)
3. Global variables
4. Trigger context variables

Scopes

Use Get variable to read a scope and write into an action variable.

Trigger variables

Triggers expose event fields as variables. Examples:

• Twitch chat: username, message, role, …
• Hotkey: shortcut, key, modifiers
• Queue status: queueName, pending, job

See each trigger in the API Reference.

Editor helpers

• Hover trigger titles for a variable picker (copies \{key\}).
• In handler fields with variable support, type \{ to open a dropdown of available trigger + action variables. Keep typing to filter, use the arrow keys to highlight, and press Enter or Tab to insert.
• The code and JSON editors have a Variables button that inserts a variable at the cursor.

Collections vs variables

Collections are named key-value stores (session or persistent). Variables are string values in scopes. Use collections for structured data shared across actions; use variables for interpolation in text fields.

See Collections.

Related

• Core handlers: Set variable
• Core handlers: Get variable