How to Integrate Zendesk with Slack (Step by Step)

One quick clarification before we start, because it trips people up: there are two different "Zendesk and Slack" things. This guide covers the Slack for Zendesk Support integration — the official app for internal collaboration (notifications, creating tickets, side conversations). That's almost certainly what you want. There's a separate, more specialized setup where Slack becomes a customer-facing messaging channel (so customers DM you in a Slack Connect channel and it lands as a ticket), which runs through Sunshine Conversations and is a different product entirely. We'll flag the difference again at the end so you don't pick the wrong one.

What the Zendesk Slack integration actually does

The official integration is bidirectional, and it does more than just ping a channel. Here's the full feature set, so you know what you're turning on:

• Ticket notifications into Slack channels. Using Zendesk triggers, you choose exactly which ticket events (new ticket, status change, priority bump, negative CSAT, etc.) post a message to which Slack channel. This is the headline feature for most teams.
• Create and manage tickets from Slack. Turn any Slack message into a Zendesk ticket via the message's More actions → Create a ticket, or use the /zendesk global shortcut to open a blank ticket form. The description auto-populates from the message.
• Reply and add internal notes from Slack. From a ticket-notification thread, agents can post a public reply or Add as internal note — visible only to other agents — without opening Zendesk.
• Side conversations into Slack. Agents can branch a ticket into a Slack thread (e.g. to loop in engineering) directly from the Agent Workspace, with replies synced back to the ticket.
• Generative AI / article suggestions. In channels where the app is active, Zendesk can surface relevant help-center articles as a first line of self-service.
• Approval requests. Route approval flows (e.g. an internal-IT request) to Slack as DMs or temporary channels.

You install it from the Zendesk Marketplace (and it's also listed in the Slack App Directory / Slack Marketplace). The Marketplace is where you find and launch the app; the actual OAuth handshake and channel configuration happen inside Admin Center and Slack, which we'll get to.

The screenshot above is the public Zendesk Marketplace — the catalog where the Slack app is published alongside Zendesk's other integrations. Worth being precise about what this page is and isn't: you discover and open the Slack integration from here, but the connect-workspace OAuth step and all the channel/trigger configuration happen in your Admin Center and in Slack itself (the Slack authorization screens are described from Zendesk's docs below — we haven't staged fake Slack screenshots).

Before you start: prerequisites

A few things will save you a mid-setup detour. Per Zendesk's docs, you need:

• Admin access in Zendesk Support. Installing integrations and creating triggers is admin-only.
• Permission to install apps in your Slack workspace. If your Slack admins have "Approve apps" locked down, you may need a Slack workspace owner to approve the Zendesk app first.
• A workspace you own — not a shared/guest one. The integration cannot be installed on a Slack workspace you've only been invited to as an external/guest user. It has to be a workspace where you're a proper member with install rights.
• Agent Workspace turned on (standard on modern accounts) for side conversations to work.

Note that each connection links one Zendesk account to one Slack workspace. If you run multiple Zendesk instances or multiple Slack workspaces, you run the install once per pair.

Step 1 — Open the Slack integration in Admin Center

1. In Zendesk Admin Center, click Apps and integrations in the left sidebar.
2. Select Integrations → Integrations.
3. Find Slack in the list, click the options menu (the ⋯ icon) next to it, and click View.

This opens the Slack integration's setup page inside Zendesk. (If you came in via the Zendesk Marketplace listing, the "Install" button drops you onto this same Admin Center flow.) Nothing is connected yet — this is just the launch pad.

Step 2 — Connect your Slack workspace (OAuth, both sides)

This is the authorization handshake. It touches both products:

1. On the Slack integration page, click Connect workspace.
2. You'll be handed to Slack's OAuth screen. Confirm the correct workspace is selected in the top-right dropdown — this is the single most common mistake, accidentally authorizing a personal or wrong workspace.
3. Review the permissions Slack lists for the Zendesk app and click Allow. This is the OAuth grant that lets Zendesk post to channels and read the messages you explicitly turn into tickets.
4. Slack returns you to Zendesk. Click Set up in Zendesk Admin Center to land on the configuration screen.

That's the whole OAuth dance: you authorize on the Slack side (Allow), and the connection registers on the Zendesk side automatically. If your Slack workspace requires app approval, the Allow step may instead file a request your Slack admin has to approve before the connection completes.

Step 3 — Add the app to the channels you want it in

Here's the nuance that explains most "why isn't it working?" confusion, and it's worth getting exactly right: **adding the app to a channel governs notifications and Answer Bot — not ticket creation.** Per Zendesk's documentation, you can create a ticket from a message in any Slack channel, but the app must be added to each channel where you want ticket-event notifications to post or where you want the AI/Answer Bot to suggest articles. Installing the integration doesn't auto-join every channel, so until the app is in a channel, that channel won't appear in the notification-trigger dropdown and won't receive posted updates — even though your agents can still raise tickets from messages there.

Two ways to add it:

• **From Slack (works for public and private channels): in the channel, type /invite @Zendesk** and send it. This is the only method for private channels.
• From Admin Center (public channels only): on the Slack integration's Configure screen, open the Channels tab, search and select the public channels you want, and click Add app to channels.

One gotcha to plan around: after you add the app, it can take up to 15 minutes for a channel to show up in the integration's channel dropdowns. If a channel you just added isn't selectable in Step 4, that's usually why — give it a few minutes.

Step 4 — Set up triggers to post ticket notifications

Notifications aren't a single on/off switch — they run on Zendesk triggers, which is a good thing: it means you control exactly which events post where. If you're new to triggers, our explainer on Zendesk triggers covers the conditions-and-actions model, and our how to create a Zendesk trigger walkthrough covers the mechanics. Here's the Slack-specific version:

1. Go to Admin Center → Objects and rules → Business rules → Triggers, open the Tickets tab, and click Add trigger.
2. Name it descriptively — include the workspace and channel, e.g. "Notify #support-urgent on new high-priority ticket." You'll thank yourself later when you have a dozen of these.
3. Under Conditions, define when it fires. Common setups: Ticket is Created, or Priority is Urgent, or Status changed to Solved. Add Meet ALL conditions to keep the channel from getting noisy.
4. Click Add action, choose Notify Zendesk integration, then select the Slack integration.
5. Pick your Slack workspace, then the channel from the dropdown. Remember: only channels the Zendesk app has been added to (Step 3) appear here. Private channels you're not a member of won't show.
6. Fill in the Notification header and Notification body. Both support Markdown and Zendesk placeholders — the curly-brace tokens for ticket title, requester name, and ticket URL — plus Slack alerts like <!here> and user/group mentions to actually get someone's attention.
7. Click Create.

A practical pattern teams settle on: a low-noise channel that gets only urgent/breaching tickets via a tight trigger, plus a firehose channel for a team that wants every new ticket. Build one trigger per channel-and-event combination.

Step 5 — Create tickets from Slack messages

This is the inbound half, and it's where Slack becomes a genuine intake source — perfect for internal requests ("the VPN is down") that would otherwise vanish in chat. Two methods:

• Turn an existing message into a ticket. Hover over the Slack message, click the More actions icon (⋯), and choose Create a ticket. The Description auto-fills with the message text. Set the remaining fields and click Submit — the new ticket's details post back into the thread.
• Start a fresh ticket with the shortcut. Type /zendesk in any channel, choose Create a ticket, and fill in Subject, optional Requester and Assignee (the assignee is a Zendesk group), and a Description, then submit. Ticket creation works from any channel — the app doesn't have to be added there for this.

Every ticket created this way is automatically tagged created_from_slack. That tag is genuinely useful — build a Zendesk view filtered on it to see exactly how much of your volume originates in Slack, and route or report on it separately.

A note on honesty here: the modern integration handles brand and group assignment through the ticket form fields and your normal Zendesk routing/triggers rather than one big "default brand" dropdown buried in settings. If you need every Slack-created ticket to land in a specific group or brand, set that with a trigger keyed on the created_from_slack tag — it's more reliable than hunting for a single default setting.

Step 6 — Reply and add internal notes from Slack

Once notifications are flowing, agents can act on tickets without context-switching:

1. In the Slack thread under a ticket notification, hover over the message and click the More actions icon.
2. Choose to post a public reply (goes to the requester) or Add as internal note (visible only to other Zendesk agents — the same private/public distinction you have inside Zendesk).
3. Type your comment and Submit. It syncs to the ticket.

Click any ticket subject or number in a notification to jump straight to the full ticket in Zendesk when you need the complete picture.

Step 7 — Test the full loop

Don't trust a fresh integration until you've watched it work end to end:

1. Test inbound: in a channel where the app is added, post a test message, use More actions → Create a ticket, submit, and confirm the ticket appears in Zendesk with the created_from_slack tag.
2. Test notifications: create or update a ticket in Zendesk that should satisfy one of your Step 4 triggers, then confirm the message posts to the right Slack channel with your header/body and placeholders rendered.
3. Test the reply path: from that Slack notification, add an internal note and confirm it lands on the ticket as a private comment.
4. Check a private channel: if you set one up, confirm you used /invite @Zendesk (private channels won't work via the Admin Center method).

If a channel won't appear in a trigger's dropdown, 90% of the time it's the 15-minute propagation delay or the app simply wasn't added to that channel. If notifications never fire, re-check the trigger's conditions — over-tight conditions are the usual culprit.

Limitations to know

The integration is solid but not unlimited. Per Zendesk's docs:

• No org-shared (Slack Connect) channels for notifications — it supports multi-workspace channels but not externally shared ones.
• Approval requests are supported for one Slack workspace at a time.
• If you run multiple help centers/brands, Answer Bot article suggestions from each appear separately, not merged.
• Reinstalling the Slack app can break the connection if your workspace's "Approve apps" setting is off — coordinate with your Slack admin.
• It's built primarily for internal collaboration and intake, not for being your customer-facing live chat (that's the Sunshine Conversations path).

Where AI fits in

Slack notifications are about surfacing tickets to humans faster — a real win, but notice the ceiling: the ticket still waits for a person to read the Slack ping, open it, and respond. The integration moves information; it doesn't resolve anything.

That's the layer an AI agent adds. To be clear about what Macha is: it's not a help desk and not a Zendesk replacement — it runs on top of your existing Zendesk. Instead of only posting a ticket into Slack for a human to grab, an AI agent can read the incoming request, pull from your connected knowledge and past tickets, and draft or fully resolve the routine ones before anyone gets pinged — escalating to your Slack channel only the cases that genuinely need a person, with context attached.

There's a second, neater connection too: Slack itself can be a knowledge source. Years of answers your team has typed into support and engineering channels are real institutional knowledge — an AI agent can learn from that corpus the same way it learns from your help center, so the resolutions it drafts sound like your team, not a generic bot.

The honest framing: it's another integration to configure, and it's only as good as the knowledge you connect to it. On cost, Macha bills per AI action — any automated step it takes, whether drafting a reply, tagging, routing, or resolving — not per resolution, because most automation is work done along the way, not a tidy closed ticket. If a big slice of what hits your Slack channels is repetitive and answerable from existing knowledge, that's the line where notifications alone stop scaling. You can try it free — 7-day free trial, no credit card required.

Frequently asked questions

How do I connect Zendesk to Slack? Install the official Slack for Zendesk Support integration: in Admin Center, go to Apps and integrations → Integrations → Integrations, click the options menu next to Slack and choose View, click Connect workspace, authorize on Slack's OAuth screen by selecting the right workspace and clicking Allow, then return to Zendesk to configure. You must be a Zendesk admin and have permission to install apps in the Slack workspace.

How do I get Zendesk ticket notifications in a Slack channel? Notifications run on triggers. First add the Zendesk app to the target channel (type /invite @Zendesk in Slack, or use the Channels tab in the integration's Configure screen for public channels). Then create a trigger in Admin Center → Objects and rules → Business rules → Triggers, add the action Notify Zendesk integration → Slack, pick the workspace and channel, and write the notification header/body.

Why doesn't my Slack channel appear in the notification dropdown? Two usual reasons: the Zendesk app hasn't been added to that channel yet (only channels the app is in appear in the list), or it was added in the last few minutes — it can take up to 15 minutes for a channel to propagate into the dropdown. Private channels also only work if you added the app via the /invite @Zendesk slash command.

Can I create a Zendesk ticket from a Slack message? Yes. Hover over the message, click the More actions icon, and choose Create a ticket — the description auto-fills from the message. Or type /zendesk in a channel for a blank ticket form. Tickets created this way are automatically tagged created_from_slack.

Is the Zendesk Slack integration free? The integration itself is provided by Zendesk at no extra cost and installed from the Zendesk Marketplace / Slack App Directory; you just need an eligible Zendesk Support plan and a Slack workspace. Always confirm plan availability for advanced features (like side conversations and approval requests) in your own account, since Zendesk adjusts feature tiers periodically.

What's the difference between this and using Slack as a customer channel? This integration is for internal use — your team gets notifications, creates tickets, and collaborates in Slack. Using Slack as a customer-facing messaging channel (where customers message you in Slack and it becomes a ticket) is a separate setup built on Sunshine Conversations. Most teams want the standard integration covered in this guide.

The bottom line

Integrating Zendesk with Slack is a clear sequence: install the Slack for Zendesk Support app (Admin Center → Apps and integrations → Integrations), authorize OAuth by connecting your workspace and clicking Allow on Slack's side, add the app to your channels (/invite @Zendesk for private ones), build triggers to post the ticket events you care about into specific channels, create tickets from Slack messages via More actions or /zendesk, and test the full loop before you rely on it. Remember the headline distinctions: notifications run on triggers (so you control the noise), the app only works in channels you've added it to, and this is the internal integration — not customer-facing live chat. Done right, it turns Slack from a place where requests get lost into a real, two-way extension of your Zendesk ticketing system.

Setup steps verified against Zendesk's official documentation, June 2026. Zendesk and Slack both revise their UIs periodically — confirm labels in your own account before relying on them. Slack-side authorization screens are described from Zendesk's docs, not staged screenshots.