Confirm every overnight Rivery pipeline actually ran
Every morning, WebRun opens Rivery, checks the run history for every scheduled pipeline from overnight, logs any failure to Airtable with the pipeline name and error, and drafts a summary email in Gmail for the data lead ranking issues by how critical the pipeline is, so broken pipelines get attention before the day's dashboards rely on them.
- 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
console.rivery.ioin a real browser with your saved login - no setup, no API keys. -
1
Rivery - check overnight pipeline runs
rivery.io
WebRun opens Rivery to check overnight pipeline runs. - Open Rivery and check the run history for every scheduled pipeline from overnight
- Find any run that ended in a failure
- Capture the pipeline name, source, and error message
Done when Every failed overnight run has been captured with its detail.
-
2
Airtable - log the failures
airtable.com How to Automate Airtable
WebRun opens Airtable to log the failures. - Create a record for each failed pipeline on the data health base
- Include the source, error, and how long it has been failing
- Mark a record resolved once its pipeline runs successfully again
Done when Every currently failing pipeline has a logged Airtable record.
-
3
Gmail - draft the summary email
gmail.com How to Automate Gmail
WebRun opens Gmail to draft the summary email. - Draft a summary email ranking failed pipelines by criticality
- List the pipeline name and error for each
- Leave the email as a draft. Never send it without review
Done when A summary email is waiting in Gmail drafts for the data lead.
How do I confirm my overnight Rivery pipelines actually ran successfully?
WebRun checks every scheduled Rivery pipeline from overnight each morning, logs any failure to Airtable with the pipeline name and error, and drafts a ranked summary email in Gmail for the data lead. Broken pipelines get logged and surfaced the same morning, so reporting does not quietly run on incomplete or stale data.
- Failed pipelines get logged and surfaced the same morning
- The data lead reviews a ranked summary instead of digging through run logs
- Resolved pipelines are marked automatically once they run clean again
Built for Data engineering teams · Data platform teams · Analytics engineers · BI teams
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 the summary email go out without anyone reviewing it?
No. WebRun only drafts it in Gmail. Nothing reaches the data lead's inbox until it is reviewed and sent.
Does WebRun rerun a failed pipeline?
No. It only detects and reports the failure. Rerunning a pipeline or fixing its configuration stays with your data team.
How does it decide which pipelines are critical?
You mark which pipelines are critical in Rivery. Those are ranked first in the summary email so the most important issues get seen first.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.