Workflow monitoring for the journeys that decide whether you get paid
A workflow monitor drives a real browser through a short journey on your site and asserts what should be true at the end. It can navigate, fill fields, click, wait for an element, and then check the result. Every check records what happened, and a failure sends you a screenshot with a plain-English summary.
14 days, no card required.
What counts as a workflow?
Anything that takes more than loading a page. Adding an item to a cart and confirming the cart appears. Submitting a contact form and confirming the thank you message comes back. Opening a sign-in page and confirming the form is really rendered. Clicking into a pricing or booking page and confirming you land where you should.
You build one by choosing a template, pointing it at a page, and picking what should be true when it finishes. There is no script to write and nothing to install on your site.
What can a check do in the browser?
Five things, in whatever order the journey needs.
| Step | What it does |
|---|---|
| Navigate | Opens a URL in a real browser |
| Fill | Types into a field you picked |
| Click | Clicks an element and waits for the page to settle |
| Wait | Waits for a specific element to appear |
| Assert | Checks the result and decides whether the journey passed |
An assertion can require that text is present or absent, that the title contains something, that the URL matches a pattern, that an element exists or does not, or that at least a certain number of elements are on the page.
What can't it do?
It does not sign in. There is nowhere to store credentials, there is no login step, and every check starts from a logged-out browser. A monitor can confirm that your sign-in page loads and the form is ready, which catches a deploy that breaks it, but it cannot go through the door.
It also cannot complete a purchase, upload a file, hover, work across browser tabs, or reach inside an embedded frame. A region that looks like a password or payment field is flagged for review rather than blocked.
How is this different from uptime monitoring?
| Uptime check | Workflow monitor | |
|---|---|---|
| What it asks | Did the server respond? | Did the journey produce the right result? |
| Runs in a browser | No | Yes, real Chromium |
| Catches a dead button | No | Yes |
| Catches a form that silently fails | No | Yes |
| Evidence on failure | A status code | A screenshot and a plain-English summary |
What does it cost?
| Plan | Monitors | Fastest check | Sites | Per month |
|---|---|---|---|---|
| Free | 2 | 6 hr | 1 | Free |
| Starter | 10 | 30 min | 3 | $49 |
| Growth | 50 | 15 min | 10 | $149 |
| Pro | 150 | 5 min | 25 | $349 |
| Agency | 500 | 1 min | 75 | Talk to us |
Annual billing is 2 months free. See full pricing or start a 14-day free trial, no card required.
14 days, no card required.
Frequently asked questions
Do I need to write code or record a script?
No. You pick a template, point it at the page, and choose what should be true at the end. There is nothing to install and no script to maintain as your site changes.
Can a workflow monitor log in to my site?
No. Checks always start logged out. A monitor can confirm your sign-in page loads and the sign-in form is present, but it does not submit credentials.
How many monitors do I need?
Fewer than most people expect. Cover the journeys that cost money when they break, usually the path into checkout, your main enquiry form, and the pages that feed them. The table above shows how many monitors each plan includes.
What happens on the very first check?
It runs like any other and records the result. Change monitors are the exception: their first check stores the baseline, so they cannot report a change until they have something to compare against.
Where do alerts go?
Email, Slack, or a signed webhook to any URL you choose. For Teams or Discord, point the webhook at Zapier, Make or a small relay of your own. There is no SMS.
Last updated