# Slack + Zendesk integration > Stop bouncing between chat and your ticketing system. Keep tickets, alerts, and updates moving through one connected workflow. **Canonical page:** https://tray.ai/connectors/slack-zendesk-integrations/ **Slack connector:** https://tray.ai/connectors/slack-integrations/ **Slack documentation:** https://tray.ai/documentation/connectors/service/slack **Zendesk connector:** https://tray.ai/connectors/zendesk-integrations/ **Zendesk documentation:** https://tray.ai/documentation/connectors/service/zendesk ## Overview Slack and Zendesk are probably already running in a dozen browser tabs on your support team's screens — Slack for real-time conversation, Zendesk for structured ticket management. The problem is they don't talk to each other. Agents manually copy ticket details into chat, chase status updates across two systems, and lose time to constant context-switching. Connecting Slack and Zendesk through tray.ai creates a bidirectional flow of information between both platforms, so your team can stay in Slack while Zendesk stays accurate. Support teams live in Slack, but their work is tracked in Zendesk. Without a connection between them, ticket escalations get missed, SLAs slip, and agents have no real-time visibility into what needs attention first. Connecting Slack and Zendesk through tray.ai lets you automatically route new tickets to the right Slack channels, alert on-call engineers to urgent issues, let agents update ticket status without leaving Slack, and push immediate notifications when customer priority or sentiment changes. The result is faster resolutions, better CSAT scores, and less time spent manually keeping two systems in sync. ## Use cases ### Instant Ticket Notifications in Slack When a new ticket is created in Zendesk, tray.ai posts a formatted notification to a designated Slack channel — ticket subject, priority, requester name, and a direct link included. Agents get real-time visibility into incoming requests without switching tabs. - Stop manually monitoring the Zendesk queue - Spot and action high-priority tickets before they sit too long - Route notifications to the right team channel based on ticket tags or category ### Escalation Alerts for High-Priority or Breaching Tickets When a Zendesk ticket breaches its SLA, hits a critical priority level, or gets escalated by a customer, tray.ai fires an alert to a dedicated Slack escalation channel and optionally @mentions the responsible agent or manager. Urgent issues don't get buried during busy periods. - Cut SLA breaches with proactive, real-time escalation alerts - Automatically tag the right team member so accountability is clear - Customize escalation rules based on ticket priority, group, or tags ### Slack-Powered Ticket Status Updates Support agents can update Zendesk ticket status, add internal notes, or change assignee directly from a Slack message using slash commands or interactive buttons — no need to open Zendesk. tray.ai translates those Slack actions into Zendesk API calls in real time. - Cut context-switching for support agents - Speed up ticket resolution by enabling in-conversation updates - Keep Zendesk records accurate while working natively in Slack ### Daily Support Digest Delivered to Slack tray.ai can run on a schedule, query Zendesk each morning, and compile a digest of open tickets by status, SLA health, longest-pending tickets, and top requesters, then post it as a formatted message to your support leadership channel. Teams start the day knowing exactly where things stand. - Give support managers a daily operational snapshot without manually building reports - Surface aging or neglected tickets before they turn into escalations - Drive accountability with team-wide visibility into queue health ### New Zendesk User or Organization Alerts When a new organization or high-value customer account is created in Zendesk — perhaps synced from your CRM — tray.ai notifies your customer success or account management team in Slack so they can reach out proactively or get onboarding resources ready. - Keep support and customer success teams in sync on new account activity - Trigger proactive outreach the moment a new organization is onboarded - Reduce time-to-first-contact for enterprise or strategic accounts ### Customer Satisfaction (CSAT) Score Alerts When a Zendesk CSAT rating comes in — especially a negative one — tray.ai immediately posts the feedback, the associated ticket details, and the agent involved to a Slack channel. Support managers can follow up with the customer or coach the agent right away, not days later. - Act on negative CSAT scores within minutes - Close the feedback loop between customer sentiment and team coaching - Build a real-time quality signal into your team's daily workflow ### Cross-Team Incident Collaboration via Slack Threads When a Zendesk ticket is tagged as a product incident or service outage, tray.ai automatically creates a dedicated Slack thread or channel, invites relevant engineering and support stakeholders, and posts live ticket updates as they come in — with Zendesk as the source of truth. - Get engineering and support teams working in the same place during incidents - Cut duplicate communication across teams - Keep a real-time update log linked back to the Zendesk ticket ## Templates ### New Zendesk Ticket → Slack Channel Notification Automatically posts a formatted message to a specified Slack channel whenever a new ticket is created in Zendesk, including ticket ID, subject, priority, requester, and a clickable link. Connectors used: Zendesk, Slack ### Zendesk SLA Breach → Slack Escalation Alert with @Mention Monitors Zendesk for tickets approaching or breaching SLA thresholds and fires an urgent Slack alert to an escalation channel, tagging the assigned agent and their manager by Slack user ID. Connectors used: Zendesk, Slack ### Slack Slash Command → Update Zendesk Ticket Lets support agents type a slash command in Slack (e.g., /update-ticket) with a ticket ID and status, triggering tray.ai to update the corresponding Zendesk ticket status, assignee, or internal note without leaving Slack. Connectors used: Slack, Zendesk ### Negative CSAT Received → Slack Alert to Support Manager When a Zendesk ticket receives a negative customer satisfaction rating, tray.ai immediately sends a Slack direct message to the support manager with the rating, customer comment, ticket details, and handling agent — so follow-up happens fast. Connectors used: Zendesk, Slack ### Scheduled Daily Zendesk Digest → Slack Summary Post Runs on a daily schedule to query Zendesk for open ticket counts by status and priority, unresolved tickets beyond 48 hours, and SLA health metrics, then formats and posts a morning briefing to a Slack leadership channel. Connectors used: Zendesk, Slack ### Zendesk Incident Tag → Auto-Create Slack Incident Channel When a Zendesk ticket is tagged with 'incident' or escalated to a critical priority, tray.ai automatically creates a new Slack channel named after the incident, invites relevant stakeholders, and posts the Zendesk ticket details as the first message. Connectors used: Zendesk, Slack ## Challenges Tray.ai solves ### Keeping Slack User IDs in Sync with Zendesk Agent Emails Mapping Zendesk agent profiles to their Slack accounts is a persistent headache. Agents change roles, use different email addresses across tools, or join and leave teams constantly. Without accurate mapping, @mentions fail or land with the wrong person. **How Tray.ai helps:** tray.ai's workflow logic dynamically looks up a Slack user's ID by email address at runtime using the Slack API, then caches the result. No static mapping tables to maintain — tray.ai resolves the correct Slack identity on the fly, every time. ### Handling High Ticket Volume Without Slack Noise Overload In high-volume support environments, piping every Zendesk ticket into Slack floods channels fast. Agents start ignoring the notifications meant to help them — which is worse than having no integration at all. Filtering by priority, tag, or group isn't optional; it's the whole game. **How Tray.ai helps:** tray.ai gives you granular conditional logic to filter and route Zendesk events before they reach Slack. You can set rules like 'only notify if priority is High or Urgent,' 'skip tickets from internal users,' or 'route by ticket group to separate team channels' — keeping Slack useful instead of noisy. ### Bidirectional Data Consistency Between Slack Actions and Zendesk Records When agents act in Slack — claiming a ticket, adding a note, changing status — those changes need to land in Zendesk reliably. Failures or race conditions leave Zendesk records out of sync with what was actually discussed in Slack, and that's a mess to untangle after the fact. **How Tray.ai helps:** tray.ai uses error handling, retry logic, and conditional branching to make sure every Slack-initiated action completes its Zendesk API call. If an update fails, tray.ai notifies the agent in Slack immediately rather than silently dropping it. ### Authenticating and Securing Slack Slash Command Requests Slack slash commands send HTTP POST requests to a public endpoint, which means your integration needs to verify request signatures properly — otherwise spoofed commands could manipulate Zendesk tickets. It's a real security concern in production, and easy to overlook during setup. **How Tray.ai helps:** tray.ai's HTTP trigger connectors support Slack's signing secret verification natively within the workflow. Every incoming slash command is validated against Slack's HMAC signature before any Zendesk action runs — no custom middleware or exposed Lambda functions needed. ### Managing Workflow Complexity as Integration Needs Grow A simple 'post new tickets to Slack' workflow has a way of turning into a sprawling web of escalation rules, routing logic, team-specific channels, and bidirectional updates. Maintaining that in custom code or a rigid point-to-point tool gets painful fast. **How Tray.ai helps:** tray.ai's visual workflow builder lets you build, version, and iterate on complex Slack-Zendesk integrations without writing infrastructure code. As your support operations grow, you can extend existing workflows with new branches, pull in additional connectors like Salesforce or Jira, and keep full visibility into your automation logic from one place. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/