We do not currently have a dedicated Zendesk Connector for QlikView and Qlik Sense, however it is relatively straightforward to use our
General XML/JSON API Web Connector to load data from the
Zendesk API into QlikView.
If we receive sufficient interest in accessing this API we will consider adding a dedicated more streamlined and user friendly Zendesk specific connector for QlikView and Qlik Sense.
Usage
NOTE: You will now find a more advanced example
over on GitHub which illustrates paging through and downloading all tickets in ZenDesk and storing them to a QVD file.
Firstly, locate the API section of your Zendesk Control Panel:
And ensure that either API password or token access is enabled and saved:
In our example we will use the API token method.
Now open up the
General XML/JSON API Web Connector for QlikView and enter:
https://[YOUR_ZENDESK_SUBDOMAIN].zendesk.com/api/v2/users/me.jsonInto the URI input in the connector:
Then for the username and password enter:
[YOUR_ZENDESK_EMAIL_LOGIN]/token
[YOUR_ZENDESK_API_TOKEN]
You should now be able to test the JsonToXmlRaw table and ensure that you are getting back data for your account:
We can now consult the
Zendesk API Docs to discover how to build queries for the data required. For example, to extract all the tickets in Zendesk we can enter the following URI into QVSource:
https://[YOUR_ZENDESK_SUBDOMAIN].zendesk.com/api/v2/tickets.jsonNote that the Zendesk API returns JSON so here we are using the QVSource JsonToXmlRaw to convert this data into XML which can then be read and parsed by QlikView by using the generated URL highlighted here:
As the path for a 'Web File' in the QlikView script editor.
With a little more work, we could also use JsonToTable table to generate a structured table directly for QlikView (for example in QVX format), you can read more about this
here.
Paging
The notes above offer a simple introduction but do not cover more advanced topics.
For example, from the
API docs it is seen that a maximum of 100 records are returned per page. In this case additional next_page values are included in the response and it would be up to the QlikView script developer to extract these and ensure that all pages of data were extracted (if desired).
NOTE: You will now find a more advanced example
over on GitHub which illustrates paging through and downloading all tickets in ZenDesk and storing them to a QVD file.