Show us the path once. We’ll walk it all day.
No scripts, no selectors, no code. You click through your site, or tell us what to do, and Lengthsman turns it into steps anyone on your team can read.
Record the path
Two ways in. Use whichever feels natural; you can switch at any time.
Record it
Your site opens in a real browser inside Lengthsman. Click and type as a customer would. Each action appears as a plain sentence.
Describe it
Write what a customer does: “Log in with my test account, open Orders and check the newest order number starts with ORD-.” Our assistant clicks through it while you watch. Stop it, correct it, or take over with a click. The assistant only writes the steps: every scheduled run follows them exactly, with no AI guessing, so a failure means your site changed.
Add checks as you go
Switch to Check something and click anything on the page, or pick one of our suggestions for that page. Say whether its text should or should not be visible, or check the page address. Before you finish, we remind you if the last page has no check.
Passwords become secrets
Type into a password field and we offer to save it as a secret. It’s encrypted and can’t be viewed again. We cover it in screenshots and remove it from traces and logs.
- Steps
- Go to shop.example.com/login
- Type your email in Email
- Type ●●●●●● in Password Secret
- Click the Sign in button
- Check that “Welcome back” is visible
- Next step
Choose where and how often
Sensible defaults are already filled in. Accept them in one click, or tune them to how you work.
How often
Every 1, 5 or 15 minutes. Each run walks the whole path.
From where
Pick locations on a map or from a list. Three close to you are chosen for you.
Who hears about it
Email by default. Add Slack, SMS or a webhook for your own tools.
You decide when it’s worth an alert
A single slow page at 3am shouldn’t wake anyone. A broken checkout should.
- ImmediatelyThe first failed check alerts.
- After N in a rowFor example, after 2 failed checks in a row.
- After X minutesOnly if it’s still failing after, say, 10 minutes.
- Confirm firstRe-check from a second location before alerting.
Get alerted with the exact broken step
Every alert says which step broke, shows a screenshot of that moment, and explains the error in plain language: “Expected the order number to look like ORD-12345, but found 48213.” The full technical trace is there for whoever fixes it.
Your problem or ours, always clear
Your site broke a step.
The page loaded, but something a customer needs didn’t work. We alert you according to your policy.
We couldn’t run the check.
Something on our side went wrong. No alert is sent; we retry straight away from another location and show you what happened.
When your site changes, we tell you before it breaks
Each step remembers several ways to find its button or field. If the main way stops working but a backup still finds it, the check passes, and we ask you to confirm the change before the last backup breaks too.
The “Sign in” button is now called “Log in”. Update your flow?
Still passing: we found the button by its backup, test id “login-submit”.
Better than maintaining your own browser scripts
Every flow is a versioned JSON document of steps. Open the code view to read or edit it. Elements are found by role, label and text first, CSS last, with backups recorded for you, so small markup changes don’t page you.
Need more? A script step runs your own JavaScript inside the page, and our browser adds a tag to its user agent so you can allowlist it.
{
"id": "s5",
"name": "Sign in",
"action": "click",
"target": {
"by": "role", "role": "button", "name": "Sign in",
"fallbacks": [
{ "by": "testId", "id": "login-submit" },
{ "by": "css", "selector": "form#login button[type=submit]" }
]
}
}