Back to Catalog

Smart Customer Support System with GPT-4o, Gmail, Slack & Drive Knowledge Base'

David OlusolaDavid Olusola
468 views
2/3/2026
Official Page

The AI Support Agent combines Gmail, Slack, and Google Drive into a seamless support workflow powered by GPT-4o and Pinecone.

🧠 Email Monitoring – New support emails are pulled from Gmail every minute. πŸ“€ Classification – AI categorizes emails (e.g., billing, support, spam, urgent). πŸ“š Knowledge-Based Replies – GPT-4o drafts personalized replies using your support documents synced from Google Drive and stored in Pinecone.

πŸ“© Automatic Response – The agent replies to the customer in the same Gmail thread. 🚨 Escalation Detection – If human support is needed, Slack is notified instantly. πŸ“Š Logging – Each interaction is logged in Google Sheets for tracking and analysis. πŸ” Live Sync – Any document added to your Google Drive folder is auto-loaded into the knowledge base for future AI responses. πŸ› οΈ Quick Setup Steps πŸ› οΈ Quick Setup Checklist

⏱ Time to Deploy: ~10–15 minutes πŸ”Œ 1. Connect Integrations βœ… Gmail (OAuth2) βœ… Google Drive (OAuth2) βœ… Google Sheets (OAuth2) βœ… OpenAI API Key βœ… Pinecone API Key βœ… Slack Webhook (for alerts)

πŸ—‚οΈ 2. Update Workflow IDs Replace the sample IDs in your nodes:

πŸ“ Google Drive Folder ID β†’ Where your KB lives πŸ“Š Google Sheet ID β†’ Where interactions are logged 🚨 Slack Webhook URL β†’ Where urgent alerts go πŸ”Ž Pinecone Index β†’ Your vector storage index

🎨 3. Customize Prompt & Tone Go to πŸ”§ β€œResponse Agent” Node Update the System Prompt to reflect your brand’s tone: e.g. β€œWe’re always here to help, and we reply fast.”

πŸ“‚ 4. Upload Your Docs Add .pdf, .txt, or .docx files to your synced Google Drive folder. The agent will auto-read and embed them into Pinecone for AI-powered replies.

▢️ 5. Run & Test Send a test email from another account βœ… Watch the reply come through Gmail βœ… Check Slack for urgent alert βœ… Confirm logging in Google Sheets βœ… Done!

Smart Customer Support System with GPT-4o, Gmail, Slack, and Drive Knowledge Base

This n8n workflow automates and enhances customer support by intelligently processing incoming emails, leveraging a knowledge base stored in Google Drive, and routing customer inquiries to the appropriate channels. It uses AI to classify emails, extract relevant information, and provide smart responses or actions.

What it does

This workflow streamlines customer support by:

  1. Monitoring Incoming Emails: Automatically triggers when new emails arrive in Gmail.
  2. Monitoring Google Drive for Knowledge Base Updates: Triggers when new files are added to a specified Google Drive folder, allowing for dynamic updates to the knowledge base.
  3. Loading and Processing Knowledge Base Documents: When new files are added to Google Drive, it loads the document content, splits it into manageable chunks, and creates embeddings using OpenAI.
  4. Storing Knowledge Base Embeddings: Stores these embeddings in Pinecone, creating a searchable vector store for AI queries.
  5. Classifying Incoming Emails: Uses an AI Text Classifier (powered by OpenAI) to determine the category or intent of incoming customer emails.
  6. Conditional Routing based on Classification: Routes emails based on their classification.
    • If classified as "Support":
      • An AI Agent (powered by OpenAI) processes the email query, potentially searching the Pinecone vector store (knowledge base) for answers.
      • It then performs an HTTP request, likely to a Slack channel or another internal system, to escalate or respond to the support query.
    • If classified as "Sales":
      • An AI Agent (powered by OpenAI) processes the email query, potentially searching the Pinecone vector store (knowledge base) for answers.
      • It then performs an HTTP request, likely to a CRM or sales team Slack channel, to handle the sales inquiry.
    • If classified as "Other":
      • An AI Agent (powered by OpenAI) processes the email query.
      • It then performs an HTTP request, likely to a general inbox or a different internal team, for manual review.
  7. Logging to Google Sheets: Records details of the processed emails and their classifications in a Google Sheet for tracking and analysis.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Gmail Account: Connected as a credential in n8n for the Gmail Trigger.
  • Google Drive Account: Connected as a credential in n8n for the Google Drive Trigger and Google Drive node.
  • OpenAI API Key: For the AI Agent, OpenAI Chat Model, Embeddings OpenAI, and Text Classifier nodes.
  • Pinecone Account: For the Pinecone Vector Store to manage your knowledge base embeddings.
  • Google Sheets Account: Connected as a credential in n8n for the Google Sheets node.
  • Slack Account / HTTP Endpoint: An HTTP endpoint or Slack webhook configured to receive messages from the workflow (for support, sales, and other inquiries).

Setup/Usage

  1. Import the Workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Gmail credential for the "Gmail Trigger" node.
    • Set up your Google Drive credential for the "Google Drive Trigger" and "Google Drive" nodes.
    • Set up your OpenAI API key credential for the "OpenAI Chat Model", "Embeddings OpenAI", "AI Agent", and "Text Classifier" nodes.
    • Set up your Pinecone credential for the "Pinecone Vector Store" node.
    • Set up your Google Sheets credential for the "Google Sheets" node.
    • Configure the HTTP Request node with the appropriate URL and authentication for your Slack webhook or other internal system.
  3. Configure Nodes:
    • Gmail Trigger: Specify the mailbox and any filters for incoming emails.
    • Google Drive Trigger: Specify the folder ID in Google Drive where your knowledge base documents will be stored.
    • Pinecone Vector Store: Configure your Pinecone index name and environment.
    • Text Classifier: Define the categories for email classification (e.g., "Support", "Sales", "Other") and provide example texts for each category to train the classifier.
    • AI Agent: Customize the agent's instructions and tools if needed.
    • HTTP Request: Adjust the payload and URL for your specific Slack channels or other endpoints for different email classifications.
    • Google Sheets: Specify the Spreadsheet ID and sheet name where you want to log the data.
  4. Activate the Workflow: Once all credentials and nodes are configured, activate the workflow.

The workflow will now automatically process new emails, update its knowledge base from Google Drive, classify inquiries using AI, and route them to the appropriate teams or systems, logging the details in Google Sheets.

Related Templates

Create, update, and get a person from Copper

This workflow allows you to create, update, and get a person from Copper. Copper node: This node will create a new person in Copper. Copper1 node: This node will update the information of the person that we created using the previous node. Copper2 node: This node will retrieve the information of the person that we created earlier.

Harshil AgrawalBy Harshil Agrawal
603

Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack

🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. πŸ‘₯ Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness β€” no custom code required. βš™οΈ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌀️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) πŸš€ Setup (quick) Open Set β†’ Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. πŸ›  Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.

nodaBy noda
52

Send severe weather alerts from Visual Crossing to Telegram

How it works This workflow automates the process of fetching weather forecasts for your home location, including severe weather alerts, and sends timely notifications. It uses the Visual Crossing API for detailed weather data and integrates with Telegram (or other messaging services) for messaging and alerts. Step-by-step In summary, the workflow runs every hour, grabs the current day's weather conditions for [your city/location of interest], and returns only those items that truly contain one or more weather alerts. πŸ“… Step 1: Hourly Trigger The workflow begins with the Hourly Trigger node, which is a scheduleTrigger. This node acts as the clock that initiates the entire process at regular hourly intervals. 🌀️ Step 2: Fetch Weather Data Immediately after the trigger, the workflow moves to the Meteo node, an httpRequest. This node makes an external API call to fetch weather data for your specified location. API Used: Visual Crossing Web Services Authentication: Uses your API key (key=[API KEY]) Response format: JSON πŸŒͺπŸŒ€ Step 3: Check for Severe Weather The JSON weather data output is analyzed, and if severe weather conditions or alerts are detected, the workflow sends the alert via your preferred communication channel(s). Optional You can replace the Telegram node with email, WhatsApp, SMS notifications, or add multiple notification nodes to receive severe weather alerts across all desired channels.

Razvan BaraBy Razvan Bara
32