Automate Gmail responses with GPT and human-in-the-loop verification
Try It Out!
This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email.
How it works
- Gmail Trigger monitors your inbox for new emails
- AI Analysis determines if a response is needed based on your criteria
- Draft Generation creates contextually appropriate replies using your business information
- Human Approval sends you the draft for review before sending
- Auto-Send replies automatically once approved
Setup
- Connect your Gmail account to the Gmail Trigger node
- Update the "Your Information" node with:
- Entity name and description
- Approval email address
- Resource guide (FAQs, policies, key info)
- Response guidelines (tone, style, formatting preferences)
- Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials
- Test with a sample email
Requirements
- n8n instance (self-hosted or cloud)
- Gmail account with API access
- LLM provider API key
Need Help?
Email Nick @ nick@tropicflare.com
Automate Gmail Responses with GPT and Human-in-the-Loop Verification
This n8n workflow automates the process of generating email responses using an OpenAI Chat Model and incorporates a human-in-the-loop verification step before sending. It helps streamline email communication by providing AI-powered drafts, while ensuring accuracy and appropriateness through manual review.
What it does
- Monitors Gmail: Continuously checks for new emails in your Gmail inbox.
- Extracts Information: Uses an Information Extractor (likely powered by an LLM) to parse key details from the incoming email.
- Generates AI Response: Leverages an OpenAI Chat Model to draft a suitable reply based on the extracted information.
- Prepares for Review: Organizes the original email content, extracted information, and the AI-generated draft into a structured format.
- Conditional Processing: Includes an
Ifnode, suggesting a conditional logic where responses might be handled differently based on certain criteria (e.g., urgency, sender, content). - Human-in-the-Loop (HITL) Verification: (Implied by the presence of Gmail node with HITL subcategory and the overall purpose) The workflow is designed to allow for human review of the AI-generated response before it is sent. This likely involves sending the draft to a human for approval or editing.
- Sends Gmail Reply: Once approved (or if the condition in the
Ifnode is met to bypass review), the workflow sends the final email reply via Gmail.
Prerequisites/Requirements
- n8n Instance: A running n8n instance (self-hosted or cloud).
- Gmail Account: A Google account with Gmail enabled, configured as a credential in n8n.
- OpenAI API Key: An OpenAI API key configured as a credential in n8n for the OpenAI Chat Model.
- Langchain Integration: The
@n8n/n8n-nodes-langchainpackage installed in your n8n instance (if not already built-in).
Setup/Usage
- Import the Workflow:
- Save the provided JSON content as a
.jsonfile. - In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and upload the saved
.jsonfile.
- Save the provided JSON content as a
- Configure Credentials:
- Locate the "Gmail Trigger" node and configure your Google OAuth2 credentials to allow n8n to access your Gmail account.
- Locate the "OpenAI Chat Model" node and configure your OpenAI API Key credential.
- Locate the "Gmail" node (for sending replies) and configure your Google OAuth2 credentials.
- Customize Nodes:
- Gmail Trigger: Adjust the "Label" or "Query" parameters if you want to monitor specific inboxes, labels, or filter emails.
- Information Extractor: Configure the schema or instructions for what information you want to extract from incoming emails.
- OpenAI Chat Model: Fine-tune the prompt to guide the AI in generating appropriate responses for your use case.
- If Node: Define the conditions under which the workflow should take different paths (e.g., send directly, require review, send to a different team).
- Code Node: Review and modify the JavaScript code to transform or prepare data as needed for your specific context.
- Edit Fields (Set) Node: Adjust which fields are being set or modified.
- Gmail (Send) Node: Customize the subject, body, and recipient logic for the outgoing email. This is where the human-in-the-loop approval mechanism would typically be integrated, perhaps by waiting for a webhook or a signal from an external system before sending.
- Activate the Workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
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.
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
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.