# Zendesk integrations

*4 integrations*

**In short:** Integrating Zendesk means getting tickets in front of the people who do not work in Zendesk: engineers in Jira, account owners in Salesforce or HubSpot, and teams in Slack. What breaks is the boundary between internal and public, where one wrong default sends internal notes to a customer, along with identity matching to CRM records, trigger loops, and per-minute API limits during a ticket storm.

## What connects to Zendesk

Zendesk is where customer support happens, and its integrations exist so that support does not stay a silo.

The most common need is escalation. A ticket becomes a [Jira](https://seamless.engineering/integrations/zendesk-jira/) issue, and when engineering moves it through its workflow the ticket and the requester are updated, with many tickets able to point at one bug. The second is customer context. Account owners in [Salesforce](https://seamless.engineering/integrations/zendesk-salesforce/) or [HubSpot](https://seamless.engineering/integrations/zendesk-hubspot/) want open tickets, CSAT and SLA breaches on the account without opening Zendesk, and agents want lifecycle stage and open deals without leaving their desk. The third is attention: new tickets, priority changes and SLA breaches routed into [Slack](https://seamless.engineering/integrations/zendesk-slack/), one thread per ticket, with threaded replies going back as internal notes or public replies.

## Where Zendesk integrations break

- **Public versus internal.** A Zendesk comment is either a public reply or an internal note. Every comment coming in from Jira, Slack or a CRM needs a deliberate visibility, or internal chatter eventually reaches a paying customer.
- **Trigger loops.** Zendesk triggers fire the pipeline, the pipeline writes a comment back, and that comment fires the trigger again. Pipeline-authored updates have to be tagged and filtered out.
- **Identity matching.** Zendesk allows aliases, secondary addresses and merged users, while CRMs dedupe on email. Organizations rarely share an ID with Salesforce Accounts or HubSpot companies, so matching needs a deliberate rule and a stored external ID.
- **Fixed statuses.** Zendesk has a fixed set of ticket statuses. Mapping them onto a Jira workflow, a Salesforce picklist or a HubSpot ticket pipeline, including solved-then-reopened, is an explicit decision.
- **Rate limits and HTML.** Zendesk caps API calls per minute by plan and answers with 429 and Retry-After, and comment bodies are HTML with inline images. Bursts need pacing, and bodies need conversion for Jira and Slack.

## All Zendesk integrations

### Support ↔ ITSM & Dev

- [Zendesk ↔ Jira](https://seamless.engineering/integrations/zendesk-jira/): Zendesk Jira integration
- [Zendesk ↔ Salesforce](https://seamless.engineering/integrations/zendesk-salesforce/): Zendesk Salesforce integration
- [Zendesk ↔ Slack](https://seamless.engineering/integrations/zendesk-slack/): Zendesk Slack integration
- [Zendesk ↔ HubSpot](https://seamless.engineering/integrations/zendesk-hubspot/): Zendesk HubSpot integration

## Zendesk API changelog

- [Zendesk API changelog](https://seamless.engineering/api-changelog/zendesk/): 0 breaking changes and 2 deprecations in the last 90 days

## Request a scoping call

Connecting Zendesk to something not listed here? Tell us which systems are involved and what data has to move. Fixed-price scoping quote within 48 hours.

- Email: hello@seamless.engineering
- Contact form: https://seamless.engineering/#contact