Once tickets start flowing into Zendesk from Slack, agents need a fast way to see just the ones that came from Slack — separate from email, web widget, or Help Center tickets. Zendesk does not add a dedicated "Slack" view out of the box, but you can build one in two ways: filter by the tag that the Slack integration applies, or build a Zendesk view scoped to the Slack channel.
If you use ClearFeed's Slack + Zendesk integration, you often do not need to leave Slack at all — ticket details, status, and controls are posted back into the Slack thread. Both approaches are covered below.
Method 1: Filter Zendesk views by the Slack tag
Slack-created tickets carry a tag applied by the Slack integration (for example, created_from_slack on Zendesk's native app, or clearfeed and slack-channel-name on tickets created through ClearFeed). Filter on the tag you use:
- Open Zendesk Support and go to Views from the left navigation.
- Click Filter at the top of the ticket list.
- Add a condition on the Tags field and enter the tag applied by your Slack integration. You can see a tag named 'created_from_ slack' in the field.
- Click Apply Filters. Zendesk shows every open ticket that carries that tag.

To reuse the filter, save it as a dedicated Zendesk view:
- Go to the Admin center and select Workspaces in the left sidebar. From the Agent tools, select Views.

- Click on Select view and fill in the details as per your requirements, and save the settings.

Method 2: Build a view scoped to the Slack channel
If different Slack channels serve different customers or teams, tag filtering alone is coarse. ClearFeed adds the Slack channel name as a tag on every ticket it creates, so you can build one view per channel:
- Repeat the steps listed above.
- Scroll down to Conditions. In the Field section, select Ticket and then Tags.
- Select Contains at least one of the following from the dropdown menu and enter created_from_slack as the value.

- Save the view. Zendesk agents can now open a per-channel queue directly from the Views sidebar.
How ClearFeed surfaces Zendesk tickets in Slack
Most teams that ask this question want the answer in Slack rather than in Zendesk. ClearFeed does that natively:
- Ticket details posted to the thread. As soon as a ticket is created, ClearFeed posts a block on the Slack thread showing the ticket title, ID, URL, and status — including Zendesk custom statuses.
- Automatic tagging for filtering in Zendesk. ClearFeed adds the clearfeed tag, the Slack channel name, and the form name to every ticket, so Zendesk-side views stay easy to build and safe to use in triggers (for example, if the clearfeed tag is present, do not auto-assign).
- Bidirectional sync. Replies on the ticket appear on the Slack thread and vice versa, so agents rarely need to switch contexts to catch up on a request.
- Solve, edit, and unlink from Slack. The ticket block exposes Mark as Solved, Edit Ticket, and Unlink Ticket buttons, gated to responders or all users depending on how you configure Screens.
- Ticket-link formats matched to the reader. Customer/request channels show the requester-facing /requests/{ticket_id} link; triage channels show the agent-facing /agent/tickets/{ticket_id} link.
- Reverse Zendesk flow. Tickets that originate outside Slack (email, Help Center, web widget) can be routed into a Slack channel with the same details block and bidirectional sync.
Want to work from Slack on Zendesk tickets?
Upgrade to ClearFeed for two-way Slack ↔ Zendesk sync, ticket details posted straight to the Slack thread, and per-channel visibility on both sides.
- Learn More about Slack + Zendesk with ClearFeed
- Try the Sandbox













