Zendesk triggers can push a Slack notification the moment something changes on a ticket — a new ticket lands, a status shifts, a priority is bumped, or an SLA is at risk. Configured well, they get the right agent to the right ticket without anyone watching Zendesk views. This guide walks through setting up a Zendesk trigger that notifies a Slack channel, then where teams typically extend the pattern with ClearFeed.
Set up the trigger in Zendesk
Follow these steps in your Zendesk Admin Center.
- Begin in the Admin center and find Objects and rules in the sidebar; select this option. Subsequently, choose Business rules from the expanded menu options, and then scroll down to Triggers.
- Click Create trigger.
- Give the trigger a name (e.g., Urgent tickets → Slack) in the Trigger name field. Include the Slack channel name so you can easily identify the trigger later.
- Add a concise Description for your trigger, outlining its function. For instance, you might describe it as: "Sends an alert to all users in the #customer-support channel whenever a ticket is marked as Urgent."
- In the Conditions section, select Ticket under Category, Is as an Operator, and Created as a Value.
- Now, in the Actions, select Notify by and then Zendesk integration.
- Select the workspace that is connected to the Zendesk account and the right channel where you would like to get the notifications.
The Slack channel selected in the action starts receiving notifications the next time the trigger's conditions are met on a Zendesk ticket.
- You can give it a title that will be used when notifications are sent to your Slack channel.
And the last step: save the settings. That’s it!
Where teams extend this with ClearFeed
Triggers are the right tool for one-way notifications: something happens in Zendesk, a message lands in Slack, and the trigger's job is done. That works for alerts. It runs out of room the moment agents want to act on the ticket from Slack — reply to the customer, add an internal note, edit a field, or just track what came of the notification.
ClearFeed is built for that pattern. Its Reverse Zendesk Flow pulls Zendesk tickets started anywhere — email, help center, chat, or the Zendesk agent workspace — into a Slack channel and keeps the two in sync, without maintaining a trigger and webhook for every scenario.
AI runs across that connection. In Slack, a ClearFeed AI Agent can answer routine questions in the thread from your configured knowledge sources — including your Zendesk help center — before a ticket is even filed, or suggest answers privately to the responder team.
On the Zendesk side, ClearFeed writes an AI-generated title and description when a Slack thread becomes a ticket, and AI-driven status transitions move the ticket to Pending or re-open it based on the intent of the next reply — without anyone toggling status manually.
Once the ticket is in the Slack thread, teams can:
- Reply from the thread — both public comments and internal notes post back to Zendesk, attributed to the actual Slack author when their email matches a Zendesk user.
- Assign, edit, and solve tickets from Slack, or via emoji reactions on the request channel.
- See status changes (including Zendesk custom statuses), CSAT responses, and Slack message edits sync back to the Zendesk ticket automatically.
Teams that outgrow one-way triggers — because they want to run support in Slack, not just get pinged there — usually consolidate on ClearFeed's Reverse Zendesk Flow.
Explore the ClearFeed Slack + Zendesk integration or book a walkthrough.
