Automated Maze Usability Test Results Digest
Every morning, WebRun checks your active Maze usability tests for new responses since the day before, posts a digest of completion rates and drop-off points to Slack, and sends a same-day Telegram flag to the research lead if any single step's drop-off crosses 50 percent.
How do I get a daily digest of my Maze usability test results?
WebRun checks your active Maze usability tests every morning for new responses since the day before, posting a digest of completion rates and drop-off points to Slack. If any single step's drop-off crosses 50 percent, it also sends a same-day flag to the research lead on Telegram, so a broken flow gets noticed fast.
- The team sees test results daily without opening Maze
- Broken flows with high drop-off get flagged the same day
- Research findings stay visible instead of buried in reports
Built for UX researchers · product teams · UX designers · research ops
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
auth.maze.co/loginin a real browser with your saved login - no setup, no API keys. -
1
Maze - check new test responses
- Open each active usability test
- Check completion rate and new responses since yesterday
- Note the misclick rate and drop-off point
Done when Every active test has yesterday's response and completion numbers.
-
2
Slack - post the results digest
slack.com
WebRun posts the results digest to Slack. - Post a digest of each test's new responses and completion rate to the research channel
- Note the biggest drop-off point
- Link to the full results
Done when The team has today's Maze results digest in Slack.
-
3
Telegram - flag a high drop-off rate
telegram.org
WebRun flags a high drop-off rate on Telegram. - Watch for any test whose drop-off rate crosses 50 percent at one step
- Send a flag to the research lead naming the test and the step
Done when A high drop-off gets a same-day flag instead of waiting to be noticed.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it create or launch new tests?
No. WebRun only reads results from tests your team has already launched. It never creates, edits, or launches a usability test on its own.
What counts as a high drop-off?
Any single step in a test flow where over half of participants drop off, flagged separately so it doesn't wait for the regular morning digest.
Can it track more than one test at a time?
Yes. It checks every active test you give it access to, and the digest breaks results out test by test.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.