All templates

Automated Cropster Roast Batch Schedule Digest

Every morning, WebRun opens Cropster, pulls every roast batch scheduled for today with its profile, target roast level, and batch size, logs the day's plan to your production Google Sheet, and posts the full schedule to Slack so the roast team knows the running order before the first bean hits the drum.

Runs on WebRun · Strict Lockdown policy
Every day at 6:00 AM WebRunorchestrates each step
1 Cropster pull today's scheduled roast batches
2 Google Sheets log the day's production plan
3 Slack post the roast schedule to the team
In short

How do I get today's roast schedule to my team automatically?

WebRun opens Cropster every morning, pulls every roast batch scheduled for the day with its profile, target roast level, and batch size, logs the plan to your production Google Sheet, and posts the full running order to Slack, so your roast team knows exactly what to roast, in what sequence, before the first batch starts.

  • Roast team starts the day with the full schedule already in Slack
  • New or untested profiles get flagged before they hit the drum
  • Production log stays up to date without manual data entry

Built for wholesale coffee roasters · head roasters · production planners

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 app.cropster.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Cropster - pull today's scheduled roast batches
    cropster.com
    WebRun in Cropster: pull today's scheduled roast batches
    WebRun opens Cropster to pull today's scheduled roast batches.
    • Open Cropster and pull every roast batch scheduled for today
    • Capture the profile, target roast level, green lot, and batch size for each
    • Order the batches by scheduled start time

    Done when Every roast batch scheduled for today is listed in start time order with its profile and size.

  3. 2
    Google Sheets - log the day's production plan
    google.com
    WebRun in Google Sheets: log the day's production plan
    WebRun opens Google Sheets to log the day's production plan.
    • Open the production log Google Sheet
    • Append today's date with each batch, its profile, green lot, and the order it fulfills
    • Mark any batch that is a rerun or a new profile test so the roaster can flag it

    Done when Today's full batch plan is logged in the production sheet with order references.

  4. 3
    Slack - post the roast schedule to the team
    slack.com
    WebRun in Slack: post the roast schedule to the team
    WebRun opens Slack to post the roast schedule to the team.
    • Post the day's roast schedule to the roasting channel in running order
    • Include the profile, batch size, and target roast level for each batch
    • Flag any new or test profile at the top so the roaster sees it first

    Done when The roast team has today's schedule in Slack before the first batch starts.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.cropster.com
ScheduleRuns automatically on this cadence
Every day at 6:00 AM
DeliveryHow each run's result reaches you
Roast schedule · Slack
OutputWhat each run produces - The day's roast schedule in running order, with profile, batch size, target roast level, and any new or test batches flagged.
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

Will it change my roast profiles or batch sizes?

No. WebRun only reads the batches already scheduled in Cropster and reports them. It never edits a profile, a batch size, or a schedule on its own.

How does it flag test or new profiles?

It compares each scheduled batch against your production log history. Any profile that hasn't run in the last 30 days gets flagged at the top of the Slack schedule so your roaster double checks it.

What if the schedule changes after the message goes out?

Rerun it any time and it posts an updated schedule reading the latest state of Cropster. It does not automatically repost, so a same day change needs a manual rerun.

Put this on autopilot.

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