Back to Catalog

Automate multi-channel customer support with Gmail, Telegram, and GPT AI

RedOneRedOne
4441 views
2/3/2026
Official Page

Smart Customer Support AI Agent with Gmail and Telegram

Who is this for?

This workflow is perfect for:

  • Small to medium businesses looking to automate customer support
  • E-commerce stores handling order inquiries and customer questions
  • SaaS companies providing technical support to users
  • Service providers managing appointment bookings and general inquiries
  • Startups wanting to provide 24/7 customer service without hiring full-time staff
  • Agencies managing client communications across multiple channels

What problem is this workflow solving?

Customer support is essential but resource-intensive. Common challenges include:

  • Slow response times leading to frustrated customers
  • Repetitive questions consuming valuable staff time
  • Inconsistent responses across different support agents
  • Limited availability outside business hours
  • Scaling support costs as business grows
  • Context loss when customers switch between channels

This workflow eliminates these pain points by providing instant, consistent, and intelligent responses 24/7.

What this workflow does

Core Functionality

  1. Multi-Channel Monitoring: Simultaneously watches Gmail and Telegram for customer inquiries
  2. Intelligent Processing: Uses AI to understand customer intent and context
  3. Knowledge Base Integration: Accesses your company's FAQ and support information
  4. Contextual Responses: Provides personalized, helpful replies maintaining conversation history
  5. Smart Escalation: Automatically escalates complex issues to human agents
  6. Comprehensive Logging: Tracks all interactions for analytics and improvement

AI Agent Capabilities

  • Natural Language Understanding: Comprehends customer questions in plain English
  • Context Awareness: Remembers previous conversations with each customer
  • Knowledge Retrieval: Searches your knowledge base for accurate information
  • Response Generation: Creates professional, brand-appropriate responses
  • Escalation Decision: Identifies when human intervention is needed
  • Multi-Channel Support: Handles Gmail and Telegram with channel-specific formatting

Automation Features

  • Auto-Response: Replies to customers within seconds
  • Email Management: Marks processed emails as read
  • Conversation Threading: Maintains context in email threads and Telegram chats
  • Error Handling: Gracefully handles failures with admin notifications
  • Analytics Tracking: Logs interactions for performance monitoring

Setup

Prerequisites

  • Active Google Workspace or Gmail account
  • Telegram account for bot creation
  • OpenAI API access
  • Google Sheets access
  • n8n instance (cloud or self-hosted)

Step 1: Credential Setup

Gmail OAuth2 Configuration

  1. Go to Google Cloud Console
  2. Create new project or select existing one
  3. Enable Gmail API
  4. Create OAuth 2.0 credentials
  5. Add authorized redirect URIs for n8n
  6. In n8n: Settings → Credentials → Add Gmail OAuth2
  7. Enter Client ID and Client Secret
  8. Complete OAuth flow

Telegram Bot Setup

  1. Message @BotFather on Telegram
  2. Create new bot with /newbot command
  3. Choose bot name and username
  4. Copy the bot token
  5. In n8n: Settings → Credentials → Add Telegram
  6. Enter bot token
  7. Set webhook URL in bot settings

OpenAI API Configuration

  1. Sign up at OpenAI Platform
  2. Generate API key in API Keys section
  3. In n8n: Settings → Credentials → Add OpenAI
  4. Enter API key
  5. Choose appropriate model (gpt-4o-mini recommended)

Google Sheets Setup

  1. Use existing Google account from Gmail setup
  2. In n8n: Settings → Credentials → Add Google Sheets OAuth2
  3. Complete authorization flow

Step 2: Google Sheets Preparation

Create three Google Sheets in your Google Drive:

Knowledge Base Sheet

  • Sheet Name: "Knowledge Base"
  • Columns: ID, Category, Question/Topic, Answer/Response, Keywords, Last_Updated
  • Import sample data from the Knowledge Base example
  • Customize with your company's FAQs and policies

Escalation Tracker Sheet

  • Sheet Name: "Escalations"
  • Columns: Timestamp, Customer_Name, Customer_Contact, Inquiry_Summary, Escalation_Reason, Priority, Status, Assigned_To
  • This will be auto-populated by the AI agent

Interaction Log Sheet

  • Sheet Name: "Interaction Log"
  • Columns: Timestamp, Channel, Customer_Name, Customer_Contact, Inquiry_Subject, Customer_Message, AI_Response, Response_Time, Status
  • This tracks all customer interactions for analytics

Step 3: Workflow Configuration

Import Template

  1. Copy the workflow JSON from the template
  2. In n8n: Import workflow from JSON
  3. Replace placeholder Sheet IDs with your actual Google Sheet IDs

Update Sheet References

  1. Open each Google Sheets node
  2. Select your created sheets from the dropdown
  3. Verify column mappings match your sheet structure

Customize AI Prompts

  1. Edit the "Customer Support AI Agent" node
  2. Update system message with:
    • Your company name and description
    • Brand voice and tone guidelines
    • Specific policies and procedures
    • Escalation criteria

Configure Error Notifications (Optional)

  1. Set up Slack webhook or email notifications
  2. Update error notification node with your webhook URL
  3. Customize error message format

Step 4: Testing

Test Gmail Integration

  1. Send test email to your support Gmail account
  2. Check workflow execution in n8n
  3. Verify response is sent and email marked as read
  4. Check interaction logging in Google Sheets

Test Telegram Integration

  1. Send message to your Telegram bot
  2. Verify bot responds appropriately
  3. Test conversation memory with follow-up messages
  4. Check escalation functionality with complex request

Test Knowledge Base

  1. Ask questions covered in your knowledge base
  2. Verify AI retrieves and uses correct information
  3. Test with variations of the same question
  4. Ensure responses are consistent and helpful

How to customize this workflow to your needs

Brand Voice Customization

Update the AI system prompt to include:
- Your company's tone (formal, casual, friendly)
- Key phrases and terminology you use
- Brand personality traits
- Communication style preferences

Knowledge Base Expansion

  • Add industry-specific FAQs
  • Include product documentation
  • Add troubleshooting guides
  • Create category-specific responses

Escalation Rules

Customize when to escalate by modifying the AI agent instructions:

  • Billing disputes over $X amount
  • Technical issues requiring developer help
  • Angry or dissatisfied customers
  • Requests outside standard services
  • Legal or compliance questions

Additional Channels

Extend the workflow to support:

  • Slack: Add Slack triggers and response nodes
  • WhatsApp: Integrate WhatsApp Business API
  • Web Chat: Add webhook triggers for website chat
  • Discord: Connect Discord bot integration

Analytics Enhancement

  • Add sentiment analysis to customer messages
  • Implement customer satisfaction scoring
  • Create automated reporting dashboards
  • Set up alert thresholds for escalation rates

Integration Opportunities

  • CRM Integration: Connect to HubSpot, Salesforce, or Pipedrive
  • Ticketing System: Link to Zendesk, Freshdesk, or Jira Service Desk
  • E-commerce Platform: Integrate with Shopify, WooCommerce, or Magento
  • Calendar Booking: Connect to Calendly or Acuity for appointment scheduling

Advanced Features

  • Multi-language Support: Add translation capabilities
  • Voice Messages: Integrate speech-to-text for Telegram voice notes
  • Image Recognition: Process customer screenshots for technical support
  • Proactive Outreach: Send follow-up messages based on customer behavior

Workflow Maintenance

Daily Tasks

  • Review escalation queue
  • Monitor error notifications
  • Check response quality in interaction log

Weekly Reviews

  • Analyze customer interaction patterns
  • Update knowledge base with new common questions
  • Review escalation reasons and optimize AI prompts

Monthly Optimization

  • Export interaction data for detailed analysis
  • Calculate key metrics (response time, resolution rate, escalation rate)
  • Update AI model parameters based on performance
  • Expand knowledge base with seasonal or trending topics

Key Metrics to Track

  • Response Time: Average time from customer message to AI response
  • Resolution Rate: Percentage of inquiries resolved without escalation
  • Customer Satisfaction: Based on follow-up surveys or sentiment analysis
  • Escalation Rate: Percentage of conversations requiring human intervention
  • Channel Performance: Effectiveness of Gmail vs Telegram vs other channels
  • Knowledge Base Usage: Which topics are accessed most frequently
  • Peak Hours: When customers contact support most often

Troubleshooting

Common Issues

  • Gmail not triggering: Check OAuth permissions and API quotas
  • Telegram bot not responding: Verify bot token and webhook configuration
  • AI responses seem off: Review and update system prompts
  • Escalations not logging: Check Google Sheets permissions and column mapping
  • High escalation rate: Expand knowledge base and refine AI instructions

Performance Optimization

  • Monitor OpenAI API usage and costs
  • Adjust AI model temperature for response consistency
  • Optimize knowledge base for faster searches
  • Set appropriate conversation memory limits

This workflow provides a solid foundation for automated customer support that can be extensively customized to match your specific business needs and grow with your company.

Automate Multi-Channel Customer Support with Gmail, Telegram, and GPT AI

This n8n workflow automates customer support by integrating Gmail, Telegram, and a GPT-powered AI agent. It allows you to respond to customer inquiries from multiple channels using AI-generated responses, while also logging interactions and handling errors gracefully.

What it does

This workflow streamlines customer support by:

  1. Listening for new messages: It can be triggered by new emails in Gmail or new messages in a Telegram chat.
  2. Processing messages with AI: An AI agent, powered by an OpenAI Chat Model and equipped with memory, processes the incoming message.
  3. Generating responses: The AI agent formulates a relevant response based on the customer's query and the conversation history.
  4. Responding to the customer: The AI-generated response is sent back to the customer via their original channel (Gmail or Telegram).
  5. Logging interactions: All interactions (incoming messages and AI responses) are logged into a Google Sheet for record-keeping and analysis.
  6. Handling errors: If any part of the main workflow fails, an error workflow is triggered to log the error, ensuring transparency and aiding debugging.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Gmail Account: Configured with n8n credentials to read and send emails.
  • Telegram Bot: A Telegram bot token and chat ID configured with n8n credentials to send and receive messages.
  • OpenAI API Key: For the OpenAI Chat Model used by the AI Agent.
  • Google Sheets Account: A Google Sheet set up to log customer interactions.
  • 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:
    • Gmail Trigger & Gmail Node: Set up your Google OAuth2 credentials for Gmail.
    • Telegram Trigger & Telegram Node: Configure your Telegram Bot API credentials.
    • Google Sheets Node: Set up your Google OAuth2 credentials for Google Sheets. Specify the spreadsheet name and sheet name where interactions should be logged.
    • OpenAI Chat Model: Provide your OpenAI API Key.
  3. Customize AI Agent:
    • The AI Agent node uses an OpenAI Chat Model and Simple Memory. You may need to adjust the AI agent's prompt or tools based on your specific customer support needs.
  4. Activate the workflow: Once all credentials are set and configurations are in place, activate the workflow.

This workflow is designed to be a robust starting point for automating multi-channel customer support with AI.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942