Make informed and strategic decisions by adding a Zendesk integration to your Grow dashboard. Zendesk helps you visualize your team's task and project management and track customer communication. The Grow/Zendesk integration improves your reliability, your customers' satisfaction, and your effectiveness in accomplishing what needs to get done.
Zendesk is on the Grow Datawarehouse, which we highly recommend you use. Here is the link to the Data Warehouse Help Article.
Warehouse Tables
We pull in all the main tables from the Zendesk API.
These tables include:
- Organizations
- Ratings
- Surveys
- Tickets
- Users
These 5 Zendesk API tables are available in Grow.
Connecting to Zendesk
Before starting, please collect your Dropbox username (email address) and password.
- Click on the Data tab at the top left of the global navigation. Then click on Connections in the Data Library section.
- Click on the blue Connect button and search for Zendesk.
- Click on the Zendesk logo.
- On the new pop-up screen, you will need to enter your Subdomain (e.g., bacana.zendesk.com).
- After this, it will ask for your Zendesk user credentials.
You are ready to start building!
Endpoints
Here you will find each report Zendesk offers in Grow, along with a short description of each.
- Organizations: List of the organizations in Zendesk along with their details.
- Satisfaction Ratings: List of all your satisfaction ratings in a given time period. Satisfaction ratings must be enabled.
- Search: Returns data based on queries. To learn more about the Search report for Zendesk, read the FAQ section.
- Search Count: The number of searches of various resource types, based on the queries you enter.
- Tags: Shows the number of times a tag has been used in Zendesk.
- Tickets: All the information about your tickets in Zendesk.
- Ticket Metrics: Show the times at which tickets were created, updated, resolved, or closed in Zendesk
- Users: All the information about anyone (any user) who has interacted with your Zendesk (submitted a ticket, customers, agents within your organization).
- Views (all): Shows the status (view) types and the settings for each one.
- Views (Detailed): Shows the settings and information for one specific view type.
- Organizational Membership: See which organizations your users belong to.
Zendesk API Docs
https://developer.zendesk.com/rest_api/docs/zendesk-apis/resources
You shouldn't need to look at these very often.
FAQs + Tips & Tricks
Zendesk Search: is the most powerful report type you can use in Zendesk. This also makes it a little complex to use.
The Search report returns tickets, users, and organizations. You can use queries and filters to narrow your search results according to resource type, dates, and object properties, such as ticket requester or tag.
Start out with some of the example queries below to see what Search can do, then try writing your own queries with other filters. If you want to add multiple criteria, just separate each one with a space. You can find a list of filters that work in Zendesk's API documentation.
Below are a few examples.
- What you want: Open tickets
- Search Query: query=type:ticket status:open
- What you want: Tickets created in the last month
- Search Query: query=created_at>={{date('-30days','YYYY-MM-DD')}} type:ticket
- What you want: Solved tickets
- Search Query: query=solved>={{date('-30days','YYYY-MM-DD')}} type:ticket
- What you want: Tickets created for a specific organization for all time
- Search Query: query=type:ticket organization:xxxxx
- With the organization, each one should have a five-digit number that you will enter where the five x-es are above.
Zendesk can take up to a few minutes for new tickets, users, and other resources to be indexed for search. If your expected results don't immediately appear in your search results, wait a few minutes for Zendesk to catch up, and try again.
The Search Count report returns how many times tickets, users, and organizations in your Zendesk have been searched in a given time period. You use the same search queries for each resource type (i.e. solved tickets, open tickets, organizations) to display the search count for that specific resource.