Flow checks

A flow is a few steps PageHum runs in a real browser on a schedule: log in with a test account, sign up with a fresh test email, send the contact form, or check out in test mode. If it breaks, you hear about it before a customer does.

How many, how often

	Free	Starter	Pro
Flows per site	1	3	10
Each runs	once a day	every hour	every hour
Run now, per flow per day	1	10	30
Run history	7 days	90 days	13 months
Failure screenshots	the latest	7 days	30 days

Steps

Add a flow under Flows on a site’s board, from a template or blank. Every flow starts by opening a page on the site’s checked host, then up to 20 steps:

Step	Does
Open a page	Goes to a path on your site, like /login. A 4xx or 5xx fails the step.
Fill a field	Types a value into a field.
Choose an option	Picks an option in a select, by its label or value.
Tick a box	Checks a checkbox or radio button.
Click	Clicks a button or link, and waits for the page to settle.
Press a key	Presses a key, like Enter.
Wait for a URL	Waits until the address starts with a path, like /dashboard.
Expect text	Waits until text is visible.
Expect no text	Fails if text is visible, like an error message.

Say which element a step uses the way a person would see it: label=Email, placeholder=you@example.com, text=Forgot password?, role=button[name=Sign in], testid=checkout-submit, or any CSS selector. Each step waits up to 15 seconds; a whole run up to 90.

Test data

{{email}} is a new address each run, pagehum-check+<run>@example.com, or at a test domain you set on the flow. {{run}} is the run’s short id.
{{secret:name}} fills in a secret, like a test account’s password. Secrets are encrypted, can’t be read back, and are masked in every step, error, and screenshot caption PageHum keeps.
Card numbers must be a payment provider’s test cards, like 4242 4242 4242 4242. PageHum refuses anything else, and stops a run before typing a card on a page that carries a live Stripe key (pk_live_).

A signup flow

Open /signup
Fill label=Email with {{email}}
Fill label=Password with {{secret:signup_password}}
Click role=button[name=Create account]
Expect text "Check your email"

Keeping test runs out of your data

The browser identifies itself as PageHumFlow/1.0 in its user agent, and PageHum’s own snippet stays quiet during a run, so flow runs never count as visitors on your board.
On your side, filter or clean up what runs create: sign-ups from pagehum-check+ addresses (or your test domain), contact messages that say “Automated check from PageHum”, and orders in your payment provider’s test mode.
A login flow needs a test account you create for PageHum; don’t use a real customer’s.

Runs and alerts

Each run records whether each step passed and how long it took, the console errors the page logged, where it ended, and a screenshot of the failing step. Open History on a flow to see them, with a ready-made AI prompt to fix a failure.

Two failed runs in a row make Reachability a problem that names the flow and the step, and alert you like an outage: a notification with the prompt, an email on Starter and Pro, your channels, and a note when it passes again. Pause a flow while you change the page it tests.