Skip to Workflow Atlas
Document Processing PipelineIntermediate

Intelligent Document Processing with AI

Intelligent Document Processing with AI is a 35-node automation blueprint connecting Mistral Cloud, Qdrant. 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.

35

Nodes

38

Links

4

Run groups

Connected tools

2 integrations

  • Mistral Cloud
  • Qdrant

Canvas controls

Fit wide systems, then zoom into any run group.

Intelligent Document Processing with AI execution lanes4 run groups containing 32 workflow nodes and 27 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.Merge. decision node, merge. 0 incoming and 1 outgoing connections.STARTMergeDECISIONMERGE0 IN / 1 OUTSplit Out. transform node, splitOut. 0 incoming and 1 outgoing connections.STARTSplit OutTRANSFORMSPLITOUT0 IN / 1 OUTPrep For AI. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Prep For AITRANSFORMSET1 IN / 1 OUTDiscover. ai node, chainRetrievalQa. 3 incoming and 1 outgoing connections.STEP 02DiscoverAICHAINRETRIEVALQA3 IN / 1 OUTGet Doc Types. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Get Doc TypesTRANSFORMSET1 IN / 1 OUTAggregate. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 03AggregateTRANSFORMAGGREGATE1 IN / 1 OUTSplit Out Doc Types. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 04Split Out Doc TypesTRANSFORMSPLITOUT1 IN / 1 OUTGenerate. ai node, chainLlm. 2 incoming and 1 outgoing connections.STEP 04GenerateAICHAINLLM2 IN / 1 OUT2secs. integration node, wait. 1 incoming and 1 outgoing connections.STEP 052secsINTEGRATIONWAIT1 IN / 1 OUTFor Each Doc Type.... integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 06For Each Doc Type...INTEGRATIONSPLITINBATCHES2 IN / 1 OUTGet Generated Documents. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Get Generated DocumentsTRANSFORMSET1 IN / 1 OUTTo Binary. integration node, convertToFile. 1 incoming and 1 outgoing connections.STEP 08To BinaryINTEGRATIONCONVERTTOFILE1 IN / 1 OUTExport to Folder. integration node, readWriteFile. 1 incoming and 0 outgoing connections.OUTCOMEExport to FolderINTEGRATIONREADWRITEFILE1 IN / 0 OUTMistral Cloud Chat Model2. ai node, lmChatMistralCloud. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Mistral Cloud Chat Model2AILMCHATMISTRALCLOUD0 IN / 1 OUTVector Store Retriever. ai node, retrieverVectorStore. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Vector Store RetrieverAIRETRIEVERVECTORSTORE1 IN / 1 OUTMistral Cloud Chat Model3. ai node, lmChatMistralCloud. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Mistral Cloud Chat Model3AILMCHATMISTRALCLOUD0 IN / 1 OUTQdrant Vector Store1. ai node, vectorStoreQdrant. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Qdrant Vector Store1AIVECTORSTOREQDRANT1 IN / 1 OUTEmbeddings Mistral Cloud1. ai node, embeddingsMistralCloud. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 3Embeddings Mistral Cloud1AIEMBEDDINGSMISTRALCLOUD0 IN / 1 OUTLocal File Trigger. trigger node, localFileTrigger. 0 incoming and 1 outgoing connections.STARTLocal File TriggerTRIGGERLOCALFILETRIGGER0 IN / 1 OUTSettings. transform node, set. 1 incoming and 1 outgoing connections.STEP 02SettingsTRANSFORMSET1 IN / 1 OUTImport File. integration node, readWriteFile. 1 incoming and 1 outgoing connections.STEP 03Import FileINTEGRATIONREADWRITEFILE1 IN / 1 OUTGet FileType. decision node, switch. 1 incoming and 3 outgoing connections.STEP 04Get FileTypeDECISIONSWITCH1 IN / 3 OUTExtract from PDF. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 05Extract from PDFINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTExtract from DOCX. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 05Extract from DOCXINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTExtract from TEXT. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 05Extract from TEXTINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTPrep Incoming Doc. transform node, set. 3 incoming and 0 outgoing connections.OUTCOMEPrep Incoming DocTRANSFORMSET3 IN / 0 OUTMistral Cloud Chat Model1. ai node, lmChatMistralCloud. 0 incoming and 0 outgoing connections.CORE RUNTIMEMistral Cloud Chat Model1AILMCHATMISTRALCLOUD0 IN / 0 OUTEmbeddings Mistral Cloud. ai node, embeddingsMistralCloud. 0 incoming and 0 outgoing connections.CORE RUNTIMEEmbeddings Mistral CloudAIEMBEDDINGSMISTRALCLOUD0 IN / 0 OUTMistral Cloud Chat Model. ai node, lmChatMistralCloud. 0 incoming and 0 outgoing connections.CORE RUNTIMEMistral Cloud Chat ModelAILMCHATMISTRALCLOUD0 IN / 0 OUTItem List Output Parser. ai node, outputParserItemList. 0 incoming and 0 outgoing connections.CORE RUNTIMEItem List Output ParserAIOUTPUTPARSERITEMLIST0 IN / 0 OUTDefault Data Loader. ai node, documentDefaultDataLoader. 1 incoming and 0 outgoing connections.CORE RUNTIMEDefault Data LoaderAIDOCUMENTDEFAULTDATALOAD1 IN / 0 OUTRecursive Character Text Splitter. ai node, textSplitterRecursiveCharacterTextSplitter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Recursive Character Text …AITEXTSPLITTERRECURSIVECH0 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.Showing 32 of 35 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

Merge

12 Execution Links5 Support Dependencies
  1. Start

    Merge

    Decision

    Split Out

    Transform

  2. Step 2

    Prep For AI

    Transform

    Discover

    AI reasoning

  3. Step 3

    Get Doc Types

    Transform

    Aggregate

    Transform

  4. Step 4

    Split Out Doc Types

    Transform

    Generate

    AI reasoning

  5. Step 5

    2secs

    Integration

  6. Step 6

    For Each Doc Type...

    Integration

  7. Step 7

    Get Generated Documents

    Transform

  8. Step 8

    To Binary

    Integration

  9. Outcome

    Export to Folder

    Integration

Attached dependencies

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

5 nodes
  • Mistral Cloud Chat Model2

    AI reasoning dependency

  • Vector Store Retriever

    AI reasoning dependency

  • Mistral Cloud Chat Model3

    AI reasoning dependency

  • Qdrant Vector Store1

    AI reasoning dependency

  • Embeddings Mistral Cloud1

    AI reasoning dependency

02

Run Group

Local File Trigger

9 Execution Links
  1. Start

    Local File Trigger

    Trigger

  2. Step 2

    Settings

    Transform

  3. Step 3

    Import File

    Integration

  4. Step 4

    Get FileType

    Decision

  5. Step 5

    Extract from PDF

    Integration

    Extract from DOCX

    Integration

    Extract from TEXT

    Integration

  6. Outcome

    Prep Incoming Doc

    Transform

03

Run Group

Standalone nodes

0 Execution Links
  1. Core Runtime

    Mistral Cloud Chat Model1

    AI reasoning

    Embeddings Mistral Cloud

    AI reasoning

    Mistral Cloud Chat Model

    AI reasoning

    Item List Output Parser

    AI reasoning

04

Run Group

Default Data Loader

0 Execution Links1 Support Dependency
  1. Core Runtime

    Default Data Loader

    AI reasoning

Attached dependencies

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

1 node
  • Recursive Character Text Splitter

    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.