Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Weekly Meal Plan Generator

Weekly Meal Plan Generator is a 6-node automation blueprint connecting Recipe API. Inspect its trigger, execution graph, branches, and implementation requirements.

Recipe API

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

6

Nodes

5

Links

1

Run groups

Connected tools

1 integrations

  • Recipe API

Canvas controls

Fit wide systems, then zoom into any run group.

Weekly Meal Plan Generator execution lanes1 run groups containing 6 workflow nodes and 5 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Friday 8pm. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTFriday 8pmTRIGGERSCHEDULETRIGGER0 IN / 1 OUTWhen clicking "Test workflow". trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking "Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTConfig. transform node, set. 2 incoming and 1 outgoing connections.STEP 02ConfigTRANSFORMSET2 IN / 1 OUTGet Recipes. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get RecipesINTEGRATIONHTTPREQUEST1 IN / 1 OUTGenerate Random Items. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Generate Random ItemsTRANSFORMCODE1 IN / 1 OUTCreate Meal Plan. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMECreate Meal PlanINTEGRATIONHTTPREQUEST1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.6 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Friday 8pm

5 Execution Links

  1. Start

    Friday 8pm

    Trigger

    When clicking "Test workflow"

    Trigger

  2. Step 2

    Config

    Transform

  3. Step 3

    Get Recipes

    Integration

  4. Step 4

    Generate Random Items

    Transform

  5. Outcome

    Create Meal Plan

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas