Skip to main content
The --set key=value flag lets you supply or override individual run inputs directly in the command line. It’s repeatable — use it as many times as you need. --set values take precedence over Case values and other resolved sources, so they’re useful for one-off overrides without modifying a Case.

​
When to use it

  • Supplying a required run input that isn’t covered by a Case.
  • Overriding a specific value from a Case without editing the Case.
  • Passing dynamic values from CI — for example, a build ID, commit SHA, or test user generated at pipeline time.
  • Quick local experiments without saving a new Case.

​
Key concepts

Run inputs. Run inputs are values the journey expects to receive at run time. They’re declared in the journey’s Values panel. If a required run input is missing, the run will fail with a clear error. Use --set to satisfy required inputs from the CLI. --set is repeatable. Pass the flag multiple times to set multiple values: 
reqflo run my-journey --set key1=value1 --set key2=value2
Precedence. --set values override anything resolved from a Case (--case), environment (--env), or variable presets. They’re the highest-precedence source short of hard-coded values in the journey itself. Values are strings. The CLI passes values as strings. The journey’s value resolution handles type coercion where needed.

​
How it works

When --set key=value is provided:
  1. Each key=value pair is parsed and added to the run’s value context.
  2. If the same key exists in a loaded Case or Environment, the --set value wins.
  3. The journey runs with the merged, resolved values.

​
Examples

Supply a single run input: 
reqflo run my-journey --set user_id=usr_abc123
Supply multiple values: 
reqflo run my-journey --set user_id=usr_abc123 --set account_id=acct_xyz
Override one value from a Case: 
reqflo run my-journey --case "Happy path" --set amount=5000
Pass a dynamic value from CI (e.g., a commit SHA): 
reqflo run my-journey --set build_ref=$GITHUB_SHA --cloud
Combine with environment and case: 
reqflo run my-journey --env staging --case "Happy path" --set user_id=usr_test_99
For values that change on every run (like build IDs or timestamps), --set is the right tool. For stable test configurations, save a Case instead — it’s easier to reuse and share.