How To Create a Zendesk Ticket From Slack

There are two very different ways to create Zendesk tickets from Slack, and the right one depends on how your team actually uses Slack for support.

Zendesk’s own Slack app is built for ad-hoc conversions: an agent (or a Slack Connect participant) spots a message and turns it into a ticket on demand.
ClearFeed is built for teams whose support conversation lives in Slack — customer Slack Connect channels, internal IT / HR / Ops help channels, DMs to a support bot — and who want those conversations to become Zendesk tickets automatically, with structured intake, forms, private triage, and bi-directional sync.

This guide covers every documented method on both sides so you can pick the one that fits.

‍

Create Zendesk Tickets With the Native Slack App

Zendesk’s official Slack for Zendesk Support app has to be installed in your Slack workspace and invited to the channel where you want ticket creation to work. Zendesk keeps the current install path and any UI changes in their Marketplace listing — use that as the source of truth if any of the labels below have shifted.

Slash command: /zendesk create_ticket

Use this when you want to file a ticket without an existing Slack message to attach it to.

In a channel where the native Zendesk app has been invited, type /zendesk create_ticket and hit enter.
Fill out the Create a new ticket form — typically Subject, Requester, Assignee, and Description.
Submit. The ticket is created in Zendesk Support, and a confirmation is posted back into the Slack channel.

Message action: convert an existing Slack message

Use this when a Slack message itself is the source of the ticket.

Hover over the Slack message and open More actions.
Choose Create a ticket, fill out the details, and submit.
The ticket is created in Zendesk and posted back as a reply in the Slack thread with the Zendesk metadata attached.

@zendesk mention in a Slack Connect channel

Slack Connect channels let internal and external participants collaborate in the same channel. The native Zendesk app lets either side kick off ticket creation with an @zendesk mention.

In a Slack Connect channel where the Zendesk app is present, type an @zendesk mention in a message.
The Zendesk app replies with a button to create a new ticket.
Click Create a ticket, fill out the details, and submit.

Tickets filed through the slash command or the message action are typically tagged by Zendesk so you can build views and business rules around them. The exact tag naming and behavior for Slack Connect creations is documented in Zendesk’s own Help Center.

‍

Where the native app stops

The native app is a strong on-demand creator. It doesn’t cover the workflows that most support teams eventually need:

Automatically converting every new thread in a customer or internal support channel into a Zendesk ticket.
Bi-directionally syncing replies typed in Slack with the corresponding Zendesk ticket after it’s filed.
Enforcing Zendesk field validation (required fields, custom fields, multi-form flows) at intake.
Private triage on a live customer thread without pulling the requester into that conversation.
Private ticket creation via DM for sensitive IT / HR / People-Ops requests.

If any of those describe how your team actually works in Slack, ClearFeed is the alternative most teams reach for.

‍

Create Zendesk tickets from Slack with ClearFeed

Once a Slack channel is added to a ClearFeed Collection and Zendesk is set as the Ticketing Integration for that Collection, ClearFeed exposes six documented methods for turning Slack activity into Zendesk tickets. Which ones are available depends on Collection settings, the channel type (public, private, Slack Connect, DM), and your ClearFeed edition.

1. Automatic ticketing

Set the Collection’s Ticketing trigger mode to Automatic, and every new thread in a monitored channel is converted into a Zendesk ticket the moment ClearFeed detects a non-ignorable request. Works in customer Slack Connect channels and internal support channels alike.

2. Emoji reaction (🎫 or custom)

Set the trigger mode to Emoji, and a responder reacts to the first message in a thread with 🎫 (or a custom emoji configured for the Collection) to file the Zendesk ticket. All messages in that thread — and their attachments — are synced to the ticket.

3. @ClearFeed mention on a top-level message

With bot-tagging enabled in the Collection’s ticketing settings, users can create a Zendesk ticket by mentioning @ClearFeed in a top-level Slack message. Tagging @ClearFeed inside a thread invokes the Virtual Agent instead of creating a ticket.

4. Triage channel → File a Zendesk Ticket

In a paired private triage channel, open More Actions on any incoming request and choose File a Zendesk Ticket. The customer-facing Slack thread stays clean; responders coordinate and file the ticket in the triage view. Public triage comments sync to Zendesk as public replies; private triage comments sync as internal notes.

5. Zendesk Forms via File Ticket button or /cf-file

Configure a Zendesk Form in ClearFeed with any of the supported Zendesk field types — text, multi-line text, email, phone, number, date, drop-down, multi-select, checkbox, tags, attachments — plus Zendesk system fields (Subject, Description, Requester Email, Status, Priority, Assignee, Group). Users file tickets either by clicking the File Ticket button that ClearFeed surfaces on a request, or by running the /cf-file command in a monitored channel. If a form has required fields that aren’t hidden or pre-defaulted, ClearFeed prompts the user to fill them before the Zendesk ticket is created; fields Zendesk itself marks “required to solve” are enforced through a Solve dialog before the ticket can be closed. If multiple forms are configured for the Collection, a form picker is shown.

6. Private tickets from DMs (Internal Helpdesk & Integrations editions)

For sensitive internal support — HR, Finance, People Ops, IT — ClearFeed supports creating tickets privately, without posting on any channel. Available in the Internal Helpdesk and Integrations editions. The methods:

DM the ClearFeed App for Slack. The message automatically becomes a private ticket.
Click File a ticket in the ClearFeed App’s App Home, pick a form if multiple are configured, and submit.
Run the Slack shortcut /file a ticket from anywhere in Slack.

Request Routing lets DM-created tickets be routed to a specific Collection (and, with multiple ClearFeed accounts, a specific account) so the ticket lands in the right Zendesk workspace with the right triage channel and settings applied.

What happens after the Zendesk ticket is created

Regardless of which ClearFeed method files the ticket:

Slack messages and attachments in the source thread are attached to the Zendesk ticket.
ClearFeed adds the clearfeed tag, the source Slack channel name, and the form name (if a form was used) so the ticket is routable in Zendesk triggers and automations.
Replies typed in Slack sync to Zendesk (public replies as comments, private triage comments as internal notes). Zendesk-side comments and status changes flow back to the Slack thread. Sync mode is configurable per ticket.
Responders can edit ticket fields, priority, and assignee from Slack via the Edit Ticket action, and mark tickets solved from the request channel.
The requester sees the Zendesk ticket ID and current Status — including custom Zendesk statuses — posted back in the Slack thread.

Choosing the right method

Ad-hoc tickets from internal chatter — no monitored channels, no automation. Native Zendesk Slack app is enough.
Slack Connect with customers where any incoming message should become a ticket. ClearFeed with Automatic ticketing.
Internal help channel where requesters expect a fielded intake form. ClearFeed with Zendesk Forms and Automatic ticketing.
Support team wants to triage privately before the ticket is filed. ClearFeed Triage channels with manual (emoji) trigger mode.
Sensitive tickets that shouldn’t sit in any channel. ClearFeed private tickets via DM or /file a ticket.