Log every reefer door-open event as an exception
Every hour, WebRun opens Wireless Links Fleet.Net, reads the reefer door sensor events, records any door opened longer than your threshold or away from a scheduled stop into a Google Sheet exception log, and posts an internal Slack digest so long or off route door openings are caught the same day.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track reefer door-open events that put a load at risk?
WebRun reads reefer door sensor events from Wireless Links Fleet.Net every hour and matches each against your scheduled stops. It logs any door opened too long or away from a stop into a Google Sheet exception list and posts an internal Slack digest, so long or off route door openings that risk the load are caught the same day.
- Long or off route door openings are caught the same hour they happen
- Every flagged opening leaves a row with duration and temperature at open
- Operations gets an internal digest with no driver or customer contact
Built for reefer carriers · cold chain fleets · food distributors · fleet 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.wlius.com/fleet-management-systemin a real browser with your saved login - no setup, no API keys. -
1
Wireless Links Fleet.Net - read reefer door events
wlius.com How to Automate Wireless Links Fleet.Net
WebRun opens Wireless Links Fleet.Net to read reefer door events. - Open Wireless Links Fleet.Net and pull reefer door sensor events since the last run
- For each event, capture the trailer, open time, duration, location, and box temperature at open
- Match each door open against the scheduled stop list to tell planned from off route
- Flag any opening longer than your duration threshold or away from a scheduled stop
Done when Every door open event is captured and tagged as planned or an exception.
-
2
Google Sheets - log door open exceptions
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log door open exceptions. - Open the Reefer Door Exception Log sheet
- Append a row per flagged opening with trailer, time, duration, location, and temperature at open
- Tag each row with the reason it was flagged, too long or off route
- Skip any event already logged so nothing is recorded twice
Done when The exception log holds one row per flagged door opening with its reason.
-
3
Slack - post the exception digest
slack.com How to Automate Slack
WebRun opens Slack to post the exception digest. - Post an hourly Slack digest counting flagged door openings by trailer and reason
- List the longest openings first with trailer, duration, and box temperature at open
- Link to the full Google Sheet for the complete exception list
- This is an internal digest, so it may post to your operations channel automatically
Done when Operations has a Slack digest of the hour's door open exceptions.
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 drivers or customers about door openings?
No. This workflow only logs door events to a Google Sheet and posts an internal Slack digest to your operations team. It never contacts a driver or customer, so it is safe to run unattended.
How does it tell a normal stop from an exception?
It matches each door opening against your scheduled stop list and your duration threshold. Openings at planned stops within the time limit are treated as normal, and only long or off route openings are flagged.
Can I change how long a door open is allowed?
Yes. You set the duration threshold and can vary it by product or lane, so a chilled load and a frozen load can carry different door open limits.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.