Create Zendesk tickets from Gmail and Slack with Google Sheets tracking
Description
Automatically convert Gmail emails and Slack messages into Zendesk support tickets with intelligent priority detection, comprehensive Google Sheets tracking, and real-time team notifications. Streamlines support workflows with zero manual ticket creation. π«π§
What This Template Does
- Monitors Gmail inbox for unread emails and Slack support channel for new messages. π₯
- Normalizes data from both sources with intelligent content processing and HTML cleanup. π§Ό
- Creates structured Zendesk tickets with proper subject lines, descriptions, and priority tagging. π«
- Generates comprehensive tracking logs in Google Sheets with clickable ticket URLs. π
- Sends formatted Slack notifications for successful ticket creation or error alerts. π’
Key Benefits
- Eliminates manual ticket creation with automated processing. β±οΈ
- Unified support workflow across Gmail and Slack channels. π
- Complete audit trail with Google Sheets tracking. π§Ύ
- Real-time team notifications with ticket details and direct links. π²
- Intelligent priority detection based on "urgent" keywords. π¨
- Error handling with detailed failure notifications. π‘οΈ
Features
- Gmail polling every minute for unread email detection. π§
- Real-time Slack message monitoring in designated support channel. π¬
- Smart data normalization with HTML tag removal and urgency detection. π§
- Automatic Zendesk ticket creation with priority-based tagging. π·οΈ
- Google Sheets logging with ticket URLs, timestamps, and metadata. π
- Formatted Slack notifications with emojis and clickable links. β¨
- Comprehensive error detection and team alerting system. π¨
Requirements
- n8n instance (cloud or self-hosted).
- Gmail OAuth2 credentials in n8n with inbox access permissions.
- Slack Bot API credentials with channels:history, chat:write, and webhook capabilities.
- Zendesk API credentials for ticket creation and management.
- Google Sheets OAuth2 credentials with spreadsheet write permissions.
- Designated Slack channel for support requests (e.g., "#post-ticket").
Target Audience
- Customer support teams automating multi-channel ticket creation. π§
- Help desk operations seeking unified request processing. π
- Small to medium businesses streamlining support workflows. π’
- IT support teams managing internal and external requests. π»
- Service organizations requiring comprehensive audit trails. π
- Remote teams needing automated workflow notifications. π
Step-by-Step Setup Instructions
- Connect Gmail, Slack, Zendesk, and Google Sheets credentials in n8n. π
- Configure Slack channel ID for support message monitoring (default: "#post-ticket"). π±
- Set up Google Sheets document for ticket tracking and logging. π
- Import the workflow and assign all required credentials to respective nodes. π¦
- Configure Zendesk subdomain in the "Format Sheet Data" node for proper ticket URLs. π
- Test with a sample email or Slack message to validate end-to-end automation. β
Create Zendesk Tickets from Gmail and Slack, with Google Sheets Tracking
This n8n workflow automates the creation of Zendesk support tickets from new emails in Gmail and new messages in Slack, while also maintaining a consolidated log of all created tickets in a Google Sheet. This ensures no customer request or internal issue goes unnoticed, providing a centralized system for tracking and managing support requests.
What it does
- Monitors Gmail: The workflow listens for new emails in a specified Gmail inbox.
- Monitors Slack: Simultaneously, it listens for new messages in a designated Slack channel.
- Processes Incoming Data: For both Gmail and Slack, it extracts relevant information such as the sender, subject/message, and content.
- Transforms Data (Code Node): A Code node normalizes the incoming data from both sources into a consistent format suitable for Zendesk and Google Sheets.
- Creates Zendesk Ticket: It creates a new ticket in Zendesk using the extracted and transformed information.
- Logs to Google Sheets: It adds a new row to a specified Google Sheet, recording details of the newly created Zendesk ticket.
- Conditional Routing (If Node): Although not explicitly connected in the provided JSON, a disconnected "If" node suggests potential for future conditional logic (e.g., routing based on content, sender, etc.).
- Merges Data (Merge Node): A disconnected "Merge" node suggests potential for combining data streams from different sources or at different stages of the workflow.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Account: A running instance of n8n.
- Gmail Account: With credentials configured in n8n to allow the
Gmail Triggernode to monitor emails. - Slack Account: With credentials configured in n8n to allow the
Slack Triggernode to monitor messages and theSlacknode to potentially send notifications. - Zendesk Account: With credentials configured in n8n to allow the
Zendesknode to create tickets. - Google Sheets Account: With credentials configured in n8n to allow the
Google Sheetsnode to write data. You will need a specific spreadsheet and sheet name for logging.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- For the
Gmail Triggernode, set up your Google OAuth2 credentials. - For the
Slack TriggerandSlacknodes, set up your Slack API Token credentials. - For the
Zendesknode, configure your Zendesk API Token or OAuth2 credentials. - For the
Google Sheetsnode, set up your Google OAuth2 credentials.
- For the
- Customize Nodes:
- Gmail Trigger: Specify the email address or query to monitor for new emails.
- Slack Trigger: Specify the Slack channel to monitor for new messages.
- Code: Review and adjust the JavaScript code within the
Codenode to correctly parse and format data from Gmail and Slack into the desired structure for Zendesk and Google Sheets. - Zendesk: Configure the ticket fields (e.g., subject, description, requester email) using expressions that reference the output of the
Codenode. - Google Sheets: Specify the Spreadsheet ID and Sheet Name where ticket details should be logged. Map the columns in your sheet to the data output from the
Codenode.
- Activate the Workflow: Once all credentials are set and nodes are configured, activate the workflow.
This workflow provides a robust foundation for centralizing your support request management. You can further enhance it by utilizing the disconnected If and Merge nodes for more complex routing, data aggregation, or conditional processing based on your specific needs.
Related Templates
AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp
This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The βvirtual executive team,β is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier π― Core Features π§βπΌ 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. π 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. π΅οΈββοΈ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. β° 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline β key traits for early-stage success. ποΈ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. π¬ WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. βοΈ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. π§© Integrations Required Gemini API β for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API β for business and competitor analysis SerpAPI β for market research and opportunity scouting Google OAuth β to connect Sheets, Calendar, and Gmail WhatsApp Business API β for message triggers and responses π Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. π§° Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startupβs needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you π‘ Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API
Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. Itβs designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this β€ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait 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) 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. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. 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