Automated Grease-Trap Route Scheduling
Every morning, WebRun opens Tank Track, pulls the grease trap jobs scheduled for today, sequences them into an efficient route for each driver with site notes, gate codes, and trap locations, writes each stop to the driver's Google Calendar, and sends the full run to the driver over Telegram.
How do I build and send each driver a daily grease trap pump route automatically?
WebRun opens Tank Track every morning, pulls the grease trap jobs scheduled for today, and sequences them into an efficient route per driver with gate codes and trap locations. It writes each stop to the driver's Google Calendar in order and sends the full run over Telegram, so every driver starts the day with a clear, ordered route.
- Drivers start the day with an ordered route instead of a raw job list
- Every stop carries its gate code and trap location, cutting on-site delays
- A changed schedule is re-pushed to calendar and Telegram without duplicates
Built for grease trap haulers · pump truck dispatchers · liquid waste operators · field service 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
tank-track.comin a real browser with your saved login - no setup, no API keys. -
1
Tank Track - pull today's scheduled jobs
tank-track.com
WebRun opens Tank Track to pull today's scheduled grease trap jobs. - Open Tank Track and list the grease trap jobs scheduled for today
- Capture the site address, trap location, gate code, contact, and any special access notes for each
- Group the jobs by assigned driver and truck
- Order each driver's stops into an efficient route from their start point
Done when Every driver has an ordered list of today's stops with full site notes.
-
2
Google Calendar - place each stop in order
calendar.google.com
WebRun places each stop on the driver's Google Calendar in route order. - Open each driver's Google Calendar for today
- Add one timed event per stop in route order with the address and access notes in the description
- Space the events using expected drive and service time between stops
- Update rather than duplicate any stop already on the calendar from an earlier run
Done when Each driver's calendar shows today's stops in route order with site details.
-
3
Telegram - send the driver their route
telegram.org
WebRun sends each driver their ordered route over Telegram. - Send each driver a Telegram message with their ordered stop list for the day
- Include the address, trap location, and access note for every stop
- Call out the first stop and the disposal site to end at
- Post the route to the driver's channel so dispatch can see it too
Done when Every driver has today's route in Telegram with stop-by-stop detail.
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 message customers or only my drivers?
Only your drivers and dispatch. The route goes to the driver over Telegram and onto their internal Google Calendar. WebRun never contacts a customer as part of building the route.
How does it decide the stop order?
It sequences each driver's scheduled jobs into an efficient route from their start point using the service addresses in Tank Track, then spaces the calendar stops by expected drive and service time between them.
What if the schedule changes after the route goes out?
Re-run it and WebRun reads the live schedule in Tank Track, then updates each driver's calendar and sends a refreshed Telegram route rather than duplicating the existing stops.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.