Skip to main content
The Values panel is the central place to see and configure everything a journey depends on: the run inputs it expects, the variables it declares, and how each step gets the data it needs. Before a run starts, every required value must be resolved — from a run input, a variable, a step output, a hard-coded value, an environment, a secret reference, or a user-specific “me” value.

​
Value sources

Reqflo supports several distinct ways to supply a value to a step. Each source has a different lifecycle and ownership model.

Run inputs

Values you supply at run time — through the UI, the CLI --set flag, or a data file.

Variables

Named values declared once and reused across multiple steps in the journey.

Derived values

Values computed from a previous step output, a variable preset, or another declared source.

Step outputs

Data extracted from a step’s response and passed forward to a later step.

Hard-coded values

Literal values baked into the journey that do not change between runs.

Variable presets

Reusable preset configurations that pre-fill variables for a given scenario.

Paste values

Bulk-paste a block of values instead of configuring each field individually.

Missing values

How Reqflo flags required values that are not yet resolved before a run starts.

Me values

User-specific values that resolve to the identity of the person running the journey.

​
Environment values and secret references

Two additional sources are managed outside the Values panel but contribute to value resolution: Environment values come from the selected environment and supply system-level config — base URLs, service endpoints, and environment-specific settings. See Environments. Secret references let you select a secret by name. The actual secret value is never displayed and is resolved at run time by the Cloud Runner (for cloud runs) or the local environment (for CLI runs). See Secrets.

​
How resolution works

When a journey runs, Reqflo resolves each required value against the configured sources in order. If a required value cannot be resolved, the run is blocked and the Run check panel explains what is missing. See Value resolution order for the full precedence rules.

Values panel

Opening and using the Values panel in Build mode.

Run check

What Reqflo validates before allowing a run to start.

Concepts: values and variables

Mental model for how values and variables fit into journeys.

Value resolution order

Precedence rules when multiple sources supply the same value.