Webhook and Zendesk 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 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

Eliminate the manual chaos of HR and legal document management. This workflow automates the transition from a raw document upload to a structured, audit-ready archive by combining UploadToURL for instant CDN hosting, Google Drive for long-term storage, and Airtable for status tracking and database management. 🎯 What This Workflow Does Transforms loose document scans into a structured corporate filing system: 📝 Captures Legal Assets - Receives signed contracts or IDs via mobile scan (binary) or remote URL. 🛡️ Duplicate Prevention - Checks Airtable first to ensure a contract isn't already filed for that specific Employee ID. ☁️ Instant CDN Hosting - UploadToURL hosts the document to provide a high-speed link for immediate HR review. 📁 Smart Folder Logic - Automatically navigates or creates a structured Google Drive path: HR/Contracts/{Year}/{Department}/{EmployeeName}/. 🗃️ Database Synchronization - Updates (or creates) an Airtable record to tick "Contract Received," logging both the Drive URL and the CDN backup. 📧 Automated Confirmation - Sends a professional HTML email to HR and the employee with access links and filing metadata. ✨ Key Features UploadToURL Integration**: Provides a redundant, accessible CDN link stored alongside your primary Drive storage for total data reliability. Auto-Nomenclature**: Renames files using a strict audit-ready format: {EmployeeID}{LastName}{Type}_{Date}.pdf. Intelligent Folder Creation**: Never manually create a folder again; the workflow builds the entire hierarchy on the fly. Audit Trail Generation**: Captures "Filed By," "Filed At," and unique "Upload IDs" for every document. Conflict Handling**: Built-in 409 Conflict logic prevents accidental overwrites or double-filing of critical legal papers. 💼 Perfect For HR Teams**: Managing onboarding documents and employment contracts at scale. Legal Departments**: Archiving NDAs, vendor agreements, and compliance certifications. Small Businesses**: Moving away from "loose files in folders" to a searchable, automated database. Remote Teams**: Enabling employees to "upload and forget" their paperwork via a simple link. 🔧 What You'll Need Required Integrations UploadToURL** - To host documents and provide public CDN backup links. n8n Community Node** - n8n-nodes-uploadtourl must be installed. Google Drive** - OAuth2 credentials for secure document storage. Airtable** - Personal Access Token to manage your employee/document database. Gmail / SMTP** - To send automated filing confirmations. Configuration Variables GDRIVE_ROOT_FOLDER_ID: The ID of your main HR folder in Google Drive. AIRTABLE_BASE_ID: Your specific Airtable base for HR/Legal tracking. 🚀 Quick Start Import Template - Copy the JSON and import it into your n8n workspace. Install Node - Ensure the UploadToURL community node is active. Set Credentials - Link your UploadToURL, Google Drive, Airtable, and Gmail accounts. Define Variables - Set your Root Folder ID and Airtable Base details in n8n variables. Test the Pipeline - Send a test POST with a sample PDF to the Webhook URL. Activate - Enable the workflow to begin hands-free archiving. 🎨 Customization Options Expiration Alerts**: Add a node to calculate 1-year expiry dates and set an automated reminder in Slack. OCR Processing**: Integrate an OCR step to read the content of scans and verify names automatically. Watermarking**: Add a "Confidential" or "Draft" watermark to documents before they are uploaded to the CDN. Multi-Base Routing**: Route documents to different Airtable bases depending on the "Department" field. 📈 Expected Results 100% Consistency** in file naming and folder structures across the entire organization. Zero manual data entry**—employee records and checkboxes update automatically. Audit-ready in minutes**: Every file has a timestamped trail and redundant storage links. Instant Accessibility**: HR can view documents via the CDN link before Drive permissions even propagate. 🏆 Use Cases High-Growth Onboarding A startup hiring 20 people a month can automate all contract filings, ensuring the "Contract Received" flag is always accurate for payroll. Compliance Audits When auditors ask for specific contracts, use the Airtable "Structured Filename" column to find and share the relevant Drive or CDN links in seconds. Field Service Scans Technicians in the field can upload signed site reports via a mobile app; the workflow handles the filing and notifies the office immediately. 💡 Pro Tips Folder IDs**: You can find your GDRIVE_ROOT_FOLDER_ID by looking at the last string in the URL when you are inside that folder in your browser. Structured JSON**: Use the returned auditTrail object to build a log of all uploads in a separate "Master Audit" spreadsheet. Employee IDs**: If no ID is provided, the workflow generates a temporary one using a timestamp to ensure the archive never breaks. Ready to secure your document pipeline? Import this template and connect UploadToURL to build a world-class archiving system in under 20 minutes. Need help with Airtable field mapping? The workflow includes detailed sticky notes explaining the exact field names required for the automation to run.

Who's it for Customer support teams, SaaS companies, and service businesses that need to quickly identify and respond to urgent customer issues. Perfect for organizations handling high ticket volumes where manual prioritization creates delays and missed critical issues. How it works This workflow automatically analyzes incoming Zendesk tickets using OpenAI's GPT-4 to determine urgency levels and routes high-priority issues to your team via Slack notifications. The system monitors new Zendesk tickets via webhook, extracts key information (subject, description, customer details), and sends this data to OpenAI for intelligent analysis. The AI considers factors like emotional language, business impact keywords, technical severity indicators, and customer context to assign an urgency score from 1-5. Based on the AI analysis, the workflow automatically updates the ticket priority in Zendesk, adds detailed reasoning as a private note, and sends formatted Slack notifications for high-priority issues (score 4+). The Slack alert includes ticket details, urgency reasoning, key indicators found, and direct links to the ticket for immediate action. How to set up Prerequisites: Zendesk account with API access OpenAI API key (GPT-4 access recommended) Slack workspace with webhook permissions n8n instance (cloud or self-hosted) Setup steps: Configure credentials in n8n: Add OpenAI API credential with your API key Add Zendesk API credential (email + API token) Add Slack API credential (bot token with chat:write permissions) Update Configuration Variables node: Set your Zendesk subdomain (e.g., "yourcompany" for yourcompany.zendesk.com) Configure Slack channel for urgent alerts (e.g., "#support-urgent") Adjust urgency threshold (1-5, default is 4) Set default assignee email for fallback scenarios Set up Zendesk webhook: Copy the webhook URL from the trigger node In Zendesk Admin, go to Settings > Extensions > Add target Create HTTP target with the copied URL and POST method Create a trigger for "Ticket is created" that sends to this target Test the workflow: Create a test ticket with urgent language ("system is down", "critical issue") Verify the AI analysis runs and priority is updated Check that Slack notifications appear for high-priority tickets Confirm ticket updates include AI reasoning in private notes Requirements Zendesk** account with API access and admin permissions for webhook setup OpenAI API key** with GPT-4 access (estimated cost: $0.01-0.05 per ticket analysis) Slack workspace** with bot creation permissions and access to notification channels n8n instance** (cloud subscription or self-hosted installation) How to customize the workflow Adjust AI analysis parameters: Modify the system prompt in the OpenAI node to focus on industry-specific urgency indicators Add custom keywords or phrases relevant to your business in the prompt Adjust the temperature setting (0.1-0.5) for more consistent vs creative analysis Configure priority mapping: Edit the Code node to change how urgency scores map to Zendesk priorities Add custom business logic based on customer tiers or product types Implement time-based urgency (e.g., higher priority during business hours) Enhance Slack notifications: Customize the Slack message blocks with additional fields (product, customer tier, SLA deadline) Add action buttons for common responses ("Acknowledge", "Escalate", "Assign to me") Route different urgency levels to different Slack channels Extend integrations: Add email notifications using the Email node for critical issues Integrate with PagerDuty or Opsgenie for after-hours escalation Connect to your CRM to enrich customer context before AI analysis Add Teams or Discord notifications as alternatives to Slack Advanced customizations: Implement machine learning feedback loops by tracking resolution times vs AI scores Add sentiment analysis as a separate factor in priority calculation Create daily/weekly summary reports of AI analysis accuracy Build approval workflows for certain priority changes before auto-updating

This workflow creates a Jira issue when a new ticket is created in Zendesk. Subsequent comments on the ticket in Zendesk are added as comments to the issue in Jira. Prerequisites Zendesk account and Zendesk credentials. Jira account and Jira credentials. Jira project to create issues in. How it works The workflow listens for new tickets in Zendesk. When a new ticket is created, the workflow creates a new issue in Jira. The Jira issue key is then saved in one of the ticket's fields (in setup we call this "Jira Issue Key"). The next time a comment is added to the ticket, the workflow retrieves the Jira issue key from the ticket's field and adds the comment to the issue in Jira. Setup This workflow requires that you set up a webhook in Zendesk. To do so, follow the steps below: In the workflow, open the On new Zendesk ticket node and copy the webhook URL. In Zendesk, navigate to Admin Center > Apps and integrations > Webhooks > Actions > Create Webhook. Add all the required details which can be retrieved from the On new Zendesk ticket node. The webhook URL gets added to the “Endpoint URL” field, and the “Request method” should match what is shown in n8n. Save the webhook. In Zendesk, navigate to Admin Center > Objects and rules > Business rules > Triggers > Add trigger. Give the trigger a name such as “New tickets”. Under “Conditions” in “Meet ALL of the following conditions”, add “Status is New”. Under “Actions”, select “Notify active webhook” and select the webhook you created previously. In the JSON body, add the following: { "id": "{{ticket.id}}", "comment": "{{ticket.latest_comment_html}}" } Save the Zendesk trigger. You will also need to set up a field in Zendesk to store the Jira issue key. To do so, follow the steps below: In Zendesk, navigate to Admin Center > Objects and rules > Tickets > Fields > Add field. Use the text field option and give the field a name such as “Jira Issue Key". Save the field. In n8n, open the Update ticket node and select the field you created in Zendesk.