Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

AI-Driven Document Processing with Milvus

AI-Driven Document Processing with Milvus is a 13-node automation blueprint connecting Google Drive, Cohere, Milvus. Inspect its trigger, execution graph, branches, and implementation requirements.

Google DriveCohereMilvusOpenAI

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.

13

Nodes

11

Links

2

Run groups

Connected tools

4 integrations

  • Google Drive
  • Cohere
  • Milvus
  • OpenAI

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Driven Document Processing with Milvus execution lanes2 run groups containing 13 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.Watch New Files. Google Drive node, googleDriveTrigger. 0 incoming and 1 outgoing connections.STARTWatch New FilesGOOGLE DRIVEGOOGLEDRIVETRIGGER0 IN / 1 OUTDownload New. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 02Download NewGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTExtract from File. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 03Extract from FileINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTInsert into Milvus. ai node, vectorStoreMilvus. 3 incoming and 0 outgoing connections.OUTCOMEInsert into MilvusAIVECTORSTOREMILVUS3 IN / 0 OUTEmbeddings Cohere. ai node, embeddingsCohere. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Embeddings CohereAIEMBEDDINGSCOHERE0 IN / 1 OUTDefault Data Loader. ai node, documentDefaultDataLoader. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Default Data LoaderAIDOCUMENTDEFAULTDATALOAD1 IN / 1 OUTSet Chunks. ai node, textSplitterRecursiveCharacterTextSplitter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Set ChunksAITEXTSPLITTERRECURSIVECH0 IN / 1 OUTWhen chat message received. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTWhen chat message receivedTRIGGERCHATTRIGGER0 IN / 1 OUTRAG Agent. ai node, agent. 4 incoming and 0 outgoing connections.OUTCOMERAG AgentAIAGENT4 IN / 0 OUTOpenAI 4o. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI 4oOPENAILMCHATOPENAI0 IN / 1 OUTMemory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTRetrieve from Milvus. ai node, vectorStoreMilvus. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Retrieve from MilvusAIVECTORSTOREMILVUS1 IN / 1 OUTCohere embeddings. ai node, embeddingsCohere. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Cohere embeddingsAIEMBEDDINGSCOHERE0 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.13 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

Watch New Files

3 Execution Links3 Support Dependencies

  1. Start

    Watch New Files

    Trigger

  2. Step 2

    Download New

    Integration

  3. Step 3

    Extract from File

    Integration

  4. Outcome

    Insert into Milvus

    AI reasoning

Attached dependencies

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

3 nodes

  • Embeddings Cohere

    AI reasoning dependency

  • Default Data Loader

    AI reasoning dependency

  • Set Chunks

    AI reasoning dependency

02

Run Group

When chat message received

1 Execution Link4 Support Dependencies

  1. Start

    When chat message received

    Trigger

  2. Outcome

    RAG Agent

    AI reasoning

Attached dependencies

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

4 nodes

  • OpenAI 4o

    AI reasoning dependency

  • Memory

    AI reasoning dependency

  • Retrieve from Milvus

    AI reasoning dependency

  • Cohere embeddings

    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