Skip to main content
Script steps are planned and not yet available. The description below reflects the intended design.
A Script step would let you run a small piece of custom code at a point in the journey’s execution. Between API calls, you might need to transform a response value, compute something from multiple captured outputs, validate state that can’t be expressed as a simple assertion, or trigger a side effect outside of an HTTP request. Script steps would cover those cases.

​
Intended idea

Scripts would execute within the journey’s runtime context — with access to current variable values, step outputs, and run inputs — and would be able to produce new values for later steps to use. Some likely uses:
  • Transforming a response body (e.g., extracting a nested value that can’t be addressed by a simple field path)
  • Computing a hash or encoding a value before sending it in a subsequent request
  • Asserting complex conditions that span multiple captured values
  • Generating data dynamically mid-journey (e.g., building a payload from earlier results)