Get texted the moment a data quality check fails
Every time a Great Expectations validation run finishes, WebRun reads the results, and if any expectation in the suite fails, it texts the on-call data engineer through Twilio with the table and rule that broke, then saves the full Data Docs report to Google Drive so there is a record to open straight away.
- No credit card
- Under $0.01 per run
- Cancel anytime
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
greatexpectations.ioin a real browser with your saved login - no setup, no API keys. -
1
Great Expectations - check the latest validation run
greatexpectations.io
WebRun opens Great Expectations to check the latest validation run. - Open the latest validation run results
- Find any expectation that failed
- Capture the table, column, and rule involved for each failure
Done when Every failed expectation in the run has been captured with its detail.
-
2
Twilio - text the on-call engineer
twilio.com How to Automate Twilio
WebRun opens Twilio to text the on-call engineer. - Send a text to the on-call data engineer naming the failed table and rule
- Include how many rows or what share of the data failed
- Send only while there is at least one open failure
Done when The on-call engineer has been texted for this run's failures.
-
3
Google Drive - save the failure report
drive.google.com How to Automate Google Drive
WebRun opens Google Drive to save the failure report. - Save the run's Data Docs report to the team's data quality folder
- Name the file with the suite name and run timestamp
- Keep prior runs in place for comparison
Done when This run's report is saved to Drive and easy to find.
How do I get alerted immediately when a Great Expectations check fails?
WebRun watches every Great Expectations validation run as it finishes. The moment an expectation fails, it texts the on-call data engineer through Twilio with the table, column, and rule that broke, and saves the full Data Docs report to Google Drive, so a bad batch of data gets caught and documented within minutes, not discovered downstream.
- A failed data quality check texts the on-call engineer within minutes
- Every failure has a saved Data Docs report instead of a lost console log
- Repeat failures keep getting flagged until the underlying data is fixed
Built for Data engineering teams · Analytics engineers · Data platform teams · On-call engineers
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
Who gets texted when a check fails?
The on-call data engineer you set up in Twilio. WebRun never contacts a customer or anyone outside your data team.
Does it stop the pipeline or fix the data?
No. WebRun only reports what it finds. Deciding whether to halt a pipeline or fix the underlying data stays with your team.
What if the same check fails on the next run too?
It texts again. A repeat failure means the issue has not been fixed yet, so it keeps the on-call engineer informed each run.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.