Skip to main content
A variable preset is a named collection of variable values that you can apply to a journey to pre-fill its variables all at once. Instead of setting each variable individually every time you switch scenarios, you select a preset and all the variables it covers are filled in.

​
When to use it

Use variable presets when:
  • You have several named scenarios that require different variable values (for example, “Standard user”, “Admin user”, or “Free tier account”).
  • You want to share reusable value configurations across team members without duplicating journey definitions.
  • You are building Cases and want the case to reference a preset rather than hard-code values inline.
Variable presets are closely related to Cases. A case can reference a preset so that selecting the case automatically applies the preset’s variable values. Presets focus on the values; cases describe the broader scenario (which may include multiple presets, run inputs, and other configuration).

​
Key concepts

Named and reusable. A preset has a name and a set of variable assignments. Once defined, any journey that declares those variables can use the preset. Partial coverage is fine. A preset does not have to supply values for every variable in the journey. It fills in what it knows; remaining variables are resolved from their defaults, other sources, or run-time inputs. Applied at run time. When a preset is selected, Reqflo uses its values during execution. The preset does not modify the journey’s stored defaults — it is an overlay applied at run time. Composable with other sources. Preset values can be overridden by a run input or a --set flag on the CLI. See Value resolution order for precedence.

​
How it works

1

Define the preset

In the Values panel, create a preset and give it a descriptive name. Add variable assignments: for each variable the preset covers, specify the value it should supply.
2

Associate it with a case (optional)

If you use Cases, you can associate the preset with a case so that selecting the case automatically applies the preset. This keeps scenario-switching fast.
3

Select it at run time

Choose the preset before running (in the UI or via CLI --case when linked to a case). All covered variables are filled from the preset. Any variable the preset does not cover falls back to its default or another source.

​
Examples

A preset in YAML: 
presets:
  - name: "Admin user"
    variables:
      base_user_id: usr_admin_001
      subscription_tier: enterprise
      feature_flags: "admin,reporting"

  - name: "Free tier user"
    variables:
      base_user_id: usr_free_042
      subscription_tier: free
      feature_flags: ""
Applying a preset via CLI (linked to a case): 
reqflo run billing-flow --case "Admin user"
Overriding one variable from a preset: 
reqflo run billing-flow --case "Admin user" --set base_user_id=usr_admin_999
The preset fills in subscription_tier and feature_flags; the --set flag overrides base_user_id.