Workflows
A workflow is an ordered series of requests that run together, with variable extraction between steps and retry policies on each step.
What you can do
Section titled “What you can do”- Sequence requests — A then B then C.
- Extract values from a response and feed them into the next step.
- Condition a step on a previous step’s result.
- Retry failing steps with exponential backoff.
- Time out a step.
Extraction
Section titled “Extraction”Pull values out of a response using any of:
- JSONPath —
$.data.user.id. - Regex — match against the body or a header.
- Header lookup — by name.
Extracted values land in a chosen scope (environment, collection, or workflow) and become available to later steps as normal {{placeholders}}.
Retries
Section titled “Retries”Each step has its own retry policy: max attempts, backoff base and ceiling, jitter on/off. The status panel shows the attempt count.
The @restura/cli runs workflows in CI with structured output:
- Exit code
0= pass,1= test failure,2= error. - Reporters: live coloured progress, JSON, JUnit XML (for CI dashboards), self-contained HTML report (for sharing).
- Per-row data-driven runs from a CSV or JSON file.
Related
Section titled “Related”- Scripts — assertions and pre/post hooks at each step.
- CLI — run workflows headlessly.
- Environments — workflow output can target an environment.