Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

AI-Driven Document Analysis & Response

AI-Driven Document Analysis & Response is a 35-node automation blueprint connecting Google Drive, OpenAI, 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

35

Links

3

Run groups

Connected tools

4 integrations

  • Google Drive
  • OpenAI
  • Qdrant
  • Telegram

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Driven Document Analysis & Response execution lanes3 run groups containing 32 workflow nodes and 32 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 OUTAI Agent. ai node, agent. 3 incoming and 2 outgoing connections.STEP 02AI AgentAIAGENT3 IN / 2 OUTUpdate Chat History. Google Docs node, googleDocs. 1 incoming and 0 outgoing connections.OUTCOMEUpdate Chat HistoryGOOGLE DOCSGOOGLEDOCS1 IN / 0 OUTRespond to User. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMERespond to UserTRANSFORMSET1 IN / 0 OUTGoogle Gemini Chat Model1. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google Gemini Chat Model1GOOGLE AILMCHATGOOGLEGEMINI0 IN / 1 OUTWindow Buffer Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Window Buffer MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTtext-embeddings-3-large1. OpenAI node, embeddingsOpenAi. 0 incoming and 0 outgoing connections.CORE RUNTIMEtext-embeddings-3-large1OPENAIEMBEDDINGSOPENAI0 IN / 0 OUTGoogle Drive. Google Drive node, googleDrive. 0 incoming and 0 outgoing connections.CORE RUNTIMEGoogle DriveGOOGLE DRIVEGOOGLEDRIVE0 IN / 0 OUTWhen clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTWebhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTGoogle Folder ID. transform node, set. 2 incoming and 1 outgoing connections.STEP 02Google Folder IDTRANSFORMSET2 IN / 1 OUTFind File Ids in Google Drive Folder. Google Drive node, googleDrive. 1 incoming and 3 outgoing connections.STEP 03Find File Ids in Google D…GOOGLE DRIVEGOOGLEDRIVE1 IN / 3 OUTQdrant Collection Name. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Qdrant Collection NameTRANSFORMSET1 IN / 1 OUTFile Id List. transform node, summarize. 1 incoming and 1 outgoing connections.STEP 04File Id ListTRANSFORMSUMMARIZE1 IN / 1 OUTMerge1. decision node, merge. 2 incoming and 1 outgoing connections.STEP 05Merge1DECISIONMERGE2 IN / 1 OUTConfirm Qdrant Delete Points. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 06Confirm Qdrant Delete Poi…TELEGRAMTELEGRAM1 IN / 1 OUTIf. decision node, if. 1 incoming and 2 outgoing connections.STEP 07IfDECISIONIF1 IN / 2 OUTDelete Qdrant Points by File ID. ai node, code. 2 incoming and 1 outgoing connections.STEP 08Delete Qdrant Points by F…AICODE2 IN / 1 OUTSend Declined Message. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 08Send Declined MessageTELEGRAMTELEGRAM1 IN / 0 OUTMerge2. decision node, merge. 2 incoming and 1 outgoing connections.STEP 09Merge2DECISIONMERGE2 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 10Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 1 OUTDownload File From Google Drive. Google Drive node, googleDrive. 1 incoming and 2 outgoing connections.STEP 11Download File From Google…GOOGLE DRIVEGOOGLEDRIVE1 IN / 2 OUTQdrant Vector Store. ai node, vectorStoreQdrant. 3 incoming and 1 outgoing connections.STEP 12Qdrant Vector StoreAIVECTORSTOREQDRANT3 IN / 1 OUTGet File Contents. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 13Get File ContentsINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 14MergeDECISIONMERGE2 IN / 1 OUTExtract Meta Data. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 15Extract Meta DataAIINFORMATIONEXTRACTOR2 IN / 1 OUTWait. integration node, wait. 1 incoming and 1 outgoing connections.OUTCOMEWaitINTEGRATIONWAIT1 IN / 1 OUTgpt-4o-mini1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1gpt-4o-mini1OPENAILMCHATOPENAI0 IN / 1 OUTtext-embeddings-3-large. OpenAI node, embeddingsOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1text-embeddings-3-largeOPENAIEMBEDDINGSOPENAI0 IN / 1 OUTData Loader. ai node, documentDefaultDataLoader. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Data LoaderAIDOCUMENTDEFAULTDATALOAD1 IN / 1 OUTGoogle Gemini Chat Model. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google Gemini Chat ModelGOOGLE AILMCHATGOOGLEGEMINI0 IN / 1 OUTToken Splitter. ai node, textSplitterTokenSplitter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Token SplitterAITEXTSPLITTERTOKENSPLITT0 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

When chat message received

3 Execution Links2 Support Dependencies
  1. Start

    When chat message received

    Trigger

  2. Step 2

    AI Agent

    AI reasoning

  3. Outcome

    Update Chat History

    Integration

    Respond to User

    Transform

Attached dependencies

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

2 nodes
  • Google Gemini Chat Model1

    AI reasoning dependency

  • Window Buffer Memory

    AI reasoning dependency

02

Run Group

Standalone nodes

0 Execution Links
  1. Core Runtime

    text-embeddings-3-large1

    AI reasoning

    Google Drive

    Integration

03

Run Group

When clicking ‘Test workflow’

22 Execution Links5 Support Dependencies
  1. Start

    When clicking ‘Test workflow’

    Trigger

    Webhook

    Trigger

  2. Step 2

    Google Folder ID

    Transform

  3. Step 3

    Find File Ids in Google Drive Folder

    Integration

  4. Step 4

    Qdrant Collection Name

    Transform

    File Id List

    Transform

  5. Step 5

    Merge1

    Decision

  6. Step 6

    Confirm Qdrant Delete Points

    Integration

  7. Step 7

    If

    Decision

  8. Step 8

    Delete Qdrant Points by File ID

    AI reasoning

    Send Declined Message

    Integration

  9. Step 9

    Merge2

    Decision

  10. Step 10

    Loop Over Items

    Integration

  11. Step 11

    Download File From Google Drive

    Integration

  12. Step 12

    Qdrant Vector Store

    AI reasoning

  13. Step 13

    Get File Contents

    Integration

  14. Step 14

    Merge

    Decision

  15. Step 15

    Extract Meta Data

    AI reasoning

  16. Outcome

    Wait

    Integration

Attached dependencies

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

5 nodes
  • Google Gemini Chat Model

    AI reasoning dependency

  • text-embeddings-3-large

    AI reasoning dependency

  • Data Loader

    AI reasoning dependency

  • Token Splitter

    AI reasoning dependency

  • gpt-4o-mini1

    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.