Automated Grubhub Adjustment Dispute Queue
Every morning, WebRun opens your Grubhub account, reads the account adjustments and refunds charged back against recent orders, works out how many days are left to dispute each one, logs the queue to a Google Sheet, and sends the urgent ones to WhatsApp.
How do I catch Grubhub refund adjustments before the dispute window closes?
WebRun builds your Grubhub dispute queue every morning. It reads the refund adjustments charged back against your orders, matches each to its order ID and amount, counts the days left to dispute, logs the queue to Google Sheets, and flags anything closing soon on WhatsApp.
- Adjustments are challenged inside the window, not spotted on next month's statement
- Every adjustment carries an order ID and an amount at stake
- Disputes are prepared for a human to file, never submitted automatically
Built for restaurant owners · multi-location operators · restaurant bookkeepers · delivery managers
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.grubhub.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Grubhub - find refund adjustments on orders
grubhub.com
WebRun opens Grubhub to find refund adjustments on orders. - Open your Grubhub account and go to the payment statement and adjustments
- Capture each refund or adjustment with the order ID, the date, and the amount
- Match each adjustment back to the original order and its items
- Work out the days remaining in the dispute window for each one
- Never submit a dispute. WebRun prepares the queue and a human files it
Done when Every open adjustment is listed with its order ID, amount, and days left to dispute.
-
2
Google Sheets - log the dispute queue
google.com
WebRun opens Google Sheets to log the dispute queue. - Append a row per adjustment with order ID, date, amount, reason, and days remaining
- Sort the sheet so the soonest deadline sits at the top
- Mark rows already disputed so nothing is worked twice
- Keep a running total of the money at stake this month
Done when The dispute queue sheet is current and sorted by deadline.
-
3
WhatsApp - flag what expires first
whatsapp.com
WebRun opens WhatsApp to flag what expires first. - Send the manager a WhatsApp note with anything closing in the next two days
- Lead with the order ID, the amount, and the days remaining
- Link to the sheet for the full queue
- Keep the message internal to your team
Done when The team knows which adjustments must be challenged today.
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
Will it file disputes for me?
No. WebRun builds the queue and puts the evidence in front of you. Submitting a dispute is a human decision, so nothing is filed against an order without someone reviewing it first.
How does it know the deadline?
It reads the adjustment date on your Grubhub statement and counts forward using the dispute window you configure, so each row shows the days remaining rather than a guess.
What if an adjustment was already disputed?
It is marked in the sheet and dropped from the daily alert, so the same order never gets worked twice and the queue only shows what still needs attention.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.