Give customers fast answers after they buy. The chat assistant checks WooCommerce for orders, sends tracking details, and explains store policies in clear language. Teams cut response time and keep private data safe with simple email checks.

A public chat webhook receives each message and keeps short chat memory for context. The flow looks up the customer by email in WooCommerce, then gets one order or many orders when needed. A secured WordPress call returns the shipment tracking code from the store plugin. Help articles live in Google Drive, are loaded and split into small parts, then turned into vectors with OpenAI embeddings and stored in Qdrant. The AI model searches those vectors to give accurate answers, and routes hard questions to a human in Telegram.

Setup is straight forward. Point the Qdrant nodes to your server, pick a collection name, connect Google Drive, and add your WooCommerce and WordPress credentials. Add your Telegram chat ID for human handoff. Stores see fewer tickets, quicker resolutions, and fewer repeat questions. This is ideal for shops with steady order volume that want reliable post sales replies without growing the support team.

• Chat webhook trigger starts the conversation and supports public access
• Short term memory keeps recent messages so the bot stays on topic
• WooCommerce tools fetch a single order, a list of orders, and customers by email
• WordPress request pulls the shipment tracking code from the store plugin with Basic Auth
• Google Drive integration selects a folder and downloads support files
• Document loader and token splitter prepare text for reliable search
• OpenAI embeddings build vectors and store them in Qdrant for fast retrieval
• OpenAI chat model composes clear answers with support from vector search
• Dedicated tool answers terms and shipping questions using your indexed policies
• Telegram tool escalates hard cases to a human with your chat ID

• Reduce manual work from 2 hours per day to 15 minutes by answering common post sales questions automatically
• Automate up to 70 percent of routine support like tracking and delivery status
• Improve answer accuracy by 30 percent by using real store data and vector search over your help docs
• Connect WooCommerce, WordPress, Google Drive, Qdrant, OpenAI and Telegram in one flow
• Handle 5 times more chat requests without adding new support agents
• Send tracking numbers instantly so customers do not open tickets

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with WooCommerce, WordPress, Google Drive, Qdrant, OpenAI and Telegram. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create WooCommerce credentials using your store URL, consumer key, and consumer secret. Open the WooCommerce nodes and select these credentials.
4. Set WordPress access for tracking. Create a Basic Auth user or an application password. In the WordPress request node, choose Basic Auth credentials and enter the username and password for your site.
5. Create an OpenAI API key in your OpenAI account. In n8n, add the OpenAI credential and select it on the embeddings and chat model nodes.
6. Connect Qdrant. If you use a hosted instance, add the API key or header in the Qdrant credentials. Update the QDRANTURL and COLLECTION fields in the Create collection and Refresh collection nodes.
7. Authorize Google Drive with OAuth in n8n. In the Google Drive nodes, pick the account, then choose the folder that holds your policies and FAQs.
8. Set up Telegram. Create a bot with BotFather to get the bot token. In n8n, add the Telegram credential and enter your chat ID in the human assistance tool.
9. Configure the vector build path. Check the Default Data Loader and Token Splitter nodes for file types and chunk size, then confirm the embeddings nodes point to your OpenAI credential.
10. Run the manual trigger path once to create or refresh the Qdrant collection. Verify points were added by checking the success output of the Qdrant nodes.
11. Open the chat trigger node and copy the public webhook URL. Send a test message and confirm you receive a response that references your documents and store data.
12. Troubleshoot common issues: 401 errors mean bad keys or permissions, missing tracking often means the plugin endpoint or order number is wrong, empty answers can mean the Google Drive folder is empty or the Qdrant collection name does not match.