Automated GoPrep Menu Rotation Checklists
When a new menu rotation is added in GoPrep, WebRun reads every new or changed recipe, creates a launch checklist card in Trello for each covering nutrition labels, photos, and pricing, and posts your kitchen and marketing team a Slack summary of what still needs to be done before launch day.
How do I automatically build a launch checklist for a new meal-prep menu rotation?
When a new menu rotation is added in GoPrep, WebRun reads every new or changed recipe and creates a Trello checklist card for each, covering the nutrition label, photo, pricing, and allergen review needed before launch. It posts your kitchen and marketing team a Slack summary of what is still outstanding, so nothing slips through before launch day.
- Every new recipe gets a launch checklist the moment the rotation is added
- Nutrition labels and allergen reviews are tracked so nothing launches incomplete
- Team sees exactly what is outstanding before launch day, not after
Built for meal prep producers · meal subscription businesses · kitchen operations · menu development teams
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.goprep.com/menusin a real browser with your saved login - no setup, no API keys. -
1
GoPrep - read the new menu rotation
WebRun opens GoPrep to read the new menu rotation. - Open GoPrep and read the newly added or changed recipes in the rotation
- Capture each recipe's name, launch date, and whether it needs a new nutrition label
- Note any recipe reused from a past rotation versus a brand-new one
Done when Every new or changed recipe in the rotation is listed with its launch date.
-
2
Trello - build a launch checklist card per recipe
WebRun opens Trello to build a launch checklist card per recipe. - Create a launch checklist card for each new recipe on the Menu Launch board
- Add checklist items for nutrition label, photo, pricing, and allergen review
- Set the due date to 2 days before the rotation's launch date
Done when Every new recipe has a Trello checklist card with its launch tasks and due date.
-
3
Slack - notify the team what's left to do
WebRun opens Slack to notify the team what's left to do. - Post a summary of the new rotation to the kitchen and marketing channel
- List which checklist items are still incomplete for each recipe
- Link to the Trello board for the full checklist
Done when The team has a Slack summary of what still needs to be done before launch.
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
Does it publish the new menu to customers automatically?
No. WebRun only builds the internal launch checklist and tracks outstanding tasks. Publishing the menu live and any customer-facing announcement stay with your team.
What tasks does the checklist cover?
By default it adds nutrition label, photo, pricing, and allergen review items for each new recipe. You can add more checklist items to match your own launch process.
What happens to recipes reused from a past rotation?
It notes which recipes are reused rather than brand-new, so the checklist can skip tasks like a new nutrition label for a recipe that already has one.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.