HumationHuman + Automation
Back to Catalog

Gmail to Zendesk ticket automation with Google Sheets logging

Rahul JoshiRahul Joshi
92 views
2/3/2026
SynchronizationHubSpotCustomer DataDatabaseCRM
Official Page

Description

Turn incoming Gmail messages into Zendesk tickets and keep a synchronized log in Google Sheets. Uses Gmail as the trigger, creates Zendesk tickets, and appends or updates a central sheet for tracking. Gain a clean, auditable pipeline from inbox to support queue. ✨

What This Template Does

  • Fetches new emails via Gmail Trigger. ✉️
  • Normalizes Gmail payload for consistent fields. 🧹
  • Creates a Zendesk ticket from the email content. 🎫
  • Formats data for Sheets and appends or updates a row. 📊
  • Executes helper sub-workflows and writes logs for traceability. 🔁🧾

Key Benefits

  • Converts emails to actionable support tickets automatically. ⚡
  • Maintains a single source of truth in Google Sheets. 📒
  • Reduces manual triage and data entry. 🕒
  • Improves accountability with structured logs. ✅

Features

  • Gmail Trigger for real-time intake. ⏱️
  • Normalize Gmail Data for consistent fields. 🧩
  • Create Zendesk Ticket (create: ticket). 🎟️
  • Format Sheet Data for clean columns. 🧱
  • Log to Google Sheets with appendOrUpdate. 🔄
  • Execute workflow (sub-workflow) steps for modularity. 🧩

Requirements

  • n8n instance (cloud or self-hosted). 🛠️
  • Gmail credentials configured in n8n (with read access to the monitored inbox). ✉️
  • Zendesk credentials (API token or OAuth) with permission to create tickets. 🔐
  • Google Sheets credentials with access to the target spreadsheet for append/update. 📊
  • Access to any sub-workflows referenced by the Execute workflow nodes. 🔁

Target Audience

  • IT support and helpdesk teams managing email-based requests. 🖥️
  • Ops teams needing auditable intake logs. 🧾
  • Agencies and service providers converting client emails to tickets. 🤝
  • Small teams standardizing email-to-ticket flows. 🧑‍💼

Step-by-Step Setup Instructions

  • Connect Gmail, Zendesk, and Google Sheets in n8n Credentials. 🔑
  • Set the Gmail Trigger to watch the desired label/inbox. 📨
  • Map Zendesk fields (description) from normalized Gmail data. 🧭
  • Point the Google Sheets node to your spreadsheet and confirm appendOrUpdate mode. 📄
  • Assign credentials to all nodes, including any Execute workflow steps. 🔁
  • Run once to test end-to-end; then activate the workflow. ✅

Gmail to Zendesk Ticket Automation with Google Sheets Logging

This n8n workflow automates the process of creating Zendesk tickets from incoming Gmail emails and logs the details of each created ticket into a Google Sheet. It streamlines customer support by ensuring that important emails are converted into trackable tickets and their information is systematically recorded.

What it does

  1. Monitors Gmail: Listens for new emails in a specified Gmail account.
  2. Processes Email Content: Extracts relevant information from the incoming email (e.g., sender, subject, body).
  3. Creates Zendesk Ticket: Uses the extracted email information to create a new ticket in Zendesk.
  4. Logs to Google Sheets: Records the details of the newly created Zendesk ticket (and potentially the original email information) into a designated Google Sheet for tracking and reporting.

Prerequisites/Requirements

  • n8n Account: A running n8n instance (cloud or self-hosted).
  • Gmail Account: An active Gmail account with appropriate permissions for n8n to monitor.
  • Zendesk Account: An active Zendesk account with API access enabled.
  • Google Sheets Account: Access to Google Sheets to create and update a spreadsheet.
  • n8n Credentials:
    • Google OAuth2 credentials configured in n8n for Gmail and Google Sheets.
    • Zendesk API Token/OAuth2 credentials configured in n8n.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON workflow definition.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three dots menu (...) in the top right and select "Import from JSON".
    • Paste the JSON content or upload the file.
  2. Configure Credentials:
    • Click on the "Gmail Trigger" node and select your Google OAuth2 credential.
    • Click on the "Zendesk" node and select your Zendesk credential.
    • Click on the "Google Sheets" node and select your Google OAuth2 credential.
  3. Configure Nodes:
    • Gmail Trigger: Specify the mailbox to monitor (e.g., "INBOX") and any filters if needed.
    • Code (if present): If there's a "Code" node, review its JavaScript to understand how email data is being transformed before being sent to Zendesk or Google Sheets. You might need to adjust it based on your specific data mapping requirements.
    • Zendesk: Configure the "Create Ticket" operation. Map the fields (e.g., subject, description, requester email) using expressions from the previous Gmail node's output.
    • Google Sheets: Configure the "Append Row" or "Add Row" operation. Specify the Spreadsheet ID and Sheet Name. Map the columns in your Google Sheet to the relevant data from the Zendesk ticket creation (e.g., Ticket ID, Subject, Requester, Status).
  4. Activate the Workflow: Once all nodes are configured and credentials are set, save and activate the workflow. It will start listening for new emails in your specified Gmail account.

Related Templates

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353

Synchronizing WooCommerce inventory and creating products with Google Gemini AI and BrowserAct

Synchronize WooCommerce Inventory & Create Products with Gemini AI & BrowserAct This sophisticated n8n template automates WooCommerce inventory management by scraping supplier data, updating existing products, and intelligently creating new ones with AI-formatted descriptions. This workflow is essential for e-commerce operators, dropshippers, and inventory managers who need to ensure their product pricing and stock levels are synchronized with multiple third-party suppliers, minimizing overselling and maximizing profit. --- Self-Hosted Only This Workflow uses a community contribution and is designed and tested for self-hosted n8n instances only. --- How it works The workflow is typically run by a Schedule Trigger (though a Manual Trigger is also shown) to check stock automatically. It reads a list of suppliers and their inventory page URLs from a central Google Sheet. The workflow loops through each supplier: A BrowserAct node scrapes the current stock and price data from the supplier's inventory page. A Code node parses this bulk data into individual product items. It then loops through each individual product found. The workflow checks WooCommerce to see if the product already exists based on its name. If the product exists: It proceeds to update the existing product's price and stock quantity. If the product DOES NOT exist: An If node checks if the missing product's category matches a predefined type (optional filtering). If it passes the filter, a second BrowserAct workflow scrapes detailed product attributes from a dedicated product page (e.g., DigiKey). An AI Agent (Gemini) transforms these attributes into a specific, styled HTML table for the product description. Finally, the product is created in WooCommerce with all scraped details and the AI-generated description. Error Handling: Multiple Slack nodes are configured to alert your team immediately if any scraping task fails or if the product update/creation process encounters an issue. Note: This workflow does not support image uploads for new products. To enable this functionality, you must modify both the n8n and BrowserAct workflows. --- Requirements BrowserAct API account for web scraping BrowserAct n8n Community Node -> (n8n Nodes BrowserAct) BrowserAct templates named “WooCommerce Inventory & Stock Synchronization” and “WooCommerce Product Data Reconciliation” Google Sheets credentials for the supplier list WooCommerce credentials for product management Google Gemini account for the AI Agent Slack credentials for error alerts --- Need Help? How to Find Your BrowseAct API Key & Workflow ID How to Connect n8n to Browseract How to Use & Customize BrowserAct Templates How to Use the BrowserAct N8N Community Node --- Workflow Guidance and Showcase STOP Overselling! Auto-Sync WooCommerce Inventory from ANY Supplier

Madame AI Team | KaiBy Madame AI Team | Kai
600

Ai website scraper & company intelligence

AI Website Scraper & Company Intelligence Description This workflow automates the process of transforming any website URL into a structured, intelligent company profile. It's triggered by a form, allowing a user to submit a website and choose between a "basic" or "deep" scrape. The workflow extracts key information (mission, services, contacts, SEO keywords), stores it in a structured Supabase database, and archives a full JSON backup to Google Drive. It also features a secondary AI agent that automatically finds and saves competitors for each company, building a rich, interconnected database of company intelligence. --- Quick Implementation Steps Import the Workflow: Import the provided JSON file into your n8n instance. Install Custom Community Node: You must install the community node from: https://www.npmjs.com/package/n8n-nodes-crawl-and-scrape FIRECRAWL N8N Documentation https://docs.firecrawl.dev/developer-guides/workflow-automation/n8n Install Additional Nodes: n8n-nodes-crawl-and-scrape and n8n-nodes-mcp fire crawl mcp . Set up Credentials: Create credentials in n8n for FIRE CRAWL API,Supabase, Mistral AI, and Google Drive. Configure API Key (CRITICAL): Open the Web Search tool node. Go to Parameters → Headers and replace the hardcoded Tavily AI API key with your own. Configure Supabase Nodes: Assign your Supabase credential to all Supabase nodes. Ensure table names (e.g., companies, competitors) match your schema. Configure Google Drive Nodes: Assign your Google Drive credential to the Google Drive2 and save to Google Drive1 nodes. Select the correct Folder ID. Activate Workflow: Turn on the workflow and open the Webhook URL in the “On form submission” node to access the form. --- What It Does Form Trigger Captures user input: “Website URL” and “Scraping Type” (basic or deep). Scraping Router A Switch node routes the flow: Deep Scraping → AI-based MCP Firecrawler agent. Basic Scraping → Crawlee node. Deep Scraping (Firecrawl AI Agent) Uses Firecrawl and Tavily Web Search. Extracts a detailed JSON profile: mission, services, contacts, SEO keywords, etc. Basic Scraping (Crawlee) Uses Crawl and Scrape node to collect raw text. A Mistral-based AI extractor structures the data into JSON. Data Storage Stores structured data in Supabase tables (companies, company_basicprofiles). Archives a full JSON backup to Google Drive. Automated Competitor Analysis Runs after a deep scrape. Uses Tavily web search to find competitors (e.g., from Crunchbase). Saves competitor data to Supabase, linked by company_id. --- Who's It For Sales & Marketing Teams: Enrich leads with deep company info. Market Researchers: Build structured, searchable company databases. B2B Data Providers: Automate company intelligence collection. Developers: Use as a base for RAG or enrichment pipelines. --- Requirements n8n instance (self-hosted or cloud) Supabase Account: With tables like companies, competitors, social_links, etc. Mistral AI API Key Google Drive Credentials Tavily AI API Key (Optional) Custom Nodes: n8n-nodes-crawl-and-scrape --- How It Works Flow Summary Form Trigger: Captures “Website URL” and “Scraping Type”. Switch Node: deep → MCP Firecrawler (AI Agent). basic → Crawl and Scrape node. Scraping & Extraction: Deep path: Firecrawler → JSON structure. Basic path: Crawlee → Mistral extractor → JSON. Storage: Save JSON to Supabase. Archive in Google Drive. Competitor Analysis (Deep Only): Finds competitors via Tavily. Saves to Supabase competitors table. End: Finishes with a No Operation node. --- How To Set Up Import workflow JSON. Install community nodes (especially n8n-nodes-crawl-and-scrape from npm). Configure credentials (Supabase, Mistral AI, Google Drive). Add your Tavily API key. Connect Supabase and Drive nodes properly. Fix disconnected “basic” path if needed. Activate workflow. Test via the webhook form URL. --- How To Customize Change LLMs: Swap Mistral for OpenAI or Claude. Edit Scraper Prompts: Modify system prompts in AI agent nodes. Change Extraction Schema: Update JSON Schema in extractor nodes. Fix Relational Tables: Add Items node before Supabase inserts for arrays (social links, keywords). Enhance Automation: Add email/slack notifications, or replace form trigger with a Google Sheets trigger. --- Add-ons Automated Trigger: Run on new sheet rows. Notifications: Email or Slack alerts after completion. RAG Integration: Use the Supabase database as a chatbot knowledge source. --- Use Case Examples Sales Lead Enrichment: Instantly get company + competitor data from a URL. Market Research: Collect and compare companies in a niche. B2B Database Creation: Build a proprietary company dataset. --- WORKFLOW IMAGE --- Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|-----------| | Form Trigger 404 | Workflow not active | Activate the workflow | | Web Search Tool fails | Missing Tavily API key | Replace the placeholder key | | FIRECRAWLER / find competitor fails | Missing MCP node | Install n8n-nodes-mcp | | Basic scrape does nothing | Switch node path disconnected | Reconnect “basic” output | | Supabase node error | Wrong table/column names | Match schema exactly | --- Need Help or More Workflows? Want to customize this workflow for your business or integrate it with your existing tools? Our team at Digital Biz Tech can tailor it precisely to your use case from automation logic to AI-powered enhancements. Contact: shilpa.raju@digitalbiz.tech For more such offerings, visit us: https://www.digitalbiz.tech ---

DIGITAL BIZ TECHBy DIGITAL BIZ TECH
923