Skip to main content
Run inputs are values that are not baked into the journey definition — they are provided each time the journey runs. This makes a journey flexible: the same workflow can target different users, accounts, or test data without needing separate journey definitions.

​
When to use it

Use run inputs when:
  • The value changes depending on who is running the journey or what they are testing (for example, an account ID or a token specific to the current session).
  • You want the journey to prompt the user for a value before running.
  • You are driving a data-driven run where each row in a CSV or JSON file supplies different values.
  • You are integrating with CI and need to pass values in from the environment without hard-coding them.
If a value is the same across every run and should never change, prefer a hard-coded value instead.

​
Key concepts

Required vs. optional. A run input can be marked required or optional. Required inputs that are not supplied block the run — the Run check panel will flag them. Default values. A run input can have a default value that is pre-filled in the UI. The user can override it before running. Declared in the journey. Run inputs are declared in the Values panel. Each input has a name, an optional description, and an optional default. Once declared, any step in the journey can reference it by name.

​
How it works

1

Declare the run input

Open the Values panel in Build mode. Add a run input by name and optionally provide a default value and description.
2

Reference it in a step

In any request step’s configuration, set a field to reference the run input by name. The step will resolve that value at run time.
3

Supply the value at run time

When you run the journey, the UI prompts you to fill in any run inputs that do not have a default (or lets you override defaults). Through the CLI you pass --set key=value. In data-driven runs, each row in the data file supplies the value for that run.

​
Examples

UI run — The journey declares a run input named account_id. When you click Run, the panel shows a field for account_id that you fill in before starting. CLI — passing a single value: 
reqflo run checkout-flow --set account_id=acc_12345
CLI — passing multiple values: 
reqflo run checkout-flow \
  --set account_id=acc_12345 \
  --set coupon_code=SUMMER10
CLI — using a case to pre-fill values, then overriding one: 
reqflo run checkout-flow --case "Happy path" --set account_id=acc_99999
Data-driven run — passing values from a CSV: 
reqflo run checkout-flow --data accounts.csv
Where accounts.csv has a column named account_id, Reqflo runs the journey once per row, injecting the row’s values as run inputs.