Integrations / Zendesk
Zendesk
Zendesk customer service platform for managing tickets, users, and knowledge base articles
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
Permissions Telara requests
- readOAuth 2.0
- writeOAuth 2.0
- tickets:readOAuth 2.0
- tickets:writeOAuth 2.0
- users:readOAuth 2.0
- users:writeOAuth 2.0
In Telara
Connect in Telara
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
- Subdomain
API Token auth — uses Basic Auth with '{email}/token:{api_token}'. Requires subdomain and email.
In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.
- Subdomain
- API token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Tickets | Partial — not every record the vendor holds is synced |
| Users | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Tickets | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
| Users | Up to 1 hour | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Tickets, Users.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty