Automated Backflow Retest Tracking
Every morning, WebRun opens Uptick, checks every backflow prevention assembly against its annual retest date, updates a Google Sheets tracker with what is due or overdue, and posts your team a short Slack list so no assembly slips past its certification window.
How do I track which backflow assemblies are due for retest?
WebRun reviews every backflow prevention assembly in Uptick each morning and works out which are due or overdue for their annual retest. It updates a Google Sheets tracker and posts your team a Slack due list sorted by urgency, so no assembly slips past its certification window and retests get scheduled in time.
- Assemblies surface 30 days before their retest, never overdue by surprise
- A live tracker shows every assembly's certification status at a glance
- The team opens Slack to a ranked retest list every morning
Built for fire protection contractors · backflow test firms · compliance coordinators · 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
app.uptickhq.comin a real browser with your saved login - no setup, no API keys. -
1
Uptick - check backflow retest dates
uptickhq.com
WebRun checks each backflow assembly against its annual retest date. - Open Uptick and filter assets to backflow prevention assemblies
- Read each assembly's last retest date and certification interval
- Flag any due within 30 days or already past their retest date
Done when Every backflow assembly has been checked against its retest window.
-
2
Google Sheets - update the retest tracker
google.com
WebRun updates the backflow retest tracker with due and overdue rows. - Update a tracking sheet with each assembly, its property, and next retest date
- Sort so the soonest due and overdue assemblies sit at the top
- Mark completed retests as done so the tracker stays current
Done when The tracker reflects every assembly's current retest status.
-
3
Slack - post the due list
slack.com
WebRun posts the backflow retest due list to your operations channel. - Post a short list of assemblies due for retest to the operations channel
- Put overdue assemblies first, then those due within 30 days
- Include the property and jurisdiction so the team can schedule
Done when Your team has today's backflow retest due list in Slack.
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 this contact customers or authorities?
No. This workflow is internal only. WebRun updates your Google Sheets tracker and posts a Slack due list for your team to act on. It never messages a property contact or a jurisdiction.
How does it know a retest is due?
It reads each backflow assembly's last retest date and certification interval in Uptick every morning, then flags anything due within 30 days or already overdue on the tracker.
Will the tracker double-count completed retests?
No. WebRun reads the live status in Uptick each run, so any assembly retested and recertified is marked done and drops off the due list automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.