Four modes
Every journey supports four modes, each suited to a different kind of use.Build
Define steps, configure values, map acceptance criteria, and manage journey metadata. Where journeys are created and maintained.
Run
Execute the journey against an environment and review results per step — requests, responses, assertions, derived values, and errors.
Runbook
A guided, support-oriented execution mode with structured steps and manual checkpoints for operational users.
CLI
Copyable commands for running journeys locally, in CI pipelines, or via the Cloud Runner.
Two editing views
In Build mode, you can switch between two views of the same journey definition at any time.Visual editor
A canvas-based view of your steps and configuration. The default way to build and edit journeys.
YAML editor
Edit the journey as structured YAML. Changes round-trip with the Visual editor — switch freely without losing work.
Build-mode pages
These pages cover everything available while building a journey: the canvas, side panels, and supporting tools.Create a journey
Step-by-step walkthrough for creating your first journey.
Base template and overlays
Build variants and customer-specific flows without duplicating journey definitions.
Values panel
Configure run inputs, variables, derived values, and secret references for the journey.
Cases
Save and reuse named value configurations for testing and validation.
Environments
Choose which system target the journey runs against.
Coverage
Map acceptance criteria and work items to the journey; find gaps.
Run check
Validate the journey before running — errors block, warnings flag risk.
Details
Journey name, description, owner, tags, and version info.
Access
Control who can own, edit, or view the journey.
Versioning and artifacts
How journeys are versioned and compiled into build artifacts for execution.