Automated Count Metric Threshold Alerts
Every few minutes, WebRun opens your tracked Count doc, reads the current value of your key metric, posts a status update to your ops Telegram group, and texts you through Twilio the moment it crosses the threshold you set.
How do I get alerted when a metric in my Count doc crosses a threshold?
WebRun reads your tracked Count doc's key metric every few minutes, posts the current status to your ops Telegram group, and texts you through Twilio the moment it crosses the threshold you set. Data teams using Count for collaborative analysis get a live metric watch without keeping the doc open all day.
- A threshold breach gets a text within minutes, not at the next manual check
- The ops group always has the current metric status in Telegram
- Only real threshold breaches trigger a text
Built for data analysts · startup data teams · growth 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
count.coin a real browser with your saved login - no setup, no API keys. -
1
Count - read the tracked metric
- Open the tracked Count doc
- Read the current value of your key metric query
- Compare it against the threshold you set
Done when The metric's current value is read and compared to threshold.
-
2
Telegram - post a status update
telegram.org
WebRun opens Telegram to post a status update. - Open the ops Telegram group
- Post the metric's current value and status
- Note the trend since the last check
Done when The ops group has the current metric status.
-
3
Twilio - text on a threshold breach
twilio.com
WebRun opens Twilio to text on a threshold breach. - If the metric crossed threshold, prepare a short alert
- Send it as a text through Twilio
- Name the metric and its current value
Done when You've been texted about any threshold breach.
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 edit the query in the Count doc?
No. It only reads the current result of the query you've already written. Editing the SQL or the doc stays a human task.
Will I get texted for every check?
No. Texts only go out on an actual threshold crossing. Routine checks within normal range stay in the Telegram status update.
Can I track more than one metric?
Set up a separate check for each metric you want watched. Each one reads its own query and threshold independently.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.