Automate email responses with OpenAI and Telegram approval for Gmail
Overview
An intelligent email automation workflow that revolutionizes how you handle email responses. This sophisticated system monitors your Gmail inbox, uses AI to determine which emails require replies, generates professional responses, and sends them only after your approval via Telegram. Perfect for busy professionals who want to maintain personalized communication while leveraging AI efficiency.
🌟 Key Features
Intelligent Email Analysis
- Smart Detection: Automatically identifies emails that genuinely need responses
- Context Understanding: Distinguishes between promotional content, newsletters, and actionable emails
- Priority Filtering: Focuses on emails with questions, requests, or time-sensitive matters
AI-Powered Response Generation
- Professional Tone: Maintains appropriate business communication standards
- Contextual Replies: Generates responses based on email content and context
- Structured Output: Creates properly formatted subject lines and email bodies
- Customizable Prompts: Easily adjust AI behavior to match your communication style
Human-in-the-Loop Approval
- Telegram Integration: Review and approve responses directly from your mobile device
- Visual Preview: See both original email and AI-generated response before sending
- Dual Approval System: Approve or reject with simple Telegram buttons
- Timeout Protection: Automatically expires after 5 minutes to prevent accidental sends
🔧 How It Works
Workflow Architecture
- Email Monitoring: Continuous Gmail inbox surveillance (every minute)
- Inbox Filtering: Processes only emails in your main inbox folder
- AI Analysis: Determines response necessity using advanced language models
- Response Generation: Creates professional, contextual replies when needed
- Telegram Notification: Sends preview to your Telegram for approval
- Conditional Sending: Executes email send only upon your explicit approval
Decision Logic
The AI evaluates emails based on:
- Question Detection: Identifies direct questions requiring answers
- Action Requests: Recognizes requests for information or tasks
- Urgency Assessment: Prioritizes time-sensitive communications
- Context Analysis: Considers sender, subject, and content relevance
🚀 Setup Requirements
Prerequisites
- Gmail Account: With OAuth2 authentication enabled
- OpenAI API Key: For AI language model access
- Telegram Bot: Personal bot token and chat ID
- N8N Instance: Cloud or self-hosted environment
Required Credentials
- Gmail OAuth2 credentials
- OpenAI API authentication
- Telegram bot token and chat configuration
📊 Use Cases
Business Applications
- Customer Support: Automated responses to common inquiries
- Sales Teams: Quick replies to prospect questions
- Account Management: Timely responses to client communications
- HR Operations: Efficient handling of employee inquiries
Personal Productivity
- Email Management: Reduce inbox overwhelm
- Professional Communication: Maintain consistent response quality
- Time Management: Focus on high-priority tasks while AI handles routine replies
- Mobile Workflow: Approve emails anywhere via Telegram
⚙️ Customization Options
AI Behavior Tuning
- Response Style: Adjust tone from formal to casual
- Content Filters: Modify email analysis criteria
- Response Length: Control reply brevity or detail level
- Language Patterns: Customize communication style
Workflow Modifications
- Polling Frequency: Adjust email checking intervals
- Approval Timeout: Modify decision time limits
- Multi-Account Support: Extend to multiple Gmail accounts
- Category Routing: Different handling for different email types
🔒 Security & Privacy
Data Protection
- Local Processing: All email analysis occurs within your N8N instance
- No Data Storage: Email content is not permanently stored
- Secure Authentication: OAuth2 and API key protection
- Encrypted Communication: Secure Telegram API integration
Access Control
- Personal Approval: You control every outgoing message
- Audit Trail: Complete workflow execution logging
- Fail-Safe Design: Defaults to no action if approval isn't received
📈 Performance & Reliability
Efficiency Metrics
- Processing Speed: Sub-second email analysis
- Accuracy: High-quality response generation
- Reliability: Robust error handling and retry mechanisms
- Scalability: Handles high email volumes efficiently
Resource Usage
- Lightweight Operation: Minimal server resource consumption
- API Optimization: Efficient OpenAI token usage
- Rate Limiting: Respects Gmail and Telegram API limits
💡 Best Practices
Optimization Tips
- Monitor AI Responses: Regularly review and refine AI prompts
- Approval Patterns: Establish consistent approval workflows
- Response Templates: Create reusable response patterns
- Performance Monitoring: Track workflow efficiency metrics
Common Configurations
- Business Hours: Limit processing to working hours
- VIP Senders: Priority handling for important contacts
- Subject Filters: Custom rules for specific email types
- Escalation Rules: Forward complex emails to human review
🏆 Benefits
Productivity Gains
- Time Savings: Reduce manual email composition time by 60-80%
- Consistency: Maintain professional communication standards
- Responsiveness: Faster reply times improve customer satisfaction
- Focus: Concentrate on high-value tasks while AI handles routine communications
Professional Advantages
- Always Available: Respond to emails even when busy
- Quality Assurance: AI ensures grammatically correct, professional responses
- Scalability: Handle increasing email volumes without proportional time investment
- Competitive Edge: Faster response times improve business relationships
Tags: Email Automation, AI Assistant, Gmail Integration, Telegram Bot, Workflow Automation, OpenAI, Business Productivity, Customer Service, Response Management, Professional Communication
Automate Email Responses with OpenAI and Telegram Approval for Gmail
This n8n workflow automates the process of generating email replies using OpenAI and sending them via Gmail, with a crucial human-in-the-loop approval step through Telegram. It helps you efficiently manage your inbox by drafting intelligent responses, while ensuring you maintain control over outgoing communications.
What it does
- Triggers on New Gmail Emails: The workflow starts whenever a new email is received in your configured Gmail account.
- Generates AI Response: It uses an OpenAI Chat Model to generate a draft reply based on the content of the incoming email.
- Parses AI Output: A Structured Output Parser extracts the relevant information (likely the drafted response) from the AI's output.
- Sends Approval Request to Telegram: The generated response, along with the original email context, is sent to a specified Telegram chat for review and approval.
- Waits for Telegram Approval: The workflow pauses, waiting for a "Yes" or "No" response from the Telegram chat.
- Conditional Action Based on Approval:
- If Approved (Yes): The workflow proceeds to send the AI-generated reply via Gmail.
- If Rejected (No): The workflow terminates without sending an email, effectively doing nothing.
Prerequisites/Requirements
- n8n Instance: A running n8n instance (self-hosted or cloud).
- Gmail Account: An active Gmail account with appropriate n8n credentials configured to read emails and send replies.
- OpenAI API Key: An OpenAI API key with access to the chat model.
- Telegram Bot Token: A Telegram Bot Token and the Chat ID of the recipient (where approval messages will be sent).
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Gmail Trigger & Gmail Node: Set up your Gmail OAuth2 credentials. Ensure the credentials have permissions to read emails and send emails.
- OpenAI Chat Model: Configure your OpenAI API Key credential.
- Telegram Node: Set up your Telegram Bot API credential. You will need your bot token and the chat ID where you want to receive approval requests.
- Activate the Workflow: Once all credentials are set and nodes are configured, activate the workflow.
- Review and Approve: When a new email arrives in your Gmail, a draft response will be sent to your Telegram chat. You can then approve or reject it directly from Telegram.
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.
By Ranjan DailataGenerate 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
By Daniel NkenchoAutomate 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.
By Le Nguyen