All templates

Automated Arborgold Storm Billing Summary

Within an hour of a storm being marked complete in Arborgold, WebRun pulls every job logged for the event across every crew, reconciles the total billable revenue against what has actually been invoiced in QuickBooks, and posts a full storm billing summary to Slack, so ownership knows what the storm brought in before the next one starts.

Runs on WebRun · Strict Lockdown policy
Within an hour of a storm being marked complete in Arborgold WebRunorchestrates each step
1 Arborgold pull every job and material used this storm
2 QuickBooks reconcile total billable revenue for the storm
3 Slack post the storm billing summary
In short

How do I get a billing summary right after a snow storm ends?

Within an hour of a storm being marked complete in Arborgold, WebRun totals every job logged for the event across all crews, reconciles that total against what has already been invoiced in QuickBooks, and posts a full billing summary to Slack. Ownership sees exactly what the storm brought in and which jobs still need an invoice before the next one hits.

  • Ownership sees storm revenue within an hour of the last route closing out
  • Unbilled jobs get flagged before they are forgotten between storms
  • Billing team starts reconciliation from a finished summary, not raw job logs

Built for snow removal contractors · snow removal business owners · commercial snow removal billing teams · 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 - pull every job and material used this storm
    arborgold.com
    WebRun in Arborgold: pull every job and material used this storm
    WebRun opens Arborgold to pull every job and material used this storm.
    • Open Arborgold and pull every job logged against this storm event across all crews
    • Total the properties serviced, materials used, and hours logged
    • Break the total down by per-push and seasonal contract revenue

    Done when Every job logged for the storm is totaled by revenue type.

  3. 2
    QuickBooks - reconcile total billable revenue for the storm
    • Check how much of the storm's billable total has already been invoiced
    • Flag any completed job with no matching invoice yet

    Done when The storm's billed total is reconciled against invoiced amounts in QuickBooks.

  4. 3
    Slack - post the storm billing summary
    slack.com
    WebRun in Slack: post the storm billing summary
    WebRun opens Slack to post the storm billing summary.
    • Post a storm billing summary to the ops channel with total revenue, properties served, and materials used
    • Flag any completed jobs still missing an invoice

    Done when Ownership has the full storm billing summary in Slack.

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
Within an hour of a storm being marked complete in Arborgold
DeliveryHow each run's result reaches you
Storm summary · Slack
OutputWhat each run produces - A full storm billing summary in Slack with total revenue, properties served, and any jobs still unbilled.
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 send any new invoices or charge a card?

No. It only reconciles totals already logged in Arborgold and QuickBooks and reports them to Slack. No invoice is created or sent and no card is charged by this workflow.

How does it know the storm is finished?

It checks for the storm event being marked complete in Arborgold, so the summary runs once the last route is closed out, not partway through.

What happens to jobs it finds without an invoice?

They are flagged in the Slack summary so your billing team can follow up, instead of a completed job quietly going unbilled.

Put this on autopilot.

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