Confirm every overnight Keboola job actually ran
Every morning, WebRun opens Keboola, checks the run history for every scheduled orchestration from overnight, posts a summary to Telegram of what completed cleanly and what failed, and texts the on-call data engineer through Twilio if a critical job is still failing, so the data team knows the pipelines are trustworthy before anyone builds on top of them.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I confirm my overnight Keboola pipelines actually ran successfully?
WebRun checks every scheduled Keboola orchestration from overnight each morning, and posts a summary of what completed, warned, or failed to Telegram. If a job marked critical failed, it also texts the on-call data engineer through Twilio, so the team starts the day knowing exactly which pipelines are trustworthy and which need attention first.
- The team starts every day knowing exactly which pipelines ran clean
- Critical failures get a text instead of waiting to be discovered downstream
- A clean night still gets a confirmation, so nothing is left to assume
Built for Data engineering teams · Data platform teams · Analytics engineers · On-call engineers
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
connection.keboola.comin a real browser with your saved login - no setup, no API keys. -
1
Keboola - check overnight orchestration runs
WebRun opens Keboola to check overnight orchestration runs. - Open Keboola and check the run history for every scheduled orchestration
- Sort each run as completed, completed with warnings, or failed
- Note the job name and error for anything that failed
Done when Every scheduled orchestration from overnight has a run status.
- 2
-
3
Twilio - text on-call about critical failures
WebRun opens Twilio to text on-call about critical failures. - Text the on-call data engineer only if a job marked critical failed
- Name the job and the error in the text
- Skip the text entirely on a clean run
Done when The on-call engineer has been texted if a critical job failed.
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
What counts as a critical job?
Whichever orchestrations you mark as critical in Keboola. Only failures on those trigger a text, so Twilio is not used for routine or low priority jobs.
Does WebRun rerun a failed job?
No. It only reports the failure. Rerunning a job or fixing its configuration stays with your data engineer.
Do we still get a message if everything ran fine?
Yes. Telegram gets a short all clear summary every morning, so silence never has to be read as good news.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.