Zendesk and Slack integration

This workflow creates an automated Product Intelligence Engine that continuously collects signals from multiple product sources and generates structured PRD updates using AI. It ingests conversations, feedback, support tickets, analytics, and design comments, standardizes them, analyzes them with an AI PRD Agent, and automatically updates a Google Doc with structured PRD recommendations. Instead of manually reviewing Slack threads, Zoom calls, Jira comments, support tickets, and customer forms, this workflow centralizes everything into one intelligent PRD analysis system. High-Level Architecture - The workflow runs in 4 layers: Signal Ingestion Layer Captures product signals from: • Slack (channel messages + app mentions) • Customer Form submissions • Zoom recordings (scheduled) • Jira comments (scheduled) • Zendesk tickets (scheduled) • Figma comments (file updates) • Platform analytics via webhook • (Extendable to Salesforce / HubSpot) Standardization Layer Each source passes through a Format Node that: • Extracts relevant text • Normalizes metadata • Adds timestamps • Labels source type All inputs are converted into a unified "product signal" object. Intelligence Layer (AI PRD Agent) All signals are merged into a single stream using a Merge node. The PRD Analysis Agent then: • Extracts feature requests • Detects scope changes • Identifies risks and constraints • Evaluates priority signals • Detects target user shifts • Generates structured PRD updates PRD Governance Layer - output in a Google Doc The structured AI output is appended to a Google Doc, which is fully traceable. This creates a living PRD that continuously evolves based on real product signals. Required Credentials (And How To Add Them): You will need to configure the following credentials in n8n: Slack Used for Slack Trigger. Steps: Create a Slack App at api.slack.com Enable: app_mentions:read channels:history chat:write (optional if you want replies) Install app to workspace Copy Bot OAuth Token In n8n → Create Slack API credential Paste token Reference - https://www.youtube.com/watch?v=qk5JH6ImK0I Zoom (OAuth2) Used to fetch recordings. Steps: Create an OAuth App in Zoom Marketplace Add the Redirect URL from n8n Copy Client ID + Secret Add Zoom OAuth2 credential in n8n Connect account Reference - https://www.youtube.com/watch?v=BC6O_3LYgac Google Docs (OAuth2) Used to update PRD document. Steps: Create Google Cloud Project Add Doc URl to n8n Replace the example Google Doc URL with your own PRD document. Reference - https://www.youtube.com/watch?v=iieEHvu93dc Jira (Cloud) Steps: Generate API token from Atlassian Create Jira Software Cloud credential Enter: Email API token Domain Reference - https://www.youtube.com/watch?v=T4z7lzqSZDY Zendesk Steps: Generate API token Add Zendesk credential Enter: Subdomain Email API token Figma Steps: Generate a personal access token in Figma Add Figma credentials with the team ID Paste token Platform Analytics Webhook Replace: <PLACEHOLDER_VALUE__your_analytics_api_endpoint> With your real analytics endpoint. You can: • Send Mixpanel exports • Send Amplitude exports • Or POST custom JSON What Makes This Powerful • Eliminates product signal silos • Creates AI-driven PRD governance • Ensures traceability of decisions • Enables continuous PRD evolution • Scales across teams

This workflow automates customer support across multiple channels (Email, Live Chat, WhatsApp, Slack, Discord) using AI-powered responses enhanced with Retrieval Augmented Generation (RAG) and your product documentation. It intelligently handles incoming queries, provides instant and context-aware answers, and escalates complex or negative-sentiment cases to your human support team. All interactions are logged and categorized for easy tracking and reporting. Key Features Omnichannel Support:** Handles customer queries from Email, Live Chat, WhatsApp, Slack, and Discord. AI-Powered Answers:** Uses RAG to generate accurate, context-aware responses based on your product documentation. Automatic Escalation:** Detects low-confidence or negative-sentiment cases and escalates them to your human support team. Conversation Logging:** Automatically logs and categorizes all conversations for future analysis. Weekly Reporting:** Sends automated weekly summaries and metrics to your support team. How It Works Trigger: The workflow starts when a new message is received on any supported channel. Normalization: Incoming messages are normalized into a common format for unified processing. Context Management: Conversation history is fetched and merged with the new query for better AI context. AI Response: The workflow uses RAG to generate a response, referencing your product documentation. Confidence & Sentiment Analysis: The response is scored for confidence and sentiment. Escalation Logic: If the response is low-confidence or negative, the workflow escalates the case to your support team and creates a ticket. Response Delivery: The answer (or escalation notice) is sent back to the customer on the original channel. Logging & Reporting: All interactions are logged, categorized, and included in weekly reports. Configuration Connect Your Channels: Set up triggers for each channel you want to support (Email, Webhook, WhatsApp, Slack, Discord). Add Your Documentation: Integrate your product documentation source (e.g., Google Docs, Notion, or a knowledge base) for the RAG model. Configure AI Model: Set your preferred AI provider and model (e.g., OpenAI, Azure OpenAI, etc.). Set Escalation Rules: Adjust confidence thresholds and escalation logic to fit your support workflow. Integrate Support Tools: Connect your ticketing system (e.g., Zendesk) and reporting tools (e.g., Google Sheets, Slack). Test the Workflow: Send test queries from each channel to ensure correct routing, AI responses, and escalation. Use Cases Provide instant, accurate answers to customer questions 24/7. Reduce manual workload for your support team by automating common queries. Ensure complex or sensitive cases are quickly escalated to human agents. Gain insights into support trends with automated logging and weekly reports. Requirements n8n version 2.0.2 or later Accounts and credentials for your chosen channels and AI provider Access to your product documentation in a supported format Notes Please review and customize the workflow to fit your company’s privacy and data handling policies. For best results, keep your product documentation up to date and well-structured.

Description This workflow is designed for B2B/SaaS teams who want to secure renewals before it’s too late. It runs every day, identifies all accounts whose licenses are up for renewal in J–30, enriches them with CRM, product usage and support data, computes an internal churn risk level, and then triggers the appropriate playbook: HIGH risk** → full escalation (tasks, alerts, emails) MEDIUM risk** → proactive follow-up by Customer Success LOW risk** → light renewal touchpoint / monitoring Everything is logged into a database table so that you can build dashboards, run analysis, or plug additional automations on top. How it works Daily detection (J–30 renewals) A scheduled trigger runs every morning and queries your database (Postgres / Supabase) to fetch all active subscriptions expiring in 30 days. Each row includes the account identifier, name, renewal date and basic commercial data. Data enrichment across tools For each account, the workflow calls several business systems to collect context: HubSpot → engagement history Salesforce → account profile and segment Pipedrive → deal activities and associated products Analytics API → product feature usage and activity trends Zendesk → recent support tickets and potential friction signals All of this is merged into a single, unified item. Churn scoring & routing An internal scoring step evaluates the risk for each account based on multiple signals (engagement, usage, support, timing). The workflow then categorizes each account into one of three risk levels: HIGH – strong churn signals → needs immediate attention MEDIUM – some warning signs → needs proactive follow-up LOW – looks healthy → light renewal reminder A Switch node routes each account to the relevant playbook. Automated playbooks 🔴 HIGH risk Create a Trello card on a dedicated “High-Risk Renewals” board/list Create a Jira ticket for the CS / AM team Send a Slack alert in a designated channel Send a detailed email to the CSM and/or account manager 🟠 MEDIUM risk Create a Trello card in a “Renewals – Follow-up” list Send a contextual email to the CSM to recommend a proactive check-in 🟢 LOW risk Send a soft renewal email / internal note to keep the account on the radar Logging & daily reporting For every processed account, the workflow prepares a structured log record (account, renewal date, risk level, basic context). A Postgres node is used to insert the data into a churn_logs table. At the end of each run, all processed accounts are aggregated and a daily summary email is sent (for example to the Customer Success leadership team), listing the renewals and their risk levels. Requirements Database A table named churn_logs (or equivalent) to store workflow decisions and history. Example fields: account_id, account_name, end_date, riskScore, riskLevel, playbook, trello_link, jira_link, timestamp. External APIs HubSpot (engagement data) Salesforce (account profile) Pipedrive (deals & products) Zendesk (support tickets) Optional: product analytics API for usage metrics Communication & task tools Gmail (emails to CSM / AM / summary recipients) Slack (alert channel for high-risk cases) Trello (task creation for CS follow-up) Jira (escalation tickets for high-risk renewals) Configuration variables Thresholds are configured in the Init config & thresholds node: days_before_renewal churn_threshold_high churn_threshold_medium These parameters let you adapt the detection window and risk sensitivity to your own business rules. Typical use cases Customer Success teams who want a daily churn watchlist without exporting spreadsheets. RevOps teams looking to standardize renewal playbooks across tools. SaaS companies who need to prioritize renewals based on real risk signals rather than gut feeling. Product-led organizations that want to combine usage data + CRM + support into one automated process. Tutorial video Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

📘 Description This workflow automates payment-related customer support escalation by validating reported issues against transaction data and coordinating all downstream actions in a controlled, auditable way. It is designed for support teams that need to quickly separate valid payment failures from false or incomplete reports—while maintaining consistent customer communication and timely human intervention. The workflow is triggered via a webhook whenever an external system reports a customer issue. Incoming data is normalized and cross-checked against Google Sheets, which acts as the single source of truth for transaction status, payment confirmation, and order creation. An AI escalation engine then applies strict, rule-based logic to determine whether the issue is confirmed, needs clarification, or not valid, without assuming or inventing missing information. For confirmed cases, the workflow runs parallel actions: it generates a concise escalation summary for human support, logs full context to Slack, creates a Zendesk ticket for traceable resolution, and sends a calm, customer-safe email acknowledging the issue. Transaction records are then updated to reflect confirmation status. Robust error handling ensures any workflow failure is immediately surfaced in Slack. ⚙️ What This Workflow Does (Step-by-Step) 📥 Webhook Intake Receives structured payment issue data from external systems. 🧾 Normalize Incoming Payload Prepares a consistent data structure for processing. 📊 Transaction Lookup (Google Sheets) Fetches payment and order details from the source of truth. 🧠 AI Escalation Decision Validates the issue and classifies it as confirmed, needs clarification, or invalid. 🚨 Notify Human Support Sends escalation email and logs detailed context to Slack. ✉️ Send Customer-Facing Email Delivers a calm, professional acknowledgement to the customer. 🎫 Create Zendesk Ticket Opens a support ticket for confirmed cases requiring manual action. 📝 Update Transaction Record Marks confirmation status in Google Sheets for auditability. ⚠️ Error Handling → Slack Alert Immediately alerts the team if any workflow step fails. 🧩 Prerequisites • Webhook access for incoming issues • Google Sheets OAuth2 (source of truth) • Azure OpenAI credentials • Gmail OAuth2 for email delivery • Slack API access • Zendesk API access 💡 Key Benefits ✔ Prevents false or premature escalations ✔ Uses Google Sheets as an authoritative data source ✔ Consistent, customer-safe communication ✔ Parallel handling for speed and clarity ✔ Full audit trail across Sheets, Slack, Email, and Zendesk ✔ Strong error monitoring and reliability 👥 Perfect For Customer support teams Payment and order operations SaaS and transaction-heavy platforms Businesses handling high-volume support escalations

Analyze and Explore your ZenDesk Support Requests using AI-Powered Knowledge Graph This template helps you create an interactive InfraNodus knowledge graph for your ZenDesk tickets using any search criteria (e.g. after a certain date, specific status, sender, keyword) that will automatically be sent to a selected Slack channel. Here's an example of the InfraNodus graph that shows the main topics and gaps in ZenDesk support tickets: You can use the workflow to: Get an instant overview of the main topics your customers are talking about Generate business and product ideas based on the blind spots identified using the InfraNodus AI See which topics correlate to the negative / positive sentiment understanding the weak and strong sides of your product and support Receive daily notifications on the main topics your customers are talking about via Slack / Telegram / Email and other channels Perform detailed search using a password-protected web form for tickets filtered by a certain date, status, tag, sender, keyword. Use the interactive graph to explore specific topics and concepts your customers are talking about — a great way to engage with their concerns in a non-linear way, bypassing the boring tabular interface Use the graph to explore the support requests by specific segments — e.g. status, priority, sentiment, tags, urgency. Use the graph generated as an AI expert available to your AI agents in other n8n workflows via InfraNodus GraphRAG. For instance, you could connect your knowledge base to the support tickets graph and let the agent discover possible solutions to your customers' most typical problems. See an sample template here. How it works You can start this workflow manually, with a daily / weekly trigger, or via a password-protected web form, where you can provide search requests. Once started, it will perform a ZenDesk tickets search with the default or your custom criteria. Then it will use the search results to generate an InfraNodus graph (or add the new data to an existing one), and — finally — use the InfraNodus AI endpoints to generate a topical summary and a product business idea based on the blind spots identified. The results are delivered a channel of your choice. Here's a description step by step: Start the workflow (manually or on schedule) Assign values to variables (search criteria, graph name) Perform ZenDesk support tickets search Convert the data received and submit it to InfraNodus to generate a knowledge graph Generate topical summary with InfraNodus Generate a business idea with InfraNodus (you can also change the setting to generate a question instead) Send a notification via Slack / Telegram / Email or back to the webform How to use You need an InfraNodus API account and key to use this workflow. You also need a ZenDesk account. It takes about 5 minutes to set everything up. Create an InfraNodus account. Get the API key at https://infranodus.com/api-access and create a Bearer authorization key for the InfraNodus HTTP nodes. Add the authorization key to all the InfraNodus HTTP nodes in the template (Steps 3, 5, and 6). Generate a ZenDesk authorization token following the instructions in n8n's ZenDesk node (Step 3). Optionally: connect your Slack or Telegram or Gmail account to receive automated notifications with the link to the graph, once the workflow is ready (it takes about 30 seconds to run). Run it with using the form to play around with the search criteria that works best for you (you can leave everything empty at first), then choose the parameters you like and activate the Daily Trigger node to receive executive summaries to a channel of your choice. Open the graph in InfraNodus and use our customer feedback analysis guide to explore the graph and generate new insights. Requirements An InfraNodus account and API key A ZenDesk API key (Optional) — a Slack / Telegram / Gmail connection for notifications FAQ What are the best use cases to try? I love to set the graph to deliver me a daily visual briefing of what's happening in my support portal. It shows me the main topics and gaps and generates product ideas based on them. Great to keep the pulse on the business. I also really like generating a graph for the past week manually, using the form, and then exploring the graph in InfraNodus directly using the customer feedback analysis workflow to: discover main topics my customers are talking about? understand the topics that have the most negative connotation for them (using the sentiment filter)? discover some support tickets that need more attention or that talk about the topics I'm personally interested in and engage with the client identify the gaps in your customers' discourse based on the blind spots — useful for generating ideas, see the graph below with a demo of how it works: Why use the graph and not just AI summary? AI summary will just give you generic results. You'll see what you already know. Using the graph helps you deconstruct the discourse and get a much more nuanced understanding of the main pain points and interests of your customers. The auto-generated InfraNodus summary and business ideas have a direct explainable connection to the discourse, so you can always see where they are coming from and maintain the focus on all the topics, rather than the most prominent ones. Additionally, having an interactive graph opens a possibility to explore your customers' concerns in a more engaging way, finding the topics and concepts that are relevant to your interests or to your agents' expertise, helping you find the conversations that you'd otherwise have missed. Is my customers' data safe? Absolutely. InfraNodus' terms of use and privacy policy state that the customers' data and text graphs are not used in AI training and are not offered to any third parties. Its underlying API system uses the Open API which explicitly states that data is not used for training either. So all the customers' data are private and safe. As an extra precaution, you can always delete the graphs after you analyzed them, in which case there is no trace of this data left on the servers. Customizing this workflow Check out the complete setup guide for this workflow at https://support.noduslabs.com/hc/en-us/articles/20447530961308-Zendesk-Tickets-Summarization-Sentiment-Analysis-and-Slack-Integration-with-n8n-and-InfraNodus For support with this template, please, contact https://support.noduslabs.com For more InfraNodus n8n workflows, please, see our creators page: https://n8n.io/creators/infranodus/ To learn more about InfraNodus, GraphRAG, and knowledge graph analysis: https://infranodus.com

(Retail) VIP Customer Escalation Flow This workflow automatically monitors new Zendesk support tickets, identifies VIP customers, generates AI-based ticket summaries, alerts available support agents on Slack and sends a consolidated email for non-VIP tickets. This workflow listens for new Zendesk tickets and checks whether the customer is a VIP.VIP tickets are prioritized using AI summaries and instant Slack alerts, while non-VIP tickets are grouped and sent as a single email notification to the support team. You get: Instant VIP ticket alerts on Slack** AI-generated issue summary and next steps** Automatic agent availability check** One clean email for all non-VIP tickets** Ticket tracking stored for reporting** Ideal for support teams who want to prioritize high-value customers without manual effort. Quick Start – Implementation Steps Connect your Zendesk account and enable the Zendesk Trigger. Add your OpenAI API key for ticket summarization. Connect your Slack workspace and select users/channels. Configure Airtable to store VIP ticket data (optional but recommended). Connect Gmail to send non-VIP ticket summary emails. Activate the workflow — automation starts immediately. What It Does This workflow automates VIP ticket handling and notifications: Detects new Zendesk support tickets. Checks if the ticket belongs to a VIP customer. Uses AI to summarize VIP ticket issues and suggest next steps. Saves VIP ticket data for tracking and audits. Finds active support agents on Slack. Sends direct Slack alerts to active agents or a fallback channel. Collects non-VIP tickets into a single list. Sends one summary email for all non-VIP tickets. This prevents alert fatigue while ensuring VIP customers get fast attention. Who’s It For This workflow is ideal for: Customer support teams Helpdesk managers SaaS and e-commerce businesses High-touch B2B support teams Operations teams handling VIP customers Anyone needing smarter ticket prioritization Requirements to Use This Workflow To run this workflow, you need: n8n instance** (cloud or self-hosted) Zendesk account** with API access OpenAI API key** Slack workspace** with bot permissions Gmail account** (or SMTP alternative) Airtable account** (optional, for logging) How It Works Ticket Trigger – Workflow starts when a new Zendesk ticket is created. VIP Check – Verifies whether the ticket contains a VIP tag. AI Summary – AI reads the ticket and generates a short summary and next steps. Save VIP Ticket – VIP tickets are stored for tracking and reporting. Agent Availability Check – Slack users are checked for online presence. Slack Alert – Sends alert to an active agent or team channel. Non-VIP Collection – Non-VIP tickets are grouped together. Email Notification – One summary email is sent to the support team. Setup Steps Import the workflow JSON into n8n. Configure Zendesk Trigger with OAuth. Add your OpenAI credentials. Map fields in the Airtable node (if used). Connect Slack API and select users/channels. Configure Gmail recipient and email format. Test with a sample VIP and non-VIP ticket. Activate the workflow. How To Customize Nodes Customize VIP Logic You can enhance VIP detection by: Adding spend-based logic Checking customer lifetime value Using CRM or database lookups Customize Slack Alerts You may add: Emojis or mentions (@here, @team) Ticket priority highlighting Direct Zendesk ticket links Customize Email Content You can: Add branding Include SLA warnings Add escalation notes Customize AI Output Adjust the AI prompt to: Change summary length Add tone (urgent, polite, technical) Include troubleshooting steps Add-Ons (Optional Enhancements) You can extend this workflow to: Auto-assign tickets to senior agents Add SLA breach detection Log VIP interactions to CRM Add sentiment analysis Create dashboards using Airtable or Google Sheets Trigger SMS or WhatsApp alerts Add priority-based routing (VIP / High / Normal) Use Case Examples 1\. VIP Customer Escalation Ensure top customers always get instant attention. 2\. Support Load Management Reduce Slack and email noise with grouped notifications. 3\. AI-Assisted Support Help agents understand issues faster with AI summaries. 4\. Audit & Reporting Track VIP issues and resolutions over time. Troubleshooting Guide | Issue | Possible Cause | Solution | |-----------------------|--------------------------|-----------------------------------| | No Slack alert | No active users | Check fallback channel | | AI summary missing | OpenAI key invalid | Reconnect OpenAI credentials | | Multiple emails sent | Aggregate node missing | Ensure aggregation is enabled | | VIP not detected | Tag mismatch | Check tag name and case | | Airtable error | Field mismatch | Match column names exactly | Need Expert Help? If you need help extending this workflow with advanced features like adding CRM integration, advanced VIP logic, dashboards or scaling this for production then our n8n automation experts at WeblineIndia can help you build reliable, enterprise-ready automations.