.flow files

.flow files use the same syntax as .http files but add directive comments for chaining requests, extracting response values, persisting state, and asserting behavior. Requests run sequentially, top to bottom.

A complete example

### Step 1 · Create user
# @name createUser
POST {{baseUrl}}/users
Content-Type: application/json

{ "name": "Jane", "email": "jane@example.com" }

# @extract userId   = $.id
# @extract userName = $.name
# @assert  status == 201
# @assert  body contains Jane

### Step 2 · Fetch created user
GET {{baseUrl}}/users/{{userId}}
# @assert status == 200
# @assert body contains {{userName}}

### Step 3 · Delete user
DELETE {{baseUrl}}/users/{{userId}}
# @assert status == 204

Run with ⌘Enter or the ▶ button. The Flow Runner shows an animated pipeline with pass/fail badges per step.

Extraction — @extract

Use JSONPath to pull values out of a response body. Extracted variables are available in all subsequent steps.

# @extract id      = $.id
# @extract first   = $.users[0].name
# @extract count   = $.meta.total
# @extract token   = $.auth.access_token

Assertions — @assert

# @assert status == 200
# @assert status != 404
# @assert status >= 200
# @assert status <  300
# @assert body contains "success"
# @assert body matches ^\{        ← regex
# @assert header[content-type] contains json

All assertions in a step are evaluated after the request completes. A failing assertion stops the flow at that step.

Naming steps — @name

### Login
# @name login
POST {{baseUrl}}/auth/login
Content-Type: application/json

{ "email": "dev@example.com", "password": "{{PASSWORD}}" }

# @extract token = $.access_token

Skip & retry

### Optional step (won't run)
# @skip
GET {{baseUrl}}/health

### Flaky endpoint — retry up to 3 times
GET {{baseUrl}}/health
# @retry 3

Persist extracted values — @persist

@persist writes an extracted value into <env>.env.local so other files and future runs can use it — even across app restarts.

### Login
POST {{BASE_URL}}/auth/login
Content-Type: application/json

{ "email": "dev@example.com", "password": "..." }

# @extract token = $.access_token
# @assert  status == 200

# Save the token for future runs
# @persist token

# Or write with a different key name
# @persist API_TOKEN = {{token}}

Rules:

• Persists run after all @asserts — a failing assertion prevents any persist in that step.
• Persists are silently skipped when the active env is named prod or production.
• SendPad auto-adds *.env.local to your workspace .gitignore.

See Environment Variables for full .env.local details.

Literate testing

Non-directive # comments become prose in the test report. When you run a flow, the Results Panel renders prose alongside results — a document that reads like documentation but is also a live test.

# User CRUD Lifecycle
#
# This flow validates the complete lifecycle of a user resource.
# It creates a user, fetches them by ID, and deletes them at the end.

@baseUrl = https://api.example.com

### Step 1 · Create user
# We create a new user and capture the returned ID for later steps.
# @name createUser
POST {{baseUrl}}/users
Content-Type: application/json

{ "name": "Test User" }

# @extract userId = $.id
# @assert status == 201

Click Export as Markdown to save the report for sharing.

Running a flow

Action	How
Run entire flow	⌘Enter or ▶ button at top of file
View step results	Click any step in the pipeline visualization
Export report	Export as Markdown in the Results toolbar