Variables Library

Published July 25, 2026 • Updated August 2, 2026

Variables are shared answer memory. They let a Flow remember a participant answer under a stable key, then reuse it in personalized copy, completion rules, Bio actions, API steps, and later decisions. The Variables workspace shows every definition and detected dependency across your Flows so you can make changes safely.

What you can do

Variables can personalize copy, support Jump Logic, feed API or Agent steps, and select Conditional Outcomes. They can also carry operational flags such as a conversation route, urgency band, readiness indicator, acknowledgement, or complexity override.

Use operational variables to describe workflow state—not to present an automated professional recommendation. When an explicit safety, status, or complexity flag must win, configure it as a variable-based Conditional Outcome. Variable overrides are evaluated before intent and score outcomes.

• Search variables by key, type, purpose, Flow title, or usage path.
• Filter by Flow to isolate definitions and usages.
• Create a new variable definition owned by a selected Flow.
• Edit existing definitions (type, description, defaults, enum options).
• Rename a variable key across references.
• Archive or restore variables.
• Delete unused variables (single or bulk).

Where to find it

Open Dashboard > Variables from the left navigation.

How usage indexing works

The library scans Flow definitions and records where each variable appears:

• Explicit mappings (for example save-to-variable fields, outcome rule variable keys, and bio action intent keys)
• Placeholder usage inside copy (for example {{customer_segment}})
• Variable definitions stored under quiz variable metadata

Each variable entry shows:

• Definition count
• Usage count
• Flows impacted
• Usage category labels (response mapping, outcome rule, bio action, placeholder)

Archive vs delete

• Archive marks a variable as deprecated for new work while preserving existing published behavior and references.
• Restore brings an archived variable back to active pickers.
• Delete is only allowed when no usages are detected.

Use archive when you are deprecating a variable but still need historical compatibility.

Rename behavior

When you choose Rename everywhere, the system updates detected references across affected Flow drafts:

• Explicit key fields where variable keys are stored
• Placeholder tokens in copy ({{old_key}} -> {{new_key}})

Renaming is blocked if the target key already exists.

Tips

• Use stable lowercase keys with underscores (for example high_intent, lead_tier).
• Prefer archive before delete in active production quizzes.
• Review usages before changing enum options to avoid invalid downstream assumptions.