Automated Propane Tank Monitor Low-Level Alerts
Every hour, WebRun checks tank-monitor readings in ADD Systems for any customer tank that has fallen to or below your low-level threshold, logs the event to a Google Sheet, and posts an immediate dispatch alert in Slack so a delivery run can be scheduled before the customer runs out.
How do I get automatic alerts when a monitored propane tank runs low?
WebRun checks tank-monitor readings in ADD Systems every hour and alerts your dispatch team in Slack the moment any customer tank falls to or below your low-level threshold. Each event is logged to Google Sheets, and tanks with under 3 days of estimated supply are flagged as urgent so emergency deliveries can be scheduled immediately.
- Dispatch teams are alerted within an hour of any tank crossing the low-level threshold
- Run-out risk is flagged before customers notice a problem
- Every low-level event is logged automatically for compliance and operations review
Built for propane delivery companies · heating fuel dispatchers · fuel oil dealers with tank monitors · remote monitoring operations 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
www.addsys.comin a real browser with your saved login - no setup, no API keys. -
1
ADD Systems - check tank-monitor readings for low levels
- Open ADD Systems and navigate to the tank-monitor or remote-monitoring view
- Identify any customer tank whose current reading is at or below the configured alert threshold (typically 20 to 25 percent)
- Capture the customer name, address, current tank level, estimated days of supply, and account type
Done when Every tank at or below the low-level threshold is identified with its customer and level details.
-
2
Google Sheets - log low-level event
google.com
WebRun opens Google Sheets to log low-level event. - Append a new row to the low-level event log for each flagged tank
- Record the timestamp, customer name, address, tank level, and alert threshold crossed
Done when Every low-level event is logged to the monitoring sheet with a timestamp.
-
3
Slack - post dispatch alert
slack.com
WebRun opens Slack to post dispatch alert. - Post a dispatch alert to the delivery channel for each new low-level tank detected
- Include the customer name, address, current level, and estimated days of supply
- Flag run-out-risk accounts, where estimated supply is under 3 days, as urgent
Done when Dispatch team has an immediate alert for every tank that crossed the low-level threshold.
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 it alert the same tank multiple times if it stays low?
It compares new readings to the previous run's log in Google Sheets and only alerts on first detection or when a tank drops to a new lower threshold, avoiding repeated noise for the same event.
What threshold triggers the alert?
WebRun uses the low-level threshold configured in your ADD Systems tank-monitor settings, typically 20 to 25 percent. You can adjust the threshold in ADD Systems and the run will respect the updated value immediately.
Can it prioritize tanks that are critically low over ones that just crossed the threshold?
Yes. Tanks estimated to have under 3 days of supply are flagged as urgent in the Slack alert and sorted to the top of the list so dispatchers can schedule an emergency delivery first.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.