HumationHuman + Automation
Back to Catalog

Prioritize Zendesk tickets with GPT-4 analysis and Slack alerts

PhilanthropEAK AutomationPhilanthropEAK Automation
433 views
2/3/2026
Event ManagementTriggerAutomationData ExtractionGoogle Calendar
Official Page

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:

  1. 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)

  2. 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

  3. 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

  4. 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

n8n Workflow: Prioritize Zendesk Tickets with GPT-4 Analysis and Slack Alerts

This n8n workflow automates the process of analyzing new Zendesk tickets using OpenAI's GPT model, determining their urgency, and sending alerts to Slack for high-priority cases. It helps support teams quickly identify and act on critical issues.

What it does

This workflow performs the following steps:

  1. Receives Zendesk Ticket Data: It is triggered by an incoming webhook, expecting data related to a new or updated Zendesk ticket.
  2. Analyzes Ticket with OpenAI: It sends the ticket subject and description to OpenAI (presumably GPT-4 based on the directory name, though the JSON doesn't explicitly state the model) for analysis. The AI's response is expected to include a priority assessment.
  3. Extracts Priority: It processes the OpenAI response to extract the determined priority level.
  4. Filters by Priority: It checks if the extracted priority is "High".
  5. Sends Slack Alert (High Priority): If the priority is "High", it sends a detailed alert message to a specified Slack channel, including the ticket subject, description, and a link to the Zendesk ticket.
  6. Updates Zendesk Ticket (High Priority): For "High" priority tickets, it also updates the corresponding Zendesk ticket to reflect the high priority.
  7. Responds to Webhook: It sends a response back to the triggering webhook, indicating the successful processing of the ticket.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Zendesk Account: With API access for creating/updating tickets.
  • OpenAI API Key: An API key for accessing the OpenAI GPT models.
  • Slack Account: With a Slack App or Bot configured to send messages to a channel.
  • Webhook Integration: A mechanism to send Zendesk ticket data to the n8n webhook (e.g., a Zendesk webhook trigger).

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON.
  2. Configure Credentials:
    • Zendesk Node (ID: 123): Configure your Zendesk API credentials.
    • OpenAI Node (ID: 1250): Configure your OpenAI API Key credential.
    • Slack Node (ID: 40): Configure your Slack API token or webhook URL.
  3. Configure Webhook Trigger (ID: 47):
    • Copy the "Webhook URL" from the "Webhook" node.
    • In Zendesk, set up a webhook or trigger to send ticket data to this URL whenever a new ticket is created or updated. Ensure the payload includes the ticket subject, description, and ID.
  4. Configure Slack Channel (ID: 40):
    • Edit the "Slack" node and specify the desired channel where alerts should be posted.
  5. Configure OpenAI Prompt (ID: 1250):
    • Review the prompt in the "OpenAI" node to ensure it aligns with how you want GPT to analyze tickets and determine priority. Adjust as needed.
  6. Activate the Workflow:
    • Once all credentials and configurations are set, activate the workflow in n8n.

Now, whenever a new ticket is created in Zendesk and triggers the webhook, n8n will process it, analyze its priority with AI, and alert your team on Slack for high-priority items, while also updating the Zendesk ticket itself.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942