Zendesk
Version 0.0.1
Checkout the Zendesk API docs for more information
Set up
To set up with Zendesk, you just need your Zendesk Username, Password and Domain.
Your domain is your URL when you are accessing your Zendesk account e.g. https://<company_name>.zendesk.com.
For Zendesk - do not include the https:// or .zendesk.com
For Zendesk (Legacy) - please include https:// and .zendesk.com within the domain.
Alternatively, setup can also be done using a token (this is also our suggested method for set-up) by following these steps:
In the username field enter:
<email>/token
e.g. [email protected]/token
In the password field enter:
<token>
e.g. 7893u5gfd5g93tj349tu3489tuhu34ihtu3gt34
See how to get a Zendesk token here.
It is recommended you use the Zendesk token as these do not expire but depending on your security level within Zendesk, your password will expire.
Features
| Feature | Support | Notes |
|---|---|---|
| Backfill | ✅ | Tickets, Users, Organisations, Ticket Metric Events (10 years). Ticket Fields, Groups (All time). Calls, Call Legs (5 years). |
| Incremental | ✅ | Tickets, Users, Organisations, Groups, Ticket Events, Ticket Metric Events, Calls |
| Custom backfill | ❌ | |
| API reliability | 🟢 | Reliable |
Reports detail
| ⬇️ Report | 🔑 Incremental key | 🔑 Primary key | 📄 Link to API endpoint |
|---|---|---|---|
| Tickets | GENERATED_TIMESTAMP | id | List all Tickets |
| Users | updated_at | id | List all Users |
| Organisations | updated_at | id | List all Organisations |
| Groups | N/A | id | List all Groups |
| Ticket Fields | None | id | List all Ticket Fields |
| Ticket Field Option (legacy only) | None | id | List all Ticket Field Options |
| Ticket Metric | None | id | Ticket Metrics |
| Ticket Metric Events | TIME | id | Ticket Metric Events |
| Calls | UPDATED_AT | id | Calls |
| Call Legs | UPDATED_AT | id | Call Legs |
We recently migrated from our Zendesk (Legacy) connector. All of the reports from the legacy are available on the new connecter other than Ticket Field Options as the Ticket Field Options are all returned with the Ticket Fields endpoint.
Authentication
Our suggestion is to use the
tokenoption for authenticating, as this is less prone to issues.
Updated about 2 months ago