Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

Local LLM Testing with LM Studio

Local LLM Testing with LM Studio is a 12-node automation blueprint connecting OpenAI, Google Sheets. Inspect its trigger, execution graph, branches, and implementation requirements.

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.

12

Nodes

11

Links

1

Run groups

Connected tools

2 integrations

  • OpenAI
  • Google Sheets

Canvas controls

Fit wide systems, then zoom into any run group.

Local LLM Testing with LM Studio execution lanes1 run groups containing 12 workflow nodes and 11 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.When chat message received. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTWhen chat message receivedTRIGGERCHATTRIGGER0 IN / 1 OUTGet Models. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Get ModelsINTEGRATIONHTTPREQUEST1 IN / 1 OUTExtract Model IDsto Run Separately. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 03Extract Model IDsto Run S…TRANSFORMSPLITOUT1 IN / 1 OUTCapture Start Time. integration node, dateTime. 1 incoming and 1 outgoing connections.STEP 04Capture Start TimeINTEGRATIONDATETIME1 IN / 1 OUTAdd System Prompt. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Add System PromptTRANSFORMSET1 IN / 1 OUTLLM Response Analysis. ai node, chainLlm. 2 incoming and 1 outgoing connections.STEP 06LLM Response AnalysisAICHAINLLM2 IN / 1 OUTCapture End Time. integration node, dateTime. 1 incoming and 1 outgoing connections.STEP 07Capture End TimeINTEGRATIONDATETIME1 IN / 1 OUTGet timeDifference. integration node, dateTime. 1 incoming and 1 outgoing connections.STEP 08Get timeDifferenceINTEGRATIONDATETIME1 IN / 1 OUTPrepare Data for Analysis. transform node, set. 1 incoming and 1 outgoing connections.STEP 09Prepare Data for AnalysisTRANSFORMSET1 IN / 1 OUTAnalyze LLM Response Metrics. transform node, code. 1 incoming and 1 outgoing connections.STEP 10Analyze LLM Response Metr…TRANSFORMCODE1 IN / 1 OUTSave Results to Google Sheets. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.OUTCOMESave Results to Google Sh…GOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTRun Model with Dunamic Inputs. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Run Model with Dunamic In…OPENAILMCHATOPENAI0 IN / 1 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.12 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

When chat message received

10 Execution Links1 Support Dependency
  1. Start

    When chat message received

    Trigger

  2. Step 2

    Get Models

    Integration

  3. Step 3

    Extract Model IDsto Run Separately

    Transform

  4. Step 4

    Capture Start Time

    Integration

  5. Step 5

    Add System Prompt

    Transform

  6. Step 6

    LLM Response Analysis

    AI reasoning

  7. Step 7

    Capture End Time

    Integration

  8. Step 8

    Get timeDifference

    Integration

  9. Step 9

    Prepare Data for Analysis

    Transform

  10. Step 10

    Analyze LLM Response Metrics

    Transform

  11. Outcome

    Save Results to Google Sheets

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

1 node
  • Run Model with Dunamic Inputs

    AI reasoning dependency

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.