Back to Catalog

WhatsApp group chat with your vector database β€” no Facebook Business required

Cecilia MukimaCecilia Mukima
1606 views
2/3/2026
Official Page

Enable smart, real-time answers in your WhatsApp groups using a custom webhook, Pinecone vector database, and no Facebook Business setup.

> 🟑 Note: This template uses a custom WhatsApp webhook. It does not use the official WhatsApp Business API.


πŸ‘₯ Who is this for?

This workflow is designed for individuals and teams who want to enable smart WhatsApp group automation β€” without going through Meta’s official WhatsApp Business API. Ideal for small businesses, internal teams, communities, and personal power users.


❓ What problem is this solving?

Setting up WhatsApp bots with intelligent responses often requires approval from Meta and a verified business account. This workflow removes those barriers by using a self-hosted webhook to handle incoming messages and respond using a document-trained AI via Pinecone.


βš™οΈ What this workflow does

  • Connects a regular WhatsApp number to a custom webhook
  • Adds the bot to any group chat (it stays silent unless mentioned)
  • Indexes documents from Google Drive into Pinecone
  • Responds with intelligent, context-aware answers from your custom knowledge base
  • Auto-updates its knowledge every minute as the document changes

πŸ› οΈ Setup

Step 1: Connect Google Drive

Step 2: Configure Pinecone

  1. Create an index in Pinecone
    • Dimension: 1536
  2. Select this index in both Pinecone nodes
  3. Click Test Workflow to ingest your document into Pinecone

Step 3: Get Access to the WhatsApp Webhook

Step 4: Test WhatsApp Integration

  • βœ… One-on-one test: Send a message from another number
  • πŸ‘₯ Group test: Add the bot to a group; it will only respond when tagged

🧩 How to customize this workflow

  • Modify the system prompt inside the AI agent node to control tone and behavior
  • Update the connected Google Doc to match your specific domain (e.g. FAQs, SOPs, product manuals)
  • Adjust the Pinecone sync frequency if you want updates more or less often

πŸ“š Use cases

  • Customer Support: Instant, intelligent replies in WhatsApp without live agents
  • Team Knowledge Bot: Tag the bot for quick access to SOPs and internal docs
  • Community Groups: Automate common questions while keeping noise low
  • Personal AI Assistant: A WhatsApp chatbot trained on your notes and files

πŸ“ Sticky Note Suggestion

πŸ’¬ What this template does:
> Enables an AI bot in your WhatsApp group that answers questions based on a Google Doc you provide. It uses a custom webhook, Google Drive, and Pinecone.

πŸ”§ Requirements:
> Google Drive account
> Pinecone account with an index (dimension 1536)
> Access to the custom WhatsApp webhook (see setup steps)

n8n AI Agent Workflow for Document-Based Q&A

This n8n workflow demonstrates a powerful AI agent that can answer questions based on documents stored in Google Drive. It leverages LangChain components to process documents, create embeddings, store them in a Pinecone vector database, and then use an OpenAI chat model to answer user queries.

This workflow is ideal for building a knowledge base Q&A system from your existing documents, enabling users to get answers without needing to manually search through files.

What it does

This workflow orchestrates several AI and data management tasks:

  1. Triggers on Google Drive Changes: It listens for new or updated files in a specified Google Drive folder.
  2. Loads Documents: When a change is detected, it loads the content of the relevant document using a default data loader.
  3. Splits Text: The document content is then split into smaller, manageable chunks using a Recursive Character Text Splitter to optimize for embedding and retrieval.
  4. Generates Embeddings: OpenAI Embeddings are generated for each text chunk, converting them into numerical representations.
  5. Stores in Vector Database: These embeddings are then stored in a Pinecone Vector Store, making them searchable for semantic similarity.
  6. Responds to Webhook Queries: A separate webhook endpoint allows users to send questions.
  7. Retrieves Relevant Information: The AI Agent uses the Pinecone Vector Store to find the most relevant document chunks based on the user's query.
  8. Generates Answers: An OpenAI Chat Model, augmented with a simple memory, synthesizes an answer using the retrieved information.
  9. Returns the Answer: The AI-generated answer is sent back as the webhook response.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Drive Account: With access to the folder containing your documents.
  • OpenAI API Key: For generating embeddings and chat model responses.
  • Pinecone Account: To set up and use a vector database for document embeddings.
  • LangChain Nodes: Ensure the @n8n/n8n-nodes-langchain package is installed in your n8n instance.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Google Drive Trigger: Set up your Google credentials for the Google Drive Trigger node to monitor your desired folder.
    • OpenAI Embeddings: Configure your OpenAI API key for the Embeddings OpenAI node.
    • OpenAI Chat Model: Configure your OpenAI API key for the OpenAI Chat Model node.
    • Pinecone Vector Store: Set up your Pinecone credentials (API Key and Environment) for the Pinecone Vector Store node.
  3. Activate the Workflow: Ensure the Google Drive Trigger is set to "Active" to start monitoring for document changes.
  4. Populate Pinecone: The first time the workflow runs (or when new documents are added to Google Drive), it will process your documents and populate the Pinecone vector store.
  5. Test the Webhook: Once the vector store is populated, you can send POST requests to the Webhook node's URL with your questions. The workflow will process the query and respond with an AI-generated answer.

This workflow provides a robust foundation for building intelligent Q&A systems directly from your document repositories.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required β€” one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- βš™οΈ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (β€œRepair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (β€œRepair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row β€” enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚑ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- πŸ› οΈ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use β€” Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➀ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

πŸ“Š Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. πŸš€πŸ“šπŸ’¬ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. πŸ“¦ Step 3: Logs release data into Google Sheets for record-keeping and analysis. πŸ“Š Step 4: Retrieves FAQ or documentation data from Notion. πŸ“š Step 5: Merges GitHub and Notion data to calculate documentation drift. πŸ” Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. πŸ”” Key Benefits βœ… Keeps SDK documentation aligned with product releases βœ… Prevents outdated information from reaching users βœ… Provides centralized release tracking in Google Sheets βœ… Sends real-time Slack alerts for overdue updates βœ… Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31