The flow
Starts it 1Logic 6Service 7
The steps in the order they run, from what starts it.
- 1Weekly Schedule TriggerSchedule triggerStarts it
- 2Generate Upcoming WeekCodeLogic
- 3Generate Random Meal PlanHttp RequestService
- 4Fetch Current Week Meal PlansHttp RequestService
- 5Prepare Meal Plan Email DataCodeLogic
- 6Send Meal Plan EmailGmailService
- 7Normalize User ResponseCodeLogic
- 8Check for RemovalsIfLogic
- 9Fetch Recipe By SlugHttp RequestService
- 10Split Removals ArraySplit OutLogic
- 11Create Shopping List in MealieHttp RequestService
- 12Delete Random Meal PlanHttp RequestService
- 13Normalize Recipe DataCodeLogic
- 14Add Ingredients To Shopping ListHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 14, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Gmail
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 14 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 14 steps before you point it at anything that matters.