Automated dbt Cloud Test Failure Alerts
Every hour, WebRun opens dbt Cloud, checks the latest job runs for failed tests, messages the on-call analytics engineer on WhatsApp with the failed test and a run link, and schedules a same-day fix block on their calendar.
How do I get alerted the moment a dbt test fails?
WebRun checks dbt Cloud job runs every hour for failed tests. The moment one breaks, it messages the on-call analytics engineer on WhatsApp with the failed test, the model, and a link to the run, then schedules a same-day fix block on their calendar, so broken data models get caught before anyone downstream trusts bad numbers.
- Failed tests get a WhatsApp alert within the hour, not at next standup
- Every failure comes with a scheduled fix block, not just a notification
- Bad data gets caught before it reaches a dashboard or report
Built for analytics engineers · data engineering teams · data platform admins · BI 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.getdbt.comin a real browser with your saved login - no setup, no API keys. -
1
dbt Labs - check job runs for test failures
WebRun opens dbt Cloud to check job runs for test failures. - Open dbt Cloud and list the latest job runs
- Check each run's test results for any failure or warning
- Note the failed test, the model it belongs to, and the run link
Done when Every completed job run has its test results checked.
-
2
WhatsApp - message the on-call engineer
WebRun sends a WhatsApp message to the on-call engineer. - Message the on-call analytics engineer with the failed test and model
- Include a link to the run so they can open it directly
Done when The on-call engineer has a WhatsApp message for every failed test.
-
3
Google Calendar - schedule a fix block
WebRun opens Google Calendar to schedule a fix block. - Add a fix block to the on-call engineer's calendar for same-day triage
- Set it right after the current meeting gap
Done when A fix block exists on the calendar for every open test failure.
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 change the model or skip the failing test?
No. WebRun only reports the failure and schedules time to fix it. Editing the model or the test itself is left to a human.
How urgent does a failure have to be to trigger a message?
Any failed test on a completed job run triggers a WhatsApp message. Warnings are noted in the run details but don't page anyone.
What if the same test fails on the next run too?
It checks the latest run each hour, so a still-failing test keeps its fix block on the calendar until a run comes back clean.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.