Collection runs walk every request in a folder. Workspaces restore the tabs you need. Neither captures the path you took: load this request, tweak the draft, send, switch to Staging, send again.

HarborClient Workflows do. Record that session once, save it under the sidebar Workflows section, then replay it in the app—or run it headlessly from the terminal for smoke checks and CI.

What are workflows?

A workflow is a named, ordered recording of HarborClient activity. While you record, HarborClient captures allowlisted actions such as loading and sending requests, applying draft edits, activating environments, and (in the desktop app) opening tabs, pages, or workspaces.

When you play the workflow back, those actions run in order. You can add a delay between steps, use Gapless timing to ignore the original wall-clock gaps, and open a Results tab that lists every action in exact execution order—including script-driven jumps.

Why use workflows?

• Multi-step scenarios — Encode login → authenticated call, checkout paths, or any sequence where order and environment matter more than “run the whole folder.”
• Demos and repros — Capture exactly what you did, then play it back without retyping.
• Environment smoke checks — Activate Env A, send a health check, switch to Env B, send again—then replay or run from CI.
• Script control flow — From pre- and post-request scripts, jump with hc.execution.workflowNextAction(actionId) or skip with hc.execution.workflowSkipAction().
• Portable run logs — Inspect results in the app, auto-export JSON via Settings → General → Workflow results directory, or write exports from the CLI.

How to record and run

In the Collections sidebar, open the Workflows section and click Record workflow.

Click Record, then use HarborClient as usual—open saved requests, edit drafts, send, switch environments. Click Stop, then Save, and give the workflow a name.

Click the workflow row to open the run dialog, press Play, and when it finishes open Results.

Need to tweak the recording? Row menu → Edit opens the timeline editor: seek, reorder or delete actions, edit action JSON, adjust delay and Gapless, rename, and save. Row menu → Export writes a workflow definition file (harborclientExport: "workflow").

Run from the CLI

The same harborclient binary that opens the desktop app can play a saved workflow headlessly from your local userData:

harborclient workflow run "My Workflow"
harborclient workflow run "My Workflow" --stop-on-failure --export ./results

Headless playback executes request.load, request.draft, request.send, and environment.activate. Pure UI actions (tabs, pages, workspaces) and some persistence steps are skipped—so prefer load/draft/send/environment actions when you also want CLI and CI coverage. Create and edit in the GUI; the CLI runs what you already saved.

A quick hello world

1. Save a GET request to https://echo.harborclient.com.
2. Record a workflow: open that request, click Send, stop, and save as Echo hello.
3. Click Echo hello → Play → Results.
4. From a terminal: harborclient workflow run "Echo hello" --export ./results.

For environment smoke checks, activate two environments during the recording and send between switches—then replay the same path from the sidebar or CLI with --stop-on-failure.

Get started

Full product guide—including action types, results export, scripting APIs, and more recipes—is on the docs site: harborclient.com/workflows. Script helpers are also documented under Request scripts.

Grab the latest HarborClient from harborclient.com or GitHub Releases, record your first workflow, and hit Play. Same harbor. Replayable sessions.