Automated Soda Data Quality Failure Alerts
Every time a Soda scan finishes, WebRun reads the results, and the moment a data quality check fails, creates a Trello card naming the table, column, and rule that broke, then pings the data owner on WhatsApp so a bad batch of data gets caught and assigned before it reaches a dashboard or report.
How do I get alerted immediately when a Soda data quality check fails?
WebRun checks every Soda scan as it finishes, and the moment a data quality check fails, creates a Trello card naming the table, column, and rule, then pings the data owner on WhatsApp. A bad batch of data gets caught and assigned to the right person within minutes, instead of surfacing later as a wrong number on a dashboard.
- Failed data checks get assigned to an owner within minutes
- The team works from a running Trello board of exactly what is failing
- Fixed checks clear from the board automatically on the next clean scan
Built for Data engineering teams · Analytics engineers · Data quality analysts · Data platform 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
cloud.soda.ioin a real browser with your saved login - no setup, no API keys. -
1
Soda - check the latest scan results
- Open Soda Cloud and check the latest scan results
- Find any check that failed
- Capture the table, column, and rule involved for each failure
Done when Every failed check in the scan has been captured with its detail.
-
2
Trello - create the failure card
trello.com
WebRun opens Trello to create the failure card. - Create a card for each failed check on the data quality board
- Include the table, column, and rule
- Move a card to done once its check passes on the next scan
Done when Every currently failing check has an open Trello card.
-
3
WhatsApp - ping the data owner
whatsapp.com
WebRun opens WhatsApp to ping the data owner. - Message the data owner naming the table and the failed rule
- Send only while there is at least one open failure for that owner
- Keep the message to the essentials
Done when The data owner has been pinged about their failing checks.
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 WebRun fix the failing data check itself?
No. It only detects and reports the failure. Fixing the underlying data or the check itself stays with the data owner.
How does WebRun know who the data owner is?
It uses the ownership you have set up for each table or check. If no owner is set, the alert goes to the general data quality channel instead.
Does the Trello card close automatically once fixed?
Yes. Once a check passes on a later scan, WebRun moves its card to done, so the board only shows what is still failing.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.