TL;DR: The official Slack for Zendesk integration does four jobs well: trigger-driven ticket notifications into channels, ticket creation from Slack (four ways, including converting any message), side conversations as Slack threads, and approvals. What it can’t do from Slack: close tickets, edit fields, or assign to individuals — and attachments don’t travel.
Slack is where your company actually talks about customers; Zendesk is where the customer record lives. The official integration bridges them better than most people configure it to. Here’s the full feature set and the documented limits, per Zendesk’s docs.
The four jobs
1️⃣ Notifications, driven by real triggers. Ticket events post to channels of your choosing using Zendesk’s trigger system — meaning full condition logic (priority, group, org, tags), not a firehose. Agents can even add internal notes to the ticket from the notification thread. Underused and excellent.
2️⃣ Ticket creation from Slack, four ways: the /zendesk shortcut, a “Create a ticket” message action that converts any Slack message (description pre-filled), the app’s Home tab, and — the sleeper feature — @zendesk mentions in Slack Connect channels, which turns shared customer channels into a support intake without leaving Slack. Tickets created the first three ways get a created_from_slack tag for reporting.
3️⃣ Side conversations as Slack threads — loop engineering or finance into a ticket via a Slack thread that stays attached to the ticket as events, usable in trigger conditions. (Note: side conversations as a Zendesk feature carry their own plan gating — check your Suite tier.)
4️⃣ Approvals — approve/deny requests from Slack (one workspace only; comments made in Slack aren’t captured).
Setup lives in Admin Center → Apps and integrations → Integrations → Slack, one Zendesk-to-workspace connection at a time, then /invite @Zendesk per channel (allow up to 15 minutes for new channels to appear).
The documented limits
- Attachments don’t travel — comment notifications include inline images/links, but not file attachments.
- Tickets can’t be closed and fields can’t be edited from Slack; assignment from Slack is group-only, never an individual.
- If the requester can’t be resolved, it defaults to whoever installed the integration — the source of every mysterious “why am I the requester on 40 tickets” thread.
- Org-wide Enterprise Grid channels aren’t supported (multi-workspace channels are); installs predating May 4, 2026 need re-authentication for group approvers; and if Slack’s app-approval setting is off, a reinstall by another user can silently break the connection.
The deeper limit: notifications aren’t knowledge
Configured well, Slack now tells you about tickets. But every notification is a moment in a stream — three weeks later, the thread where support, the AE, and an engineer actually diagnosed the problem is unfindable, and none of it made it back to the account record. The conversation about the customer and the record of the customer never meet. That’s the gap Noded closes: Slack and Zendesk are both native integrations, and the Customer Context Graph weaves channel discussions, tickets, calls, and CRM into one account story — so “what happened with Acme’s escalation?” has an answer that includes the Slack context, right where you work (including in Slack itself). The native integration remains the right tool for the notify-and-create mechanics; it’s free with your plans and this guide is most of what you need to run it well.
FAQ
Can I create a Zendesk ticket from a Slack message?
Yes — the “Create a ticket” message action converts any message (description pre-filled), plus the /zendesk shortcut, the app Home tab, and @zendesk mentions in Slack Connect channels.
Can agents work tickets entirely from Slack?
No — you can comment and create, but not close tickets, edit fields, or assign to individuals (groups only).
Which plans include it?
All current Zendesk Suite and Support plans; it’s configured per Slack workspace in Admin Center. Side conversations may require a higher Suite tier.