Sequence Flow

A Sequence Flow lets you chain HTTP and database kits into an ordered list of steps. Each step runs in turn, and any variables extracted from one step are automatically available in the next.

Create a flow

• From the tab bar: click the + icon and select New Flow.

An empty flow opens with two panels: a collection tree on the left and an ordered step list on the right.

Build a flow

1. In the left panel, browse your collections and check the kits you want to add. Checking a collection or folder selects all child kits at once.
2. Click Add → to append the selected kits as steps in the right panel.
3. Drag steps to reorder them, or click the delete icon on any row to remove it.
4. Save with Ctrl+S or the Save button — choose a collection and folder in the Save dialog.

Kits already in the flow show a visual indicator in the tree, but you can add the same kit more than once.

Database kits can only be added and run in the desktop app. On the web, adding a database step will result in an error when the flow runs.

Run a flow

Click Run ▶ in the step list header. Steps execute in order:

1. Each step shows a spinner while it runs.
2. On success, the row shows a status badge — for example 200 · 42ms · 2 vars for an HTTP step or 15 rows · 18ms · 0 vars for a database step.
3. If a step fails, it shows Error (red) and all remaining steps are marked Skipped (grey). The flow stops.
4. If a referenced kit no longer exists, the step is marked Error: Kit not found and the flow stops.

The Run button is disabled while the flow is executing.

Variable propagation

Variables extracted from a step (via JSONPath query extraction in the kit) are written to the active environment after that step completes. The next step resolves {{variableName}} syntax in its URL, headers, body, and query fields automatically — no extra wiring needed.

Inspect step results

Click any step row after a run to open the result panel at the bottom of the screen. The panel shows the response body and query results for that step. Results are read-only; you cannot re-run a single step in isolation.

Platform differences