Automated Tadabase Threshold Alerts
Every hour, WebRun opens Tadabase, checks records against the thresholds you've set, such as low inventory or a spike in form submissions, posts the alert to Telegram, and texts you through Twilio when it's urgent.
How do I get alerted when a Tadabase record crosses a critical threshold?
WebRun checks your Tadabase app every hour against the thresholds you set, whether that's inventory running low or form submissions spiking. It posts every breach to Telegram and sends a text through Twilio for anything marked urgent, so a critical record change gets noticed within the hour, not at the next manual check.
- Critical breaches noticed within the hour, not at the next check
- Urgent items escalated by text, routine ones stay in Telegram
- No repeated alerts for a breach already flagged
Built for operations teams · no-code builders · small business owners · inventory managers
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.tadabase.ioin a real browser with your saved login - no setup, no API keys. -
1
Tadabase - check records against thresholds
WebRun opens Tadabase to check records against thresholds. - Open the app and check records against your set thresholds
- Note which records crossed a threshold since the last check
- Rank breaches by how far over or under the threshold they are
Done when Every record breaching a threshold this hour is identified.
-
2
Telegram - post the alert
WebRun opens Telegram to post the alert. - Post each breach to your alerts channel with the record and threshold
- Include how far past the threshold it is
- Skip records already alerted this run
Done when Every new breach has been posted to Telegram.
-
3
Twilio - text urgent breaches
WebRun opens Twilio to text urgent breaches. - Send a text only for breaches marked urgent
- Include the record name and current value
- Skip the text for routine, non-urgent breaches
Done when An SMS has gone out for any urgent 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
Will it change any record values to fix the issue?
No. WebRun only reads records and alerts you. Updating a record or restocking inventory is left to your team.
Who decides what counts as urgent?
You do. You set which thresholds are routine versus urgent when this workflow is configured, and the text only fires for the urgent ones.
Will I get alerted for the same breach twice?
No. It tracks what's already been posted this run, so a record stuck over threshold does not spam the same alert every hour.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.