HumationHuman + Automation
Back to Catalog

Zendesk ticket escalation to ClickUp with Telegram alerts

Rahul JoshiRahul Joshi
88 views
2/3/2026
emailautomationdiscordattachmentsimap
Official Page

Description

This workflow automates Zendesk ticket escalation by creating ClickUp tasks for urgent cases and notifying the support team in Telegram. It ensures that high-priority tickets are instantly visible to the right team members, avoiding delays in resolution.

What This Template Does (Step-by-Step)

🟢 Trigger (Manual Test or Later Zendesk Trigger)

  • Currently uses a manual trigger (Execute Workflow) for testing.
  • In production, this would start whenever a pending Zendesk ticket appears.

🎫 Fetch Zendesk Tickets

  • Pulls all pending tickets assigned to a group.
  • Sorts them by status and date.

🧹 Select Latest Ticket

  • Sorts by created_at and keeps only the newest ticket.
  • Outputs: id, subject, description, requester_id, created_at.

📧 Fetch Requester Email

  • Retrieves requester details (name, email, timezone) from Zendesk Users API.

🔀 Merge Ticket & Requester Data

  • Combines both streams: ticket info + requester info.
  • Ensures the ClickUp task payload has everything it needs.

📝 Prepare ClickUp Task Payload

  • Builds a structured task:
  • Task Name: [Escalation] {Subject} (Ticket #ID)
  • Description: Ticket + requester details + escalation message
  • Priority: 3 (default, can be adjusted)
  • Tags: zendesk, escalation

📂 Create ClickUp Task

  • Pushes the structured task into ClickUp under the escalation list.
  • Assigns it to a predefined team member.

📨 Format Telegram Alert Message

  • Generates a concise but urgent message:
  • Ticket subject + ID
  • Requester name + email
  • Direct ClickUp link
  • Adds urgency formatting (🚨 Immediate Attention Required).

📢 Send Telegram Escalation Alert

  • Posts the alert into the chosen Telegram chat/team.
  • Ensures managers/stakeholders know instantly.

Prerequisites

  • Zendesk account + API credentials
  • ClickUp account + API credentials
  • Telegram bot token & chat ID
  • n8n instance (cloud or self-hosted)

Customization Ideas

⚡ Replace manual trigger with Zendesk “Ticket Created” trigger. 🎯 Add SLA-based conditions (e.g., escalate only if response > 4 hrs). 📊 Auto-assign ClickUp tasks by ticket category. 🔔 Add Slack/Email notification along with Telegram. 📂 Store escalation logs into Notion or Google Sheets.

Key Benefits

✅ Zero delay in handling critical tickets ✅ Automatically creates ClickUp task + Telegram alert ✅ Reduces manual handoff between support → escalation team ✅ Keeps everyone aligned in real-time

Perfect For

🎯 Support teams needing fast escalations 📈 SaaS companies managing large ticket volumes 🚀 Agencies ensuring VIP clients never wait

Zendesk Ticket Escalation to ClickUp with Telegram Alerts

This n8n workflow automates the process of escalating Zendesk tickets to ClickUp tasks and sending real-time notifications via Telegram. It streamlines the communication and task management for critical Zendesk tickets, ensuring that urgent issues are promptly addressed by the relevant teams in ClickUp and that stakeholders are kept informed.

What it does

This workflow performs the following key actions:

  1. Manual Trigger: Initiates the workflow upon a manual execution. This allows for on-demand escalation of tickets.
  2. Code Execution: Executes custom JavaScript code. This node is typically used for data manipulation, formatting, or conditional logic based on the input data before further processing.
  3. Zendesk Interaction: Interacts with Zendesk, likely to retrieve ticket details or update ticket status.
  4. ClickUp Task Creation: Creates or updates tasks within ClickUp, using information from the Zendesk ticket. This ensures that escalated issues are tracked and managed in the project management tool.
  5. Telegram Notification: Sends an alert or summary of the escalated ticket and created ClickUp task to a designated Telegram chat, ensuring immediate awareness for relevant team members.
  6. Merge Data: Combines data from different branches of the workflow. This could be used to consolidate information before sending a final notification or updating a system.
  7. Sticky Note: Provides a place for notes or comments within the workflow for documentation purposes.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Zendesk Account: With appropriate API access and credentials configured in n8n.
  • ClickUp Account: With API access and credentials configured in n8n.
  • Telegram Account & Bot: A Telegram bot token and the chat ID where alerts should be sent, configured as credentials in n8n.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Zendesk API credentials.
    • Set up your ClickUp API credentials.
    • Set up your Telegram Bot API credentials (Bot Token and Chat ID).
  3. Customize the Code Node: Adjust the JavaScript code in the "Code" node (ID: 834) to match your specific data transformation or filtering requirements for Zendesk ticket data.
  4. Configure Zendesk Node: Ensure the "Zendesk" node (ID: 123) is configured to fetch or update the correct ticket information.
  5. Configure ClickUp Node: Adjust the "ClickUp" node (ID: 129) to create tasks in the desired workspace, space, folder, and list, mapping the Zendesk ticket details to ClickUp task fields.
  6. Configure Telegram Node: Verify the "Telegram" node (ID: 49) is set to send messages to the correct chat ID with the desired message format.
  7. Activate the Workflow: Once configured, activate the workflow. You can then manually trigger it to test its functionality.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements 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) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | 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. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. 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

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31