Visual editor

The Visual editor is the default way to build journeys in Reqflo. It displays your journey as an ordered sequence of steps on a canvas, with panel controls on the side. No YAML required — though you can switch to the YAML editor at any time and your changes will round-trip.

​

When to use it

Use the Visual editor for day-to-day journey building and editing: adding steps, configuring values, reviewing acceptance criteria, and working through the side panels. It’s the most direct way to interact with a journey’s structure. If you prefer editing YAML directly — or need to make bulk structural changes — switch to the YAML editor.

​

Key concepts

• Canvas — the main area of the Visual editor, showing steps in order. You add, remove, and reorder steps here.
• Step card — each step is displayed as a card on the canvas. Selecting a step expands its configuration: the request template it uses, its value bindings, and any assertions.
• Side panels — the panel rail on the right gives access to Values, Coverage, Run check, Details, and Access without leaving the canvas.
• Round-trip editing — the Visual editor and YAML editor share the same underlying journey definition. Switching between them at any point is safe.

​

How it works

When you open a journey in Build mode, the Visual editor loads the canvas with your current step sequence. Adding a step: Click Add step at the bottom of the canvas (or between existing steps). Select a request template from the library. The step card appears with the template’s request shape pre-populated. Configuring a step: Select the step card to expand it. You can configure:

• Which request template the step uses
• How each input value is supplied (run input, variable, hard-coded, step output, secret reference, etc.)
• Assertions on the response

Reordering steps: Drag step cards to reorder them. Reqflo updates any step-output references that depend on position. Switching to YAML: Use the view toggle at the top of the canvas to switch to the YAML editor. Your Visual editor changes are reflected immediately.

​

Examples

A three-step journey in the Visual editor might look like:

1. Step 1 — Create session (POST /auth/session): run input username and secret reference user_password.
2. Step 2 — Fetch account (GET /accounts/{account_id}): account_id supplied as a run input; Authorization header derived from step 1’s session_token output.
3. Step 3 — Close session (DELETE /auth/session): Authorization header from step 1’s output.

Each step card shows its template name, value sources, and any assertion status.

​

Related pages