receive schedule events and create meal plan and http request
Configured with HTTP Request, Schedule Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Transform
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Friday 8pm | Trigger | Schedule Trigger | See node parameters |
| Create Meal Plan | Web / API | HTTP Request | POST |
| When clicking "Test workflow" | Trigger | Manual Trigger | See node parameters |
| Get Recipes | Web / API | HTTP Request | See node parameters |
| Config | Transform | Edit Fields | See node parameters |
| Generate Random Items | Code | Code | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
httpHeaderAuth
Workflow notes
Trigger
Trigger
Set the trigger to run when you like
Update this Config
Update this Config
Set the base Url of your Mealie instance Set number of recipes to generate and number of days to offset the plan (0 will start today). Grab a category id from Mealie (or leave blank for all categories)
Get started
Get started
- Set up a credential for your Mealie API token
- Apply the credential to the 2 Http request nodes
- Set schedule trigger and desired config
Workflow logic
Workflow logic
- Get all recipes from Mealie (within category if supplied)
- Randomly pick out the number set in the config
- Create dinner meal plans for the upcoming days
receive schedule events and create meal plan and http request
receive schedule events and create meal plan and http request
Purpose and structure
This folder contains the receive schedule events and create meal plan and http request workflow. Its executable nodes use code, httpRequest, manualTrigger, scheduleTrigger, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Friday 8pm, When clicking "Test workflow"
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0651_Code_Schedule_Create_Webhook.json MIT; preserve source notices.