Skip to main content
Sub-journey steps are planned and not yet available. The description below reflects the intended design.
A Sub-journey step would let you call another journey from within the current one — embedding its full step sequence as a unit. If several of your journeys share a common setup flow (logging in, creating a test resource, establishing a billing relationship), you’d define that sequence once as its own journey and reference it from the others rather than copying the steps into each.

​
Intended idea

Sub-journeys would run inline, with the parent journey passing values in and receiving outputs back. From the parent’s perspective, the sub-journey would look like a single step — it runs, it either passes or fails, and it can expose outputs the parent uses downstream. Some likely uses:
  • Shared authentication or setup sequences reused across many journeys
  • Complex prerequisite flows (seeding a customer record, provisioning a subscription) that several workflows depend on
  • Decomposing a large journey into named, testable pieces