Automated Redash Daily Query Digest
Every morning, WebRun opens Redash, reads the latest results from your key scheduled queries, posts a digest to Slack, and sends an extra ping to Telegram only when a result crosses the threshold you set.
How do I get a daily digest of my Redash query results?
WebRun reads the latest results from your scheduled Redash queries every morning and posts a digest to Slack, then sends an extra Telegram ping only when a result crosses the threshold you set. Data teams get one daily summary in Slack and a fast, separate escalation path for anything that needs attention now.
- Key query results land in Slack every morning without a login
- Threshold breaches reach Telegram separately so they're never missed
- A failed scheduled query is reported, not silently dropped
Built for data analysts · BI teams · data engineering 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
redash.ioin a real browser with your saved login - no setup, no API keys. -
1
Redash - read the key query results
redash.io
WebRun opens Redash to read the key query results. - Open Redash and check the latest run of each tracked query
- Read the current result for every one
- Compare each against its normal range or your set threshold
Done when Every tracked query's latest result is read and compared.
-
2
Slack - post the daily digest
slack.com
WebRun opens Slack to post the daily digest. - Open the analytics channel in Slack
- Post each query's latest result with the change from yesterday
- Link back to the query in Redash for anyone who wants the detail
Done when This morning's digest is posted in Slack.
-
3
Telegram - escalate anything critical
telegram.org
WebRun opens Telegram to escalate anything critical. - If any result crossed the threshold, prepare a short escalation message
- Send it to the on-call Telegram group
- Name the exact query and the number that triggered it
Done when Anything past the threshold has been escalated on Telegram.
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 create or edit queries in Redash?
No. It only runs and reads the results of queries you already scheduled. Writing or editing SQL stays a human task.
When does something go to Telegram instead of just Slack?
Only when a result crosses the threshold you set for that query. Everything else stays a normal line in the Slack digest.
What if a scheduled query fails to run?
It's reported as a failure in the digest rather than skipped silently, so a broken query doesn't just disappear from the report.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.