Skip to main content
Runbook mode turns a Journey into a step-by-step guided procedure. Instead of configuring and firing off a run yourself, you’re walked through each step with context, prompted to confirm what you see, and left with a structured record of what happened. It’s designed for support agents, QA reviewers, or any operational user who needs to run a known workflow and communicate the result.

​
When to use it

Use Runbook mode when:
  • A support agent needs to reproduce a scenario tied to a customer case.
  • A team member needs to verify a workflow without needing to understand the journey’s internal configuration.
  • You need an auditable, evidence-backed record — not just a pass/fail signal.
  • You’re handing a workflow to someone who isn’t a journey author but needs to run it reliably.
Runbook mode is not a replacement for automated runs in CI or the Cloud Runner. It’s the right tool when a human needs to be in the loop.

​
Key concepts

Guided execution. Runbook mode walks the user through the journey one step at a time. Each step shows the relevant request, response, and assertions — the user doesn’t need to understand how the journey was built. Manual checkpoints. Some steps may require the user to actively confirm what they observed — marking a step as passed or failed, or checking off evidence items. These are manual checkpoints placed by the journey author. (Manual checkpoints are a planned step type.) Evidence logs. As the run proceeds, Reqflo captures a structured record: statuses, responses, assertion results, and any notes added during the run. See evidence logs. Cases. A runbook is often paired with a Case that pre-fills the right values for the scenario — for example, “Expired token” or “Missing funding source.” The support agent selects the case; the journey handles the rest. Reporting. When the run is complete, Runbook mode produces a clear summary of what passed, what failed, and what evidence was collected. See reporting results.

​
How it works

1

Open the journey in Runbook mode

Select the journey and switch to Runbook mode. If you’re investigating a specific scenario, select the matching Case to pre-fill the run’s values.
2

Select an environment

Choose the target environment (sandbox, staging, production) for this run.
3

Work through the steps

Each step is presented in sequence. Reqflo executes the request, shows the response and assertion results, and prompts you to continue. At manual checkpoints, you mark success or failure and add any observations.
4

Review and report

When all steps are complete, Runbook mode produces a structured summary. You can share this as a report or attach it to a case or ticket.

​
Examples

A support team receives a report that a payment initiation flow fails for a specific customer profile. The journey author has already built a journey for this workflow with a Case named “Missing funding source.” A support agent:
  1. Opens the journey in Runbook mode.
  2. Selects the Missing funding source case.
  3. Selects the staging environment.
  4. Works through each step, confirming responses and checking off evidence at a manual checkpoint.
  5. Receives a report showing which assertion failed, the full response body, and their notes.
The report goes into the support ticket. No raw API debugging required.

Support agent runs

How a support agent runs a journey as a runbook.

Manual checkpoints

Require confirmation or evidence at specific steps.

Evidence logs

What Reqflo captures during a runbook run.

Reporting results

Summarizing and sharing what happened.