Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Personal Data Extraction with Mistral NeMo

Personal Data Extraction with Mistral NeMo is a 7-node automation blueprint connecting Ollama API, Self-hosted LLM. Inspect its trigger, execution graph, branches, and implementation requirements.

Ollama APISelf-hosted LLM

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.

7

Nodes

7

Links

1

Run groups

Connected tools

2 integrations

  • Ollama API
  • Self-hosted LLM

Canvas controls

Fit wide systems, then zoom into any run group.

Personal Data Extraction with Mistral NeMo execution lanes1 run groups containing 7 workflow nodes and 7 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 OUTBasic LLM Chain. ai node, chainLlm. 3 incoming and 2 outgoing connections.STEP 02Basic LLM ChainAICHAINLLM3 IN / 2 OUTExtract JSON Output. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMEExtract JSON OutputTRANSFORMSET1 IN / 0 OUTOn Error. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMEOn ErrorINTEGRATIONNOOP1 IN / 0 OUTAuto-fixing Output Parser. ai node, outputParserAutofixing. 2 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Auto-fixing Output ParserAIOUTPUTPARSERAUTOFIXING2 IN / 1 OUTOllama Chat Model. ai node, lmChatOllama. 0 incoming and 2 outgoing connections.DEPENDENCY · DEPTH 1Ollama Chat ModelAILMCHATOLLAMA0 IN / 2 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 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.7 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

3 Execution Links4 Support Dependencies

  1. Start

    When chat message received

    Trigger

  2. Step 2

    Basic LLM Chain

    AI reasoning

  3. Outcome

    Extract JSON Output

    Transform

    On Error

    Integration

Attached dependencies

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

3 nodes

  • Auto-fixing Output Parser

    AI reasoning dependency

  • Structured Output Parser

    AI reasoning dependency

  • Ollama Chat Model

    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.

Create a build planReturn to the atlas