Escalate urgent Zendesk tickets into ClickUp bugs with a Slack ping

By General Input

When a high or urgent Zendesk ticket lands, file a clean ClickUp bug task for engineering and post a quick heads-up in your triage Slack channel.

Integrations

  • Zendesk
  • ClickUp
  • Slack

Type

Agentic Task

Categories

  • Customer Support
  • Engineering

I want a customer-support escalation workflow that turns urgent Zendesk tickets into engineering-ready ClickUp bug tasks and pings my team on Slack.

Trigger: a Zendesk outgoing webhook that fires when a ticket is created with high or urgent priority, or when a ticket gets tagged or updated to high or urgent priority. The webhook payload includes the ticket ID.

When the workflow fires, the agent should:

1. Pull the full ticket context. Call Zendesk Show Ticket with the ticket ID to get the subject, requester, organization, priority, tags, and status. Then call Zendesk List Ticket Comments for the same ticket to get the full conversation history (public replies and internal notes).

2. Check for duplicates before filing. Call ClickUp Get Tasks on the configured engineering bug List (filter to open statuses) and scan the recent task names and descriptions for anything that looks like the same underlying issue (same error message, same feature area, same affected account). If a likely-duplicate open task already exists, skip the rest of the workflow and stop. Do not create another task and do not Slack the channel.

3. Write a clean engineering-style bug task. Compose the task description with these sections in this order: Problem statement (one or two sentences), What the customer expected, What actually happened, Steps to reproduce (only if reasonably inferable from the ticket; otherwise say "Repro steps not provided, follow up with reporter"), Customer impact (severity, blocking vs degraded, any revenue or churn signal), and Affected accounts (org name, plan, requester email). Include the full Zendesk ticket URL at the bottom of the description so engineers can jump back to the source.

4. File the task. Call ClickUp Create Task in the configured engineering bug List. Map Zendesk priority to ClickUp priority as follows: urgent -> 1 (Urgent), high -> 2 (High), normal -> 3 (Normal), low -> 4 (Low). Set the task name to a short, scannable title derived from the Zendesk subject. Leave the assignee unset unless an on-call engineer is configured.

5. Ping engineering on Slack. Call Slack Send a Message in the configured eng-triage channel. The message should be short: one-line summary of the bug, the Zendesk priority, the assignee (or "unassigned") if any, a link to the new ClickUp task, and a link to the original Zendesk ticket. Use Slack mrkdwn formatting.

Make the engineering bug List ID, the Slack channel, and the priority mapping configurable. Keep the Zendesk-to-ClickUp priority mapping and the bug task template easy for an ops person to edit later.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsPause marketing emails to escalated customers, then restore themWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsLook up any customer's email delivery history in one placeMailjet email delivery lookup console for support teams