Log every blend recipe change before production roasts the old ratio
Every hour, WebRun opens Cropster, checks every blend for a recipe or ratio change since the last run, logs the old ratio, the new ratio, and who made the change to a Google Sheet, and pings your production team on Telegram the moment a blend changes so the next batch always roasts to the current recipe.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I make sure production never roasts an outdated blend recipe?
WebRun checks every active blend in Cropster each hour for a recipe or ratio change, logs the old ratio, the new ratio, and the timestamp to a Google Sheet, and pings your production team on Telegram the moment a blend changes, so the next batch on the roaster always runs the current recipe, not an outdated one.
- Production is pinged the moment a blend ratio changes, before the next batch starts
- Every recipe change is logged with a full before and after history
- No batch gets roasted to an outdated ratio because production missed the memo
Built for wholesale coffee roasters · production managers · head roasters
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
app.cropster.comin a real browser with your saved login - no setup, no API keys. -
1
Cropster - check every blend for a recipe change
cropster.com How to Automate Cropster
WebRun opens Cropster to check every blend for a recipe change. - Open Cropster and pull the current recipe for every active blend
- Compare each blend's component ratios against the version recorded last run
- Flag any blend where a component, ratio, or green lot has changed
Done when Every blend is checked against its last known recipe and any change is identified.
-
2
Google Sheets - log the old and new ratio
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log the old and new ratio. - Open the blend recipe change log
- Append a new row for each changed blend with the old ratio, the new ratio, and the timestamp
- Note which component or green lot drove the change
Done when Every recipe change this run is logged with its old and new ratio.
-
3
Telegram - ping production about the change
telegram.org How to Automate Telegram
WebRun opens Telegram to ping production about the change. - Send a Telegram message to the production channel for every blend that changed
- State the blend name, the new ratio, and the effective date
- Send nothing when no blend recipe has changed since the last run
Done when Production has been pinged about every blend change, or nothing is sent when no recipe changed.
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 change a blend recipe on its own?
No. WebRun only reads recipes that a person already changed in Cropster. It never edits a ratio or a recipe itself, it just logs and reports changes made by your team.
How far back does the change log go?
Every change is appended to the same Google Sheet, so you get a running history of every blend's ratio over time, not just the most recent change.
What if the same blend changes twice in one hour?
Both changes are logged and both trigger a Telegram ping, so production always sees the latest ratio even if it changed more than once between runs.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.