Zendesk
Zendesk is the support side of every customer relationship. Connecting it gives Sonora visibility into ticket volume, response times, sentiment trends, escalation patterns, and the actual content of support conversations. Those signals feed health scoring, eCSAT, and the support-related actions your CSMs see every morning.
Authentication uses an admin email plus a Zendesk-issued API token. The token is read-only.
What syncs
Section titled “What syncs”| Object | Notes |
|---|---|
| Tickets | Subject, status, priority, type, custom fields |
| Comments | Internal notes and public replies (toggle in setup) |
| Users | End users (customers) and agents (your team) |
| Organizations | Map to Sonora customers via configured matching |
| Tags | Used as filters in chat and Canvas |
Prerequisites
Section titled “Prerequisites”- Zendesk admin role
- Token authentication enabled in your Zendesk instance
1. Generate an API token
Section titled “1. Generate an API token”- In Zendesk: Admin Center → Apps and integrations → APIs → Zendesk API.
- On the Settings tab, enable Token Access if it isn’t already.
- Click Add API token, label it “Sonora Integration”, and click Create.
- Copy the token — Zendesk will not show it again.
2. Connect in Sonora
Section titled “2. Connect in Sonora”- Settings → Integrations → Zendesk → Connect.
- Fill in:
- Subdomain — the prefix in your Zendesk URL (e.g.,
acmeforacme.zendesk.com) - Admin Email — the email of the admin user the token is associated with
- API Token — the token you just generated
- Subdomain — the prefix in your Zendesk URL (e.g.,
- Decide whether to Import ticket comments. Most teams leave this on; turn it off if you want only metadata for cost or compliance reasons.
- Save.
The first import covers your active tickets and recent history. Sonora pulls updates incrementally after that.
Customer matching
Section titled “Customer matching”Sonora matches Zendesk organizations to customers via name and domain. Configure organization matching from the Zendesk card after the initial sync — for B2B accounts where multiple end users share an organization, mapping the org once propagates to every related ticket.
Disconnect
Section titled “Disconnect”From Settings → Integrations, click Disconnect on the Zendesk card. Revoke the token in Admin Center → APIs → Zendesk API to fully cut access.
Troubleshooting
Section titled “Troubleshooting”“Couldn’t authenticate” — The most common cause is an admin email that doesn’t match the user the token belongs to. Tokens are scoped to the user that created them; the email field has to be that user’s email.
Ticket comments missing — Confirm “Import ticket comments” is enabled in the Zendesk card configuration.
Some tickets aren’t syncing — Zendesk’s group and brand restrictions can limit what an admin sees. If your admin account is restricted to one brand, create a token under an unrestricted account or scope the integration to the brand you want.
Rate limiting — Sonora respects Zendesk’s API limits and pauses automatically when a window is exhausted. Initial backfills for instances with millions of tickets may take several hours.