Skip to main content
When you add an HTTP request step to a journey, its template defines what the request looks like. But the template doesn’t know what values to use at run time — that’s your job. For every field that needs a value (a path parameter, a header, an auth token, a body field), you pick a source. That source might be something a user types in, a shared variable, a value captured from an earlier step, or a fixed value you’ve decided will never change.

​
When to use it

You configure step values any time you add or edit an HTTP request step. If the Run check panel flags missing values, this is where you resolve them.

​
Key concepts

Value sources. The source determines where the value comes from when the step runs. Different sources suit different use cases:
SourceBest for
Run inputValues that the caller supplies fresh each run (IDs, user-provided data)
VariableValues declared once and reused across multiple steps
Derived valueValues computed from a preset, another variable, or a step output
Step outputA response value captured from an earlier step in the same journey
Hard-codedValues that never change between runs
Environment valueBase URLs and service-level config tied to the active environment
Secret referenceCredentials, tokens, and keys — resolved at run time, never displayed
”Me” valueUser-specific context resolved for the person running the journey
Value resolution order. When a run starts, Reqflo resolves each field’s value in a defined order. See Value resolution order for the full precedence chain. Missing values. If a required field has no value source configured, Run check will flag it as an error. The journey cannot run until all required values are resolved. The Values panel also surfaces unresolved required inputs at the journey level.

​
How it works

Open a step in Build mode. Each configurable field shows its current source and, if one is set, a preview of what the value resolves to (where possible — secret values and unresolved run inputs won’t preview). To change a field’s source, select the field and choose a new source from the dropdown. Depending on the source type you’ll be asked to:
  • Run input — choose or create a named run input
  • Variable — choose a declared variable
  • Derived value — choose a step output, preset, or other declared source
  • Step output — choose the step and the named output to reference
  • Hard-coded — type the literal value directly
  • Environment value — choose the environment key to pull from
  • Secret reference — select a secret by name (the value is resolved by the runner, not stored here)
  • “Me” value — select the user context field to use
Changes are saved as part of the journey definition and included in the build artifact when you run.

​
Examples

Wiring a path parameter to a step output: 
values:
  path.user_id: { source: step-output, step: create-user, output: user_id }
Using a secret reference for an Authorization header: 
values:
  headers.Authorization: { source: secret-reference, name: service-api-key }
Hard-coding a content-type header: 
values:
  headers.Content-Type: { source: hard-coded, value: "application/json" }
Pulling a base URL from the environment: 
values:
  url.base: { source: environment, key: payments_service_base_url }

HTTP request steps

How request steps are added and configured.

Step outputs

Capture response values to use as sources in later steps.

Values panel

The journey-level view of all run inputs, variables, and derived values.

Value resolution order

Full precedence chain for how values are resolved at run time.