Automate WhatsApp sales with DeepSeek AI, Google Sheets and Gmail notifications
Turn WhatsApp Into a 24/7 AI Sales Assistant — n8n + DeepSeek + Sheets + Gmail
⚠️ Self-Hosted n8n Only
Description
Turn your WhatsApp channel into a smart sales assistant! This workflow listens for inbound customer messages, looks up product data in Google Sheets, uses a DeepSeek Chat Model to answer in Saudi dialect, collects purchase details, and notifies your service rep only when the customer is ready to buy.
🔧 How to Install Community Nodes
Go to Settings → Community Nodes Click Install Node, then add:
n8n-nodes-evolution-api
Restart n8n if prompted.
🔄 What This Workflow Does
- Webhook Listener
Captures inbound WhatsApp messages (
MESSAGES_UPSERTvia Evolution API). - Filters
Ignores outbound (fromMe) and group (
@g.us) messages. - Data Extraction Pulls the customer’s message and phone number.
- AI Response Uses the DeepSeek Chat Model node to answer from your Google Sheets product list, greeting with “هلا وغلا” and speaking in Saudi dialect.
- Purchase Flow Prompts for name, phone, and delivery/pickup date.
- Notify Sales Sends an email via Gmail only when the customer requests to purchase.
- Context Memory (Optional) Stores conversation history in Postgres for coherent multi-turn chats.
📸 Visual Preview
🧩 Workflow
🛠️ Setup Instructions
-
Evolution API Webhook
- In Evolution API dashboard → Events → Webhook
- Enable only MESSAGES_UPSERT
- Set Webhook URL to:
https://your-n8n-domain/webhook/whatsAppListen
-
Google Sheets
- Create a spreadsheet (“You Conmanay Name Items”) with your product data [Item name, Item Model, Item Description, Item Components, Item Price, Item Availability, ...]
- Connect your Google Sheets credentials in n8n
-
DeepSeek Chat Model
- Configure your DeepSeek API credentials in the DeepSeek Chat Model node
- Ensure the system prompt matches your company’s tone and data columns
-
Gmail Notifications
- Add Gmail OAuth2 credentials to the Send a message in Gmail node
- Customize subject and email template if needed
-
Postgres Memory (Optional)
- Connect a Postgres instance in the Postgres Chat Memory node for session context
👥 Who Is This For?
- E-commerce teams automating first-touch customer replies
- Sales reps needing AI-driven chat support on WhatsApp
- Businesses using WhatsApp as a primary customer channel
🔐 Credentials Required
- Evolution API (webhook only)
- Google Sheets API
- DeepSeek API
- Gmail OAuth2
- Postgres (optional, for memory)
🏷 Tags
whatsapp bot, deepseek, google sheets, evolution api, gmail, postgres memory, ecommerce, sales automation, n8n template, no-code, ai, agent, ai agent
Automate AI-Powered WhatsApp Sales with DeepSeek AI, Google Sheets, and Gmail Notifications
This n8n workflow streamlines your sales process by leveraging AI to respond to WhatsApp messages, managing customer data in Google Sheets, and sending internal Gmail notifications. It acts as an intelligent assistant, ensuring timely and relevant communication with potential customers.
What it does
This workflow is designed to:
- Receive WhatsApp Messages: It listens for incoming WhatsApp messages via a webhook, acting as the entry point for new customer inquiries.
- Process with AI Agent: It utilizes an AI Agent (powered by DeepSeek Chat Model) to understand the message content and generate appropriate responses.
- Maintain Chat History: It leverages a Postgres Chat Memory to keep track of conversation history, allowing the AI to provide context-aware responses.
- Route AI Responses: It uses an "If" node to potentially route AI-generated responses based on certain conditions (though the specific conditions are not defined in the provided JSON, it indicates a branching logic capability).
- Perform No Operation: A "No Operation" node is present, which typically serves as a placeholder or a path for actions that are intentionally left blank or for future expansion.
- (Implicit - based on directory name): While not explicitly visible in the provided JSON, the directory name suggests further integration with Google Sheets for data management and Gmail for notifications. These steps would likely follow the AI processing and conditional routing.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance to import and execute the workflow.
- WhatsApp Webhook: A mechanism to send incoming WhatsApp messages to the n8n webhook URL. This often involves a third-party WhatsApp API provider (e.g., Twilio, MessageBird, etc.) that can forward messages to a custom webhook.
- DeepSeek API Key: An API key for the DeepSeek Chat Model to enable the AI Agent functionality.
- PostgreSQL Database: Access to a PostgreSQL database for the
Postgres Chat Memorynode to store and retrieve chat history. You will need the connection details (host, port, database name, user, password). - Google Sheets Account (Implicit): If integrating with Google Sheets for customer data.
- Gmail Account (Implicit): If sending Gmail notifications.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Webhook:
- Activate the
Webhooknode. - Copy the generated webhook URL.
- Configure your WhatsApp API provider to send incoming messages to this URL.
- Activate the
- Configure DeepSeek Chat Model:
- Open the
DeepSeek Chat Modelnode. - Provide your DeepSeek API key in the credentials section.
- Open the
- Configure Postgres Chat Memory:
- Open the
Postgres Chat Memorynode. - Set up your PostgreSQL database credentials (host, port, database, user, password) to allow the node to connect and store chat history.
- Open the
- Configure AI Agent:
- Review the
AI Agentnode settings. Ensure it's correctly configured to use theDeepSeek Chat ModelandPostgres Chat Memory.
- Review the
- Review "If" Node:
- Examine the
Ifnode. Currently, its conditions are not defined in the JSON. You will need to set up the conditions based on how you want to route messages (e.g., if the AI detects a specific intent, if a keyword is present, etc.).
- Examine the
- Add Google Sheets and Gmail Nodes (Optional):
- If you intend to use Google Sheets for data management and Gmail for notifications, add the respective n8n nodes after the
Ifnode (or within its branches). - Configure their credentials and operations (e.g., "Google Sheets: Add Row" for new leads, "Gmail: Send Email" for internal alerts).
- If you intend to use Google Sheets for data management and Gmail for notifications, add the respective n8n nodes after the
- Activate the Workflow: Once all configurations are complete, activate the workflow in n8n.
This workflow provides a robust foundation for automating WhatsApp sales interactions with intelligent AI responses and historical context.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte