All templates

Automated Ekos Brew Day Schedule Digests

Every morning, WebRun opens Ekos, pulls every batch scheduled to brew that day with its recipe, target tank, and lead brewer, logs the day's lineup to a running Google Sheet, and posts a clear brew day digest to Slack so the team starts the shift already knowing the plan.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every day at 5:30 AM WebRunorchestrates each step
1 Ekos pull today's scheduled brews
2 Google Sheets log the day's brew lineup
3 Slack post the brew day digest
In short

How do I automatically send the brew day schedule to my team?

WebRun opens Ekos every morning, pulls every batch scheduled to brew that day with its recipe, target tank, and lead brewer, logs the lineup to a running Google Sheet, and posts a clear digest to Slack, so the brewing team starts each shift already knowing the day's plan without opening Ekos themselves.

  • The brewing team sees the full brew day lineup before shift start
  • Tank and recipe conflicts surface the moment they hit the schedule
  • No one has to open Ekos just to check what is brewing today

Built for craft breweries · head brewers · production managers · brewing teams

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

  2. 1
    Ekos - pull today's scheduled brews
    goekos.com
    WebRun in Ekos: pull today's scheduled brews
    WebRun opens Ekos to pull today's scheduled brews.
    • Open Ekos and go to the production or batch scheduling calendar
    • Filter to batches scheduled to brew today
    • Capture the recipe, target volume, assigned tank, and lead brewer for each
    • Note any batch flagged as a rebrew or a new recipe trial

    Done when Every batch scheduled to brew today is listed with its recipe, tank, and brewer.

  3. 2
    Google Sheets - log the day's brew lineup
    google.com
    WebRun in Google Sheets: log the day's brew lineup
    WebRun opens Google Sheets to log the day's brew lineup.
    • Open the brew day tracking Google Sheet
    • Add a row for each of today's batches with recipe, tank, volume, and brewer
    • Update the week view so the whole team can see the schedule ahead

    Done when Today's brew lineup is logged and the week view is current.

  4. 3
    Slack - post the brew day digest
    slack.com
    WebRun in Slack: post the brew day digest
    WebRun opens Slack to post the brew day digest.
    • Post the brew day digest to the brewing team channel
    • List each batch with its recipe, tank, and lead brewer in brew order
    • Flag any new recipe trial or rebrew so the team plans extra time

    Done when The brewing team has today's full brew schedule in Slack before shift start.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.goekos.com
ScheduleRuns automatically on this cadence
Every day at 5:30 AM
DeliveryHow each run's result reaches you
Brew day digest · Slack
OutputWhat each run produces - A Slack digest listing today's batches with recipe, tank, volume, and lead brewer, plus a logged row in the Google Sheets brew tracker.
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 it change the brew schedule itself?

No. WebRun only reads the schedule already set in Ekos and reports it. Changing tanks, recipes, or brew dates stays a decision your head brewer makes in Ekos.

Will it warn us about new recipe trials?

Yes. Any batch flagged as a new recipe or a rebrew is called out separately in the Slack digest so the team can plan extra time for it.

What if the schedule changes after the digest posts?

It reads the live schedule fresh each morning, so any change made in Ekos the night before shows up correctly on the next run.

Keep going

Related templates

Automated Ekos Can and Bottle Run Scheduling
Every Monday, WebRun opens Ekos, checks which batches are ready to package against can and bottle stock on hand, builds the week's packaging run order, and posts it to Slack so the packaging line knows exactly what runs and when.
Ekos›Google Sheets›Slack
Automated Ekos Distributor Allocation Reports
Every Friday, WebRun opens Ekos, pulls how much beer is allocated to each distributor and territory against what has shipped, and posts a clear allocation report to Slack so your sales team walks into Monday's distributor calls with the numbers already in hand.
Ekos›Google Sheets›Slack
Automated Ekos Distributor Depletion Reports
Every Monday, WebRun pulls distributor depletion data from Ekos, checks it against invoiced sales in QuickBooks, logs the trend to Google Sheets, and posts a depletion report to Slack so you know who is truly moving product.
Ekos›QuickBooks›Google Sheets›Slack

Put this on autopilot.

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

Deploy this workflow Talk to us