When to use it
Open the Values panel when you want to:- Review what inputs and variables the journey currently requires.
- Configure where each value comes from (run input, variable, step output, secret, hard-coded, etc.).
- Detect and resolve missing values before switching to Run mode.
- Paste in a set of values in bulk rather than configuring them one by one.
Key concepts
- Run inputs — values supplied at run time by the person (or system) triggering the journey. They’re not stored in the journey definition; they’re provided fresh each run.
- Variables — declared values used across multiple steps in the journey. You define the variable name and its source; steps reference it by name.
- Derived values — values computed from other sources: a previous step’s output, a variable preset, or another declared value source. You configure the derivation rule, and Reqflo resolves the value at run time.
- Hard-coded values — values baked into the journey definition that don’t change between runs. Useful for constants that are unlikely to vary.
- Secret references — you select secrets by name only. The actual secret value is never displayed or stored in the journey. Secrets are resolved by the Cloud Runner (for cloud runs) or your local environment (for CLI runs).
- Missing values — the panel highlights any required value that has no source configured. You must resolve these before the journey can run.
How it works
The Values panel lists all values the journey requires, grouped by type. Each entry shows:- The value name
- Its current source (or a warning if no source is set)
- Controls to update the source or configure it
secret as a source, you choose the secret by name from your available secrets. You do not see the secret value — it stays in the secret store and is injected at execution time.
Examples
A journey that creates a payment might need:| Value | Source |
|---|---|
customer_id | Run input |
amount | Run input |
currency | Hard-coded (usd) |
payment_method_id | Variable (set from a prior step output) |
api_key | Secret reference (payments_api_key) |
Related pages
Run inputs
How run inputs work and when to use them.
Variables
Declaring and using variables across a journey.
Derived values
Computing values from step outputs, presets, and other sources.
Secret references
How secrets are referenced by name and resolved at run time.