Automated FullStory Error Spike Alerts
Every hour, WebRun signs in to FullStory, reads the error and console event counts for the pages that matter most, compares them against the same hour on a normal day, and when errors jump it texts the on-call engineer through Twilio and posts the affected pages, browsers, and replay links to your WhatsApp engineering chat.
How do I get alerted when errors spike on my website?
WebRun checks FullStory every hour, reading error and console event counts on your key pages and comparing them against a normal day. When errors spike, it texts the on-call engineer through Twilio and posts the affected pages, browsers, and session replay links to your WhatsApp engineering chat.
- Broken pages are found within the hour, not from a support ticket
- On-call gets the page, the browser, and a replay link in one message
- Only internal roster numbers are ever texted
Built for ecommerce teams · product engineers · SaaS operations · growth teams
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
app.fullstory.comin a real browser with your saved login - no setup, no API keys. -
1
FullStory - check errors on key pages
fullstory.com
WebRun opens FullStory to check errors on key pages. - Sign in to FullStory and open the segments and dashboards covering your checkout, signup, and other key pages
- Read the count of error and console events in the last hour and the pages they landed on
- Compare against the same hour on a normal day, and capture the browsers, devices, and a few session replay links for anything abnormal
Done when This hour's error counts are compared against baseline and the affected sessions are captured.
-
2
Twilio - text the on-call engineer
twilio.com
WebRun opens Twilio to text the on-call engineer. - Send a short text to the on-call number from your own internal roster when errors clear the spike threshold
- Keep it to the page, the error count, and the multiple over baseline so it reads in one glance
- Only roster numbers are ever texted. WebRun never texts a customer, and anything off roster is staged for your approval instead
Done when The on-call engineer has been paged about a real spike.
-
3
WhatsApp - post the session detail
whatsapp.com
WebRun opens WhatsApp to post the session detail. - Post the full detail to your engineering chat: the pages, the browsers, the devices, and the replay links
- Add how many distinct users hit the error so severity is obvious
- Repeat the alert only if the spike is still running an hour later
Done when Engineering has everything needed to start debugging.
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
Will it text customers who hit the error?
No. Twilio only messages the on-call numbers on your own internal roster. Any message to a number outside that roster is staged for a person to approve, so no affected user is ever contacted by the run.
How does it avoid false alarms?
It compares this hour against the same hour on a normal day rather than a fixed number, and it only alerts once per spike. A quiet hour produces no message at all.
Does it change anything in FullStory?
No. The FullStory step is read only. WebRun opens your existing segments and dashboards, reads the counts, and copies replay links without creating, editing, or deleting anything.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.