Zendesk to ClickUp bug escalation with Slack alert

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.

Additional information

What does this prompt do?

Listens for new high or urgent priority tickets in Zendesk the moment they come in.
Reads the full ticket and the back-and-forth with the customer, then writes an engineering-ready bug task in ClickUp with the problem, what the customer expected, what actually happened, steps to reproduce if it can infer them, customer impact, and the accounts affected.
Posts a short summary in your engineering triage Slack channel with the assignee and links back to both the Zendesk ticket and the new ClickUp task.
Checks the engineering bug list first for an open task that looks like the same issue, so the same bug never gets filed twice.

What do I need to use this?

A Zendesk account with admin access so we can listen for new high and urgent priority tickets.
A ClickUp workspace and the specific list where your engineering team triages bugs.
A Slack workspace and the channel where your engineering triage team gets pinged.

How can I customize it?

Pick which Zendesk tags or priorities count as urgent enough to escalate, so you only get pinged on the ones that matter.
Change which ClickUp list new bug tasks land in, or adjust how Zendesk priority maps to ClickUp priority.
Swap the Slack channel, add an @mention for the on-call engineer, or change the format of the heads-up message.

Frequently asked questions

Will this fire on every new Zendesk ticket?

No. It only escalates when a Zendesk ticket is created or tagged with high or urgent priority. Lower priority tickets are ignored so your engineering channel stays signal-heavy.

What stops the same bug from being filed twice?

Before creating a new ClickUp task, the workflow checks your engineering bug list for an open task that looks like the same issue. If it finds one, it skips the new task so your queue does not fill up with duplicates.

Do I need a developer to set this up?

No. Once you connect your Zendesk, ClickUp, and Slack accounts and pick the list and channel you want to use, the workflow runs on its own.

Can I change the bug task template?

Yes. The default covers problem statement, expected behavior, actual behavior, steps to reproduce, customer impact, and affected accounts, but you can edit any section or add your own fields.

Will the ClickUp task and Slack message link back to the original Zendesk ticket?

Yes. Every ClickUp task description includes the Zendesk ticket URL, and the Slack message links to both the ClickUp task and the original Zendesk ticket so support can follow the engineering work.