All templates

Automated Arborgold Route Completion Checks

Every night during an active storm, WebRun opens Arborgold, checks GPS route completion against the stop list for every crew, posts a Slack summary flagging any property still marked incomplete, and logs the night's completion record to a Google Sheet so you have proof of service for every contract.

Runs on WebRun · Strict Lockdown policy
Every night at 11:00 PM during an active storm WebRunorchestrates each step
1 Arborgold check every route's completion status
2 Slack post the verification summary
3 Google Sheets log completion for the storm
In short

How do I verify every snow removal route actually got completed?

WebRun checks Arborgold every night for GPS completion status on every route run during the storm, then posts a Slack summary flagging any stop still marked incomplete or unconfirmed. It logs a full completion record property by property to a Google Sheet, giving you proof of service for every contract without anyone manually checking a single route.

  • Incomplete stops get flagged the same night, not after a customer complaint
  • Every contract has a GPS-backed proof of service record
  • Ops manager sees the whole storm's completion status in one Slack summary

Built for snow removal contractors · commercial snow plow operators · property management snow vendors · Arborgold users

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.arborgold.com/login in a real browser with your saved login - no setup, no API keys.

  2. 1
    Arborgold - check every route's completion status
    arborgold.com
    WebRun in Arborgold: check every route's completion status
    WebRun opens Arborgold to check every route's completion status.
    • Open Arborgold and pull each crew's route with GPS completion status per stop
    • Flag any stop marked incomplete, skipped, or with no GPS confirmation
    • Note the service level and time completed for finished stops

    Done when Every stop on every route has a checked completion status.

  3. 2
    Slack - post the verification summary
    slack.com
    WebRun in Slack: post the verification summary
    WebRun opens Slack to post the verification summary.
    • Post a summary to the ops channel listing any incomplete or unconfirmed stops by crew
    • Include the total stops completed against the total scheduled for the night

    Done when Ops manager has tonight's completion summary with any gaps flagged.

  4. 3
    Google Sheets - log completion for the storm
    google.com
    WebRun in Google Sheets: log completion for the storm
    WebRun opens Google Sheets to log completion for the storm.
    • Add a row per property with the crew, completion time, and service level for the storm
    • Mark any property still outstanding at the time of the run

    Done when The storm's completion record is logged property by property.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.arborgold.com/login
ScheduleRuns automatically on this cadence
Every night at 11:00 PM during an active storm
DeliveryHow each run's result reaches you
Completion summary · Slack
OutputWhat each run produces - A Slack summary of any incomplete stops plus a full completion log in Sheets for the storm.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does this contact the customer about their service?

No. It only checks GPS completion data already in Arborgold and reports internally to Slack and Sheets. Customers are not contacted by this workflow.

How does it know a stop was actually completed?

It reads the GPS confirmation and completion timestamp Arborgold already records for each stop, so a route cannot be marked done without the location data to back it up.

What happens with the incomplete stops it finds?

They are flagged in the Slack summary so your ops manager can send a crew back out before the log closes for the night.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.