Automated ClicData Dashboard Alert Digest
Every morning, WebRun opens ClicData, reads every configured KPI alert and its current value, posts a digest to Slack, and sends an extra Telegram ping for any KPI that breached a critical threshold.
How do I get a daily digest of ClicData KPI alerts?
WebRun reads every configured ClicData KPI alert every morning and posts a digest to Slack, then sends an extra Telegram ping for any KPI that breached a critical threshold. BI and operations teams get one daily summary in Slack and a fast, separate escalation path for whatever genuinely needs attention now.
- KPI values land in Slack every morning without a login
- Critical breaches reach Telegram separately so they're never missed
- A broken data source is reported, not silently dropped
Built for BI teams · operations teams · business analysts
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
app.clicdata.comin a real browser with your saved login - no setup, no API keys. -
1
ClicData - read KPI alerts
- Open ClicData and check every configured KPI alert
- Read the current value behind each one
- Note which alerts are within normal range and which breached
Done when Every KPI alert's current value is read.
-
2
Slack - post the digest
slack.com
WebRun opens Slack to post the digest. - Open the analytics channel in Slack
- Post each KPI's current value and status
- Link back to the dashboard in ClicData for full detail
Done when Today's digest is posted in Slack.
-
3
Telegram - escalate critical breaches
telegram.org
WebRun opens Telegram to escalate critical breaches. - If any KPI breached a critical threshold, prepare a short escalation
- Send it to the on-call Telegram group
- Name the exact KPI and how far past threshold it is
Done when Any critical breach 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 the KPI alerts?
No. It only reads alerts you've already configured in ClicData. Creating or tuning an alert stays a human task.
When does something escalate to Telegram instead of just Slack?
Only when a KPI breaches the critical threshold you set for it. Everything else stays a normal line in the Slack digest.
What if a KPI's data source fails to load?
It's reported as unavailable in the digest rather than skipped silently, so a broken data source 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.