Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

AI-Powered Personal Shopper Workflow

AI-Powered Personal Shopper Workflow is a 21-node automation blueprint connecting OpenAI, WooCommerce, Google Drive. 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.

21

Nodes

19

Links

2

Run groups

Connected tools

4 integrations

  • OpenAI
  • WooCommerce
  • Google Drive
  • Qdrant

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Powered Personal Shopper Workflow execution lanes2 run groups containing 21 workflow nodes and 19 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 clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTHTTP Request. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02HTTP RequestINTEGRATIONHTTPREQUEST1 IN / 1 OUTGoogle Drive2. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 03Google Drive2GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTGoogle Drive1. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 04Google Drive1GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTQdrant Vector Store1. ai node, vectorStoreQdrant. 3 incoming and 0 outgoing connections.OUTCOMEQdrant Vector Store1AIVECTORSTOREQDRANT3 IN / 0 OUTEmbeddings OpenAI3. OpenAI node, embeddingsOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Embeddings OpenAI3OPENAIEMBEDDINGSOPENAI0 IN / 1 OUTDefault Data Loader2. ai node, documentDefaultDataLoader. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Default Data Loader2AIDOCUMENTDEFAULTDATALOAD1 IN / 1 OUTToken Splitter1. ai node, textSplitterTokenSplitter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Token Splitter1AITEXTSPLITTERTOKENSPLITT0 IN / 1 OUTWhen chat message received. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTWhen chat message receivedTRIGGERCHATTRIGGER0 IN / 1 OUTEdit Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Edit FieldsTRANSFORMSET1 IN / 1 OUTInformation Extractor. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 03Information ExtractorAIINFORMATIONEXTRACTOR2 IN / 1 OUTAI Agent. ai node, agent. 6 incoming and 0 outgoing connections.OUTCOMEAI AgentAIAGENT6 IN / 0 OUTOpenAI Chat Model2. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat Model2OPENAILMCHATOPENAI0 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTWindow Buffer Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Window Buffer MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTCalculator. ai node, toolCalculator. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1CalculatorAITOOLCALCULATOR0 IN / 1 OUTpersonal_shopper. integration node, wooCommerceTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1personal_shopperINTEGRATIONWOOCOMMERCETOOL0 IN / 1 OUTRAG. ai node, toolVectorStore. 2 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1RAGAITOOLVECTORSTORE2 IN / 1 OUTQdrant Vector Store. ai node, vectorStoreQdrant. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Qdrant Vector StoreAIVECTORSTOREQDRANT1 IN / 1 OUTOpenAI Chat Model1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2OpenAI Chat Model1OPENAILMCHATOPENAI0 IN / 1 OUTEmbeddings OpenAI. OpenAI node, embeddingsOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 3Embeddings OpenAIOPENAIEMBEDDINGSOPENAI0 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.21 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 clicking ‘Test workflow’

4 Execution Links3 Support Dependencies
  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    HTTP Request

    Integration

  3. Step 3

    Google Drive2

    Integration

  4. Step 4

    Google Drive1

    Integration

  5. Outcome

    Qdrant Vector Store1

    AI reasoning

Attached dependencies

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

3 nodes
  • Embeddings OpenAI3

    AI reasoning dependency

  • Default Data Loader2

    AI reasoning dependency

  • Token Splitter1

    AI reasoning dependency

02

Run Group

When chat message received

3 Execution Links9 Support Dependencies
  1. Start

    When chat message received

    Trigger

  2. Step 2

    Edit Fields

    Transform

  3. Step 3

    Information Extractor

    AI reasoning

  4. Outcome

    AI Agent

    AI reasoning

Attached dependencies

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

9 nodes
  • OpenAI Chat Model2

    AI reasoning dependency

  • OpenAI Chat Model

    AI reasoning dependency

  • Window Buffer Memory

    AI reasoning dependency

  • Calculator

    AI reasoning dependency

  • personal_shopper

    Integration dependency

  • RAG

    AI reasoning dependency

  • Qdrant Vector Store

    AI reasoning dependency

  • OpenAI Chat Model1

    AI reasoning dependency

  • Embeddings OpenAI

    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.