Bear Brown
← All N8N workflows
AI & researchAgentChat TriggerDocument Default Data LoaderEmbeddings Open AiExecute Workflow Trigger

WooCommerce AI Chatbot Workflow for Post-Sales Support

Configured with Agent, Chat Trigger, Document Default Data Loader, Embeddings Open Ai, and additional nodes. Review the connections and setup before adapting this template.

Download workflow JSONView files on GitHub ↗26 nodes · MIT
Workflow preview
TriggerWhen chat messagereceivedChat TriggerData storeSimple MemoryMemory Buffer WindowIntegrationget_orderWoo Commerce ToolIntegrationget_ordersWoo Commerce ToolIntegrationget_userWoo Commerce ToolIntegrationCalculatorTool CalculatorTriggerWhen clicking ‘Testworkflow’Manual TriggerWeb / APICreate collectionHTTP RequestWeb / APIRefresh collectionHTTP RequestFiles / mediaGet folderGoogle DriveFiles / mediaDownload FilesGoogle DriveFiles / mediaDefault Data LoaderDocument Default Data Lo…TransformToken SplitterText Splitter Token Spli…Data storeQdrant Vector Store1Vector Store QdrantAI & modelsEmbeddings OpenAI1Embeddings Open AiData storeQdrant Vector StoreVector Store QdrantAI & modelsEmbeddings OpenAIEmbeddings Open AiAI & modelsOpenAI Chat ModelOpenAI Chat ModelAI & modelsToSTool Vector StoreSubworkflowget_trackingTool WorkflowTriggerWhen Executed byAnother WorkflowExecute Workflow TriggerAI & modelsPost-Sales AgentAgentMessaginghuman_assistenceTelegram ToolWeb / APIGet trackingHTTP RequestTransformSet tracking codeEdit FieldsAI & modelsGPT 4o-miniOpenAI Chat Model

Node categories in this workflow

  • Trigger
  • Data store
  • Integration
  • Web / API
  • Files / media
  • Transform
  • AI & models
  • Subworkflow
  • Messaging

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When chat message receivedTriggerChat TriggerSee node parameters
Simple MemoryData storeMemory Buffer WindowSee node parameters
get_orderIntegrationWoo Commerce Toolorder / get
get_ordersIntegrationWoo Commerce Toolorder / getAll
get_userIntegrationWoo Commerce Toolcustomer / getAll
CalculatorIntegrationTool CalculatorSee node parameters
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
Create collectionWeb / APIHTTP RequestPOST
Refresh collectionWeb / APIHTTP RequestPOST
Get folderFiles / mediaGoogle DrivefileFolder
Download FilesFiles / mediaGoogle Drivedownload
Default Data LoaderFiles / mediaDocument Default Data LoaderSee node parameters
Token SplitterTransformText Splitter Token SplitterSee node parameters
Qdrant Vector Store1Data storeVector Store QdrantSee node parameters
Embeddings OpenAI1AI & modelsEmbeddings Open AiSee node parameters
Qdrant Vector StoreData storeVector Store QdrantSee node parameters
Embeddings OpenAIAI & modelsEmbeddings Open AiSee node parameters
OpenAI Chat ModelAI & modelsOpenAI Chat ModelSee node parameters
ToSAI & modelsTool Vector StoreSee node parameters
get_trackingSubworkflowTool WorkflowSee node parameters
When Executed by Another WorkflowTriggerExecute Workflow TriggerSee node parameters
Post-Sales AgentAI & modelsAgentSee node parameters
human_assistenceMessagingTelegram ToolSee node parameters
Get trackingWeb / APIHTTP RequestSee node parameters
Set tracking codeTransformEdit FieldsSee node parameters
GPT 4o-miniAI & modelsOpenAI Chat ModelSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • googleDriveOAuth2Api
  • httpBasicAuth
  • httpHeaderAuth
  • openAiApi
  • qdrantApi
  • telegramApi
  • wooCommerceApi

Workflow notes

STEP 1

STEP 1

Create Qdrant Collection

Change:

  • QDRANTURL
  • COLLECTION
STEP 2

STEP 2

Documents vectorization with Qdrant and Google Drive

Change:

  • QDRANTURL
  • COLLECTION
STEP 3

STEP 3

  • Add your Telegram CHAT_ID in the "human_assistance" tool
STEP 4

STEP 4

The tracking code request is made through the most popular WooCommerce tracking plugin: "YITH WooCommerce Order & Shipment Tracking". The free version can be downloaded here

  • Create a new workflow and change URL in the node "Http Request" with your WooCommerce shop url
WooCommerce AI Chatbot Workflow for Post-Sales Support

WooCommerce AI Chatbot Workflow for Post-Sales Support

This WooCommerce-integrated chatbot is designed to transform post-sales customer support by combining automation and artificial intelligence to deliver fast, secure, and personalized assistance. By connecting directly to the WooCommerce database, the chatbot retrieves real-time order information—including shipping details and tracking numbers—after verifying the customer's identity through a strict email-based authentication system. This ensures maximum data security, preventing leaks of sensitive information.

Beyond order management, the chatbot answers frequently asked questions about return policies, delivery times, and terms of service using a vector database that provides accurate, context-aware responses. If a request is too complex, the system seamlessly escalates it to a human operator via Telegram, guaranteeing no customer query goes unresolved.

WooCommerce AI Chatbot Workflow for Post-Sales Support

WooCommerce AI Chatbot Workflow for Post-Sales Support

Purpose and structure

This folder contains the WooCommerce AI Chatbot Workflow for Post-Sales Support workflow. Its executable nodes use agent, chatTrigger, documentDefaultDataLoader, embeddingsOpenAi, executeWorkflowTrigger, googleDrive, httpRequest, lmChatOpenAi, manualTrigger, memoryBufferWindow, set, telegramTool, textSplitterTokenSplitter, toolCalculator, toolVectorStore, toolWorkflow, vectorStoreQdrant, wooCommerceTool. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When chat message received, When clicking ‘Test workflow’, When Executed by Another Workflow

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegramtool/1575_Telegramtool_Woocommercetool_Automate_Webhook.json MIT; preserve source notices.

More in AI & research

"Hey Siri, Ask Agent" workflow#️⃣Nostr #damus AI Powered Reporting + Gmail + Telegram(G) - Email Classification