Zendesk Connector for Power BI
In this article you will learn how to integrate Using Zendesk Connector you will be able to connect, read, and write data from within Power BI. Follow the steps below to see how we would accomplish that. The driver mentioned above is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc. If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started. |
Connect to Zendesk in other apps
|
Video Tutorial - Integrate Zendesk data in Power BI
This video covers following and more so watch carefully. After watching this video follow the steps described in this article.
- How to download / install required driver for
Zendesk integration in Power BI - How to configure connection for
Zendesk - Features about
API Driver (Authentication / Query Language / Examples / Driver UI) - Using
Zendesk Connection in Power BI
Create ODBC Data Source (DSN) based on ZappySys API Driver
Step-by-step instructions
To get data from Zendesk using Power BI we first need to create a DSN (Data Source) which will access data from Zendesk. We will later be able to read data using Power BI. Perform these steps:
-
Install ZappySys ODBC PowerPack.
-
Open ODBC Data Sources (x64):
-
Create a User Data Source (User DSN) based on ZappySys API Driver
ZappySys API DriverYou should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version. -
When the Configuration window appears give your data source a name if you haven't done that already, then select "Zendesk" from the list of Popular Connectors. If "Zendesk" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:
ZendeskDSNZendesk -
Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.
Authenticate using Static Token instead of userid / password ([Token Access] option must be enabled under Admin Console > Channel > API > Settings and then Click [ADD API Token] to generate new token. These settings typically found here https://YOUR-SUB-DOMAIN.zendesk.com/agent/admin/api/settings [API Help..]
Please refer to below API Reference (External Site) link for Token Authentication [Http]https://developer.zendesk.com/rest_api/docs/support/introduction#api-token
Fill in all required parameters and set optional parameters if needed:
ZendeskDSNZendeskToken Authentication [Http]https://[$Domain$].zendesk.com/api/v2Required Parameters Sub Domain (e.g. mycompany) Fill in the parameter... UserId Fill in the parameter... Token Fill in the parameter... Optional Parameters RetryMode Fill in the parameter... RetryStatusCodeList Fill in the parameter... RetryCountMax Fill in the parameter... RetryMultiplyWaitTime Fill in the parameter... OAuth App must be created under Admin Console > Channel > API > Settings. These settings typically found here https://YOUR-SUB-DOMAIN.zendesk.com/agent/admin/api/oauth_clients [API Help..]
Please refer to below API Reference (External Site) link for OAuth Authentication [OAuth]https://developer.zendesk.com/rest_api/docs/support/introduction#oauth-access-token
Fill in all required parameters and set optional parameters if needed:
ZendeskDSNZendeskOAuth Authentication [OAuth]https://[$Domain$].zendesk.com/api/v2Required Parameters Sub Domain (e.g. mycompany) Fill in the parameter... ClientId Fill in the parameter... ClientSecret Fill in the parameter... Permissions Fill in the parameter... RedirectUrl Fill in the parameter... Optional Parameters RetryMode Fill in the parameter... RetryStatusCodeList Fill in the parameter... RetryCountMax Fill in the parameter... RetryMultiplyWaitTime Fill in the parameter... Authenticate using your userid / password (2FA must be OFF and [Password Access] option must be enabled under Admin Console > Channel > API > Settings. These settings typically found here https://YOUR-SUB-DOMAIN.zendesk.com/agent/admin/api/settings [API Help..]
Please refer to below API Reference (External Site) link for UserID/Password Authentication (2FA must be OFF) [Http]https://developer.zendesk.com/rest_api/docs/support/introduction#basic-authentication.
Fill in all required parameters and set optional parameters if needed:
ZendeskDSNZendeskUserID/Password Authentication (2FA must be OFF) [Http]https://[$Domain$].zendesk.com/api/v2Required Parameters Sub Domain (e.g. mycompany) Fill in the parameter... UserName (2FA Must be OFF) Fill in the parameter... Password Fill in the parameter... Optional Parameters RetryMode Fill in the parameter... RetryStatusCodeList Fill in the parameter... RetryCountMax Fill in the parameter... RetryMultiplyWaitTime Fill in the parameter... -
Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
-
Click OK to finish creating the data source.
Video instructions
Read Zendesk data in Power BI using ODBC
-
Once you open Power BI Desktop click Get Data to get data from ODBC:
-
A window opens, and then search for "odbc" to get data from ODBC data source:
-
Another window opens and asks to select a Data Source we already created. Choose ZendeskDSN and continue:
ZendeskDSN -
Most likely, you will be asked to authenticate to a newly created DSN. Just select Windows authentication option together with Use my current credentials option:
ZendeskDSN -
Finally, you will be asked to select a table or view to get data from. Select one and load the data!
-
Finally, finally, use extracted data from Zendesk in a Power BI report:
Import Zendesk data into Power BI from SQL Query
If you wish to import Zendesk data from SQL query rather than selecting table name then you can use advanced options during import steps (as below). After selecting DSN you can click on advanced options to see SQL Query editor.
If you type invalid SQL, Power BI may revert to table mode rather than import from Query. Make sure you do not use "$"
it as a table name in SELECT...FROM $
. You can use "_root_"
instead (e.g., SELECT .. FROM _root_). Consider using Custom Object to wrap custom SQL in a Virtual Table. This way, you can see a virtual table in Table mode where you can import multiple objects using the same connection rather than creating a new connection for each custom SQL.
Edit Query / Using Parameters in Power BI (Dynamic Query)
let
vKey=paraAPIKey,
Source = Odbc.Query(
"dsn=ZS-OData Customers",
"SELECT * FROM value WITH (SRC='http://httpbin.org/post',"
& "METHOD='POST',"
& "HEADER='Content-Type:application/json',"
& "BODY=@'{""CallerId"":1111, ""ApiKey"":""" & vKey & """}')")
in
Source
Edit Query Settings after Import
There will be a time you need to change initial Query after dataset import in Power BI. Not to worry, just follow these steps to edit your SQL.
Using DirectQuery Option rather than Import
So far we have seen how to Import Zendesk data into Power BI but what if you have too much data and you dont want to import but link it. Power BI Offers very useful feature for this scenario. Its called DirectQuery Option. In this section we will explore how to use DirectQuery along with ZappySys Drivers. Out of the box ZappySys Drivers wont work in ODBC Connection Mode so you have to use SQL Server Connection rather than ODBC if you wish to use Live data using DirectQuery option. See below step by step instructions to enable DirectQuery mode in Power BI for Zendesk data. Basically we will use ZappySys Data Gateway its part of ODBC PowerPack. We will then use Linked Server in SQL Server to Link API Service and then we will issue OPENROWSET queries from Power BI to SQL Server and it will then call Zendesk via ZappySys Data Gateway.Step-By-Step - How to query Zendesk API in SQL Server
- First read this article carefully, How to query Zendesk API in SQL Server.
- Once linked server is configured we are ready to issue API query in Power BI.
- Click Get Data in Power BI, select SQL Server Database
- Enter your server name and any database name
- Select Mode as DirectQuery
-
Click on Advanced and enter query like below (we are assuming you have created Zendesk Data Source in Data Gateway and defined linked server (Change name below).
Select * from OPENQUERY([ZENDESK_LINKED_SERVER],'SELECT * FROM Customers')
- Click OK and Load data ... That's it. Now your Zendesk API data is linked rather than imported.
Working with Gateways in Power BI (Schedule Import)
If the data needs to be updated, it is necessary to create a gateway on-premises. In this new section, we will install a Power BI Gateway and in the next section schedule it to update the Zendesk information.- In the last section, we Published the report. Power BI may ask you to SIGN IN.
- Select the Workspace and select Datasets
- Right-click the report and select Settings.
- The system will ask for a Gateway. Stay here.
-
Use the following link to install a Data Gateway:
https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem
- Run the installer and press Next
- Select the option On-premises data gateway (recommended). This option allows access to multiple users and can be used by more applications than Power BI.
- The installer will show a warning message.
- Select the path to install and check the I accept the terms.
- Specify the email address to use the gateway.
- After entering the email, write the gateway name and a recovery key. Make sure to confirm the recovery key.
Manage gateways and configure the schedule
Once that the gateway is installed we will configure it and add the connection strings.- The next step is to go to manage gateway
- In order to get the connection string, we will need the connection string of the ZappySys API Driver. In the first section of this post, we explained how to configure it. Press Copy Connection String
- Once that the data is copied, add a New data Source. In Data Source Name, enter the Data Source Name of the ZappySys API Driver in step 13 and in Data Source Type, select ODBC. In connection string copy and paste from the clipboard of the step 13 and press Add.
- Once added the gateway. You can see the schedule refresh to On and Add another time to add the time where you want to refresh the data.
Advanced topics
Create Custom Stored Procedure in ZappySys Driver
You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.
Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
-
Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
-
Enter the desired Procedure name and click on OK:
-
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
CREATE PROCEDURE [usp_get_orders] @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>' AS SELECT * FROM Orders where OrderDate >= '<@fromdate>';
-
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
Exec usp_get_orders '1996-01-01';
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Create Custom Virtual Table in ZappySys Driver
ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.
If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.
Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.
-
Go to Custom Objects Tab and Click on Add button and Select Add Table:
-
Enter the desired Table name and click on OK:
-
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
-
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
SELECT "ShipCountry", "OrderID", "CustomerID", "EmployeeID", "OrderDate", "RequiredDate", "ShippedDate", "ShipVia", "Freight", "ShipName", "ShipAddress", "ShipCity", "ShipRegion", "ShipPostalCode" FROM "Orders" Where "ShipCountry"='USA'
-
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
SELECT * FROM "vt__usa_orders_only"
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Actions supported by Zendesk Connector
Zendesk Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.Parameter | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sort By |
|
||||||||||||||||||||||||
Sort Order |
|
||||||||||||||||||||||||
Extra Columns to Include |
|
||||||||||||||||||||||||
External ID for Ticket |
|
||||||||||||||||||||||||
Records Per Page (Max 100) |
|
Parameter | Description | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Start Time (e.g. yyyy-MM-dd -OR- yyyy-MM-ddTHH:mm:ss) |
|
||||||||||||||||||||||||||||||||||
Exclude Deleted |
|
||||||||||||||||||||||||||||||||||
Page Size (Default 1000) |
|
Parameter | Description | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Start Time (e.g. yyyy-MM-dd -OR- yyyy-MM-ddTHH:mm:ss) |
|
||||||||||||||||||||||||||||||||||
Exclude Deleted |
|
||||||||||||||||||||||||||||||||||
Page Size (Default 1000) |
|
Parameter | Description | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Start Time (e.g. yyyy-MM-dd -OR- yyyy-MM-ddTHH:mm:ss) |
|
||||||||||||||||||||||||||||||||||
Exclude Deleted |
|
||||||||||||||||||||||||||||||||||
Page Size (Default 1000) |
|
Parameter | Description | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Start Time (e.g. yyyy-MM-dd -OR- yyyy-MM-ddTHH:mm:ss) |
|
Parameter | Description | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Start Time (e.g. yyyy-MM-dd -OR- yyyy-MM-ddTHH:mm:ss) |
|
||||||||||||||||||||||||||||||||||
Exclude Deleted |
|
||||||||||||||||||||||||||||||||||
Page Size (Default 1000) |
|
Parameter | Description |
---|---|
Ticket ID(S) - Use Comma for multiple (e.g. 111,222) |
|
Parameter | Description |
---|---|
User ID(S) - Use Comma for multiple (e.g. 111,222) |
|
Parameter | Description |
---|---|
Organization ID(S) - Use Comma for multiple (e.g. 111,222) |
|
Parameter | Description |
---|---|
Organization ID |
|
Records Per Page (Max 100) |
|
Parameter | Description |
---|---|
User ID |
|
Records Per Page (Max 100) |
|
Parameter | Description |
---|---|
User ID |
|
Records Per Page (Max 100) |
|
Parameter | Description |
---|---|
User ID |
|
Records Per Page (Max 100) |
|
Parameter | Description |
---|---|
Organization ID |
|
Parameter | Description |
---|---|
Records Per Page (Max 100) |
|
Parameter | Description |
---|
Parameter | Description | ||||||
---|---|---|---|---|---|---|---|
Ticket ID |
|
||||||
Sort Order |
|
||||||
Include inline images |
|
Parameter | Description | ||||||
---|---|---|---|---|---|---|---|
Ticket ID |
|
||||||
Sort Order |
|
||||||
Include inline images |
|
Parameter | Description |
---|---|
Since (ISO e.g. 2013-04-03T16:02:46Z) |
|
Parameter | Description |
---|---|
activity_id |
|
Parameter | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Search Criteria |
|
||||||||||||||||||||||
Sort By |
|
||||||||||||||||||||||
Sort Order |
|
||||||||||||||||||||||
Extra Columns to Include |
|
Parameter | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
FilterType |
|
||||||||||||||||||||||
Search Criteria |
|
Parameter | Description | ||||||
---|---|---|---|---|---|---|---|
Filter |
|
Parameter | Description |
---|---|
user_id |
|
Parameter | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sort By |
|
||||||||||||
Sort Order |
|
||||||||||||
Status |
|
Parameter | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sort By |
|
||||||||||||||||||||||
Sort Order |
|
||||||||||||||||||||||
Search Criteria |
|
||||||||||||||||||||||
Status |
|
||||||||||||||||||||||
organization_id |
|
||||||||||||||||||||||
cc_id |
|
Parameter | Description |
---|---|
Attachment ID |
|
Parameter | Description |
---|---|
Attachment ID |
|
Parameter | Description |
---|---|
File Name |
|
File Path (Local) |
|
Token for exising Upload Session |
|
Parameter | Description |
---|---|
Token for exising upload |
|
Parameter | Description |
---|---|
Ticket ID(S) - Use Comma for multiple (e.g. 111,222) |
|
Parameter | Description |
---|---|
Ticket ID to Update |
|
Parameter | Description |
---|---|
Ticket ID for Delete |
|
Parameter | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Role |
|
||||||||
permission_set |
|
||||||||
External ID for Ticket |
|
||||||||
Records Per Page (Max 100) |
|
Parameter | Description |
---|---|
Records Per Page (Max 100) |
|
Parameter | Description |
---|---|
User ID for Delete |
|
Parameter | Description |
---|---|
id |
|
Parameter | Description |
---|---|
Organization ID for Delete |
|
Parameter | Description |
---|---|
id |
|
Parameter | Description |
---|---|
Url |
|
Body |
|
IsMultiPart |
|
Filter |
|
Headers |
|
Zendesk Connector Examples for Power BI Connection
This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.
Get all Tickets [Read more...]
Read all tickets from Zendesk
SELECT * FROM Tickets
Get Ticket information by ID(s) [Read more...]
Read multiple ticket information from Zendesk by ID(s)
SELECT * from get_tickets_by_ids
WITH(ticket_ids='104861,104860')
Get Single Ticket information by ID [Read more...]
SELECT * from Tickets
WHERE ID=104861
Get all tickets (incremental) modified after ceratin date/time [Read more...]
Read tickets modified after ceratin date/time. This is incremental data fetch. If you use this endpoint to read data and insert to destination like SSIS Upsert Destination (ZappySys Product) then make sure you do not select delete option in the target. Only choose Update + Insert for Incremental fetch.
SELECT * FROM get_tickets_incr
WITH(
start_time='2012-01-31T00:00:00' --modified after exact date / time (yyyy-MM-dd or yyyy-MM-ddTHH:mm:ss)
--start_time='yesterday' --modified after yesterday
--start_time='now-5h' --modified after current time minus 5 hours
--start_time='today-60s' --modified after today minus 60 seconds
--start_time='weekstart' --modified after weekstart
--start_time='monthstart-1d' --modified after month start minus 1 day
--start_time='yearstart-1d' --modified after year start minus 1 day
--start_time='yearstart+1d' --modified after year start plus 1 day
--start_time='yearend+1d' --modified after year end plus 1 day
)
Get all users (incremental) modified after ceratin date/time [Read more...]
Read users modified after ceratin date/time. This is incremental data fetch. If you use this endpoint to read data and insert to destination like SSIS Upsert Destination (ZappySys Product) then make sure you do not select delete option in the target. Only choose Update + Insert for Incremental fetch.
SELECT * FROM get_users_incr
WITH(
start_time='2012-01-31T00:00:00' --modified after exact date / time (yyyy-MM-dd or yyyy-MM-ddTHH:mm:ss)
--start_time='yesterday' --modified after yesterday
--start_time='now-5h' --modified after current time minus 5 hours
--start_time='today-60s' --modified after today minus 60 seconds
--start_time='weekstart' --modified after weekstart
--start_time='monthstart-1d' --modified after month start minus 1 day
--start_time='yearstart-1d' --modified after year start minus 1 day
--start_time='yearstart+1d' --modified after year start plus 1 day
--start_time='yearend+1d' --modified after year end plus 1 day
)
Get all organizations (incremental) modified after ceratin date/time [Read more...]
Read organizations modified after ceratin date/time. This is incremental data fetch. If you use this endpoint to read data and insert to destination like SSIS Upsert Destination (ZappySys Product) then make sure you do not select delete option in the target. Only choose Update + Insert for Incremental fetch.
SELECT * FROM get_organizations_incr
WITH(
start_time='2012-01-31T00:00:00' --modified after exact date / time (yyyy-MM-dd or yyyy-MM-ddTHH:mm:ss)
--start_time='yesterday' --modified after yesterday
--start_time='now-5h' --modified after current time minus 5 hours
--start_time='today-60s' --modified after today minus 60 seconds
--start_time='weekstart' --modified after weekstart
--start_time='monthstart-1d' --modified after month start minus 1 day
--start_time='yearstart-1d' --modified after year start minus 1 day
--start_time='yearstart+1d' --modified after year start plus 1 day
--start_time='yearend+1d' --modified after year end plus 1 day
)
Get all tickets for specific organization [Read more...]
Read tickets for a specified organization_id (company).
SELECT * FROM get_tickets_by_org
WITH(
organization_id='12'
)
Get all tickets for a specific user who requested ticket(s) [Read more...]
Read tickets for a specified user_id who is listed as requested by.
SELECT * FROM get_tickets_for_user_requested
WITH(
user_id='123'
)
Get all tickets for a specific user who is CCed on ticket(s) [Read more...]
Read tickets for a specified user_id who is listed as CC.
SELECT * FROM get_tickets_for_user_cced
WITH(
user_id='123'
)
Get all tickets for a specific user who is assigned to ticket(s) [Read more...]
Read tickets for a specified user_id who is assigned to ticket(s).
SELECT * FROM get_tickets_for_user_assigned
WITH(
user_id='123'
)
Get total tickets count [Read more...]
SELECT * FROM get_tickets_count
Get total tickets count for a specific organization [Read more...]
SELECT * FROM get_tickets_count_org
WITH(
organization_id='123'
)
Get all attachment urls for a specific ticket [Read more...]
SELECT * FROM get_ticket_attachments
WITH(
ticket_id='104351'
)
Get User(s) [Read more...]
SELECT * FROM Users --Where Id=1234
Get multiple users by ID(s) [Read more...]
Read multiple user information from Zendesk by ID(s)
SELECT * from get_users_by_ids
WITH(user_ids='1111,2222,3333')
Get Organization(s) [Read more...]
SELECT * FROM Organizations --Where Id=1234
Get multiple organizations by ID(s) [Read more...]
Read multiple organization information from Zendesk by ID(s)
SELECT * from get_organizations_by_ids
WITH(organization_ids='1111,2222,3333')
Create a new ticket [Read more...]
Use Tickets_Bulk instead of Tickets table if you like to multiple tickets at once. Tickets_Bulk table supports BULK operation (using SOURCE clause).
INSERT INTO Tickets(
subject
,status
,assignee_id
,comment_body_html --(for html body)
--,comment_body (for plain text)
,comment_public
,tags
,custom_fields)
VALUES(
'Test Ticket Subject - From email'
, 'new' --new, solved, closed
, 18590685428 --assign to agent id
, 'This is <b>html body</b>' --markup also supported
, 1 --1=public, 0=private
, '["tag1","tag2"]'
--below json can be obtained using select custom_fields from tickets where id=1234
, '[
{
"id": 56608448,
"value": "1122"
},
{
"id": 57385967,
"value": "ORD-12345"
}
]'
)
Create a new ticket (behalf of user) [Read more...]
This example creates ticket behalf of user (i.e. requester_email and requester_name) and if user is missing then creates a new user for supplied username and email. Use Tickets_Bulk instead of Tickets table if you like to multiple tickets at once. Tickets_Bulk table supports BULK operation (using SOURCE clause).
INSERT INTO Tickets(
subject
,status
,requester_email
,requester_name
,assignee_id
--,group_id --or assign to group
,comment_body_html --(for html body)
--,comment_body (for plain text)
,comment_public
,tags
,custom_fields)
VALUES(
'Test Ticket Subject - From email'
, 'new' --new, solved, closed
, 'fromsomeuser@abc.com' --from email
, 'Bob Smith' --submitter name needed if its new user
, 18590685428 --assign to agent id
--,123435454 --or use group id if not assignee
, 'This is <b>html body</b>' --markup also supported
--, 'This is plain text'
, 1 --1=public, 0=private
, '["tag1","tag2"]'
--below json can be obtained using select custom_fields from tickets where id=1234
, '[
{
"id": 56608448,
"value": "1122"
},
{
"id": 57385967,
"value": "ORD-12345"
}
]'
)
BULK Create tickets (BULK read / write from external source) [Read more...]
This examples shows how to use SOURCE clause to read data from MS SQL Server (or other external system) and send data to Zendesk using Bulk API
INSERT INTO Tickets_BULK
SOURCE(
'MSSQL' --ODBC or OLEDB
,'Data Source=localhost;Initial Catalog=Test;Integrated Security=true'
,'select ''Test Subject#1'' as subject,''new'' as status,''this is description#1'' as comment_body from Projects'
)
Delete a ticket by Id [Read more...]
DELETE FROM Tickets WHERE Id=111
Delete multiple by tickets by Id list - BULK (comma seperated - max 100 ids) [Read more...]
DELETE FROM Tickets_Bulk WHERE [$$ticket_ids]='111,222,333'
Update ticket by Id [Read more...]
Update Tickets
SET subject='Test ticket subject'
, tags='["tag1","tag2"]'
--, additional_tags ='["tag1","tag2"]' --tags you like to remove
--, remove tags='["tag1","tag2"]'
, status='pending' --new, solved, closed
--below json can be obtained using select custom_fields from tickets where id=1234
, custom_fields='[
{
"id": 10000,
"value": "some value for prop1"
},
{
"id": 10001,
"value": "some value for prop2"
}
]'
Where Id = 1234
Update exising ticket with private comment [Read more...]
Update Tickets
SET comment_body='Closing this ticket'
, comment_public = 0 --or 1
, status='solved' --pending, new, closed
--, comment_body_html='Closing <b>this</b> ticket'
--, comment_author_id=123545
Where Id = 1234
Update exising ticket with HTML body [Read more...]
Update Tickets
SET comment_body_html='Closing <b>this</b> ticket'
, status='solved' --pending, new, closed
--, comment_author_id=123545
--, comment_public = 0 --or 1
Where Id = 1234
Update ticket with Add or remove tags [Read more...]
Update ticket with Add new tags or remove tags. Adding / removing tags available via special field names only in BULK mode so you must use Tickets_BULK table.
Update Tickets_Bulk
SET subject='New subject'
, additional_tags ='["new-tag1","new-tag2"]' --//add some tags
--, remove_tags='["old-tag1","old-tag2"]' --//removes some tags
--, tags='["tag1","tag2"]' --//overwrite all tags
, status='pending' --new, solved, closed
Where Id = 1234
Update multiple tickets - (BULK read / write from external source) [Read more...]
This examples shows how to perform bulk update using SOURCE clause. It reads data from external system (in this example MS SQL Server) and sends data to Zendesk using Bulk API
UPDATE Tickets_BULK
SOURCE(
'MSSQL' --ODBC or OLEDB
,'Data Source=localhost;Initial Catalog=Test;Integrated Security=true'
,'select 104897 as Id, ''Test Subject#1-updated-bulk-demo'' as subject,''new'' as status
UNION
select 104898 as Id, ''Test Subject#2-updated-bulk-demo'' as subject,''new'' as status'
)
Delete multiple tickets - (BULK read / write from external source) [Read more...]
This examples shows how to perform bulk delete using SOURCE clause. It reads data from external system (in this example MS SQL Server) and sends data to Zendesk using Bulk API
DELETE FROM Tickets_BULK
SOURCE(
'MSSQL' --ODBC or OLEDB
,'Data Source=localhost;Initial Catalog=Test;Integrated Security=true'
,'select 104897 as Id
UNION
select 104898 as Id'
)
Create a new ticket using Raw JSON Body approach [Read more...]
INSERT INTO Tickets(_rawdoc_)
VALUES(
'{
"subject": "Test ticket #1",
"comment": {
"body": "Test ticket #1"
},
"priority": "urgent"
}'
)
Update an existing ticket using Raw JSON Body approach [Read more...]
UPDATE Tickets
SET _rawdoc_ =
'{
"subject": "Test ticket #1",
"comment": {
"body": "Test ticket #1"
},
"priority": "urgent"
}'
WHERE Id=1234
Create multiple ticket(s) using a RAW JSON body (single or multiple) [Read more...]
INSERT INTO Tickets_Bulk(_rawdoc_)
VALUES(
'[
{
"subject": "Test ticket #1",
"comment": {
"body": "Test ticket #1"
},
"priority": "urgent"
},
{
"subject": "Test ticket #2",
"comment": {
"body": "This is a comment for #2"
},
"priority": "normal"
}
]'
)
Create User [Read more...]
Create a new user for specified email id and other information. If user with same email exists then call fails.
INSERT INTO Users
(
name
,email
,organization_id
,phone
,default_group_id
,locale
,moderator
,skip_verify_email
,only_private_comments
,signature
,tags
,time_zone
,role
,external_id
,alias
,details
,notes
,remote_photo_url
,user_fields
)
VALUES(
'Bob Walton'
,'bob@abc.com'
,5397098432795
,'111-222-3333'
,114094762733
,'en-US'
,'false'
,'true' --true=do not send verify account email
,1 --user can put only private comments
,'Best regards, Support Team' --Only agents and admins can have signatures
,'["paid","trial","solved"]'
,'America/New_York'
,'end-user' --agent or admin
,'zcrm_1558554000052161270'
,'some alias'
,'some details'
,'some notes'
,'https://zappysys.com/wp-content/uploads/2021/10/Slider-API-Hub-1.png' --this does not work in INSERT (works only in UPDATE/UPSERT for now)
,'{"birthdate": "1981-01-23", "gender": "M"}'
)
Update User [Read more...]
UPDATE Users
SET name='Sam Walton'
,email='sam@abc.com'
,organization_id=5397098432795
,phone='111-222-3333'
,default_group_id=114094762733
,locale='en-US'
,skip_verify_email='true' --do not send verify account email
,moderator='false'
,only_private_comments=1 --user can put only private comments
,signature='Best regards, Support Team' --Only agents and admins can have signatures
,tags='["paid","trial","solved"]'
,time_zone='America/New_York'
,role='end-user'
,external_id='zcrm_1558554000052161269'
,alias='some alias'
,details='some details'
,notes='some notes'
,remote_photo_url='https://zappysys.com/wp-content/uploads/2021/10/Slider-API-Hub-1.png'
,user_fields='{"birthdate": "1981-01-23", "gender": "M"}'
Where id=21811221397915
Upsert User (Create or Update) [Read more...]
Creates a user if the user does not already exist, or updates an existing user identified by e-mail address or external ID.
INSERT INTO Users
(
name
,email
,organization_id
,phone
,default_group_id
,locale
,moderator
,skip_verify_email
,only_private_comments
,signature
,tags
,time_zone
,role
,external_id
,alias
,details
,notes
,remote_photo_url
,user_fields
)
VALUES(
'Bob Walton'
,'bob@abc.com'
,5397098432795
,'111-222-3333'
,114094762733
,'en-US'
,'false'
,'true' --true=do not send verify account email
,1 --user can put only private comments
,'Best regards, Support Team' --Only agents and admins can have signatures
,'["paid","trial","solved"]'
,'America/New_York'
,'end-user' --agent or admin
,'zcrm_1558554000052161270'
,'some alias'
,'some details'
,'some notes'
,'https://zappysys.com/wp-content/uploads/2021/10/Slider-API-Hub-1.png' --this does not work in INSERT (works only in UPDATE/UPSERT for now)
,'{"birthdate": "1981-01-23", "gender": "M"}'
)
Delete User [Read more...]
DELETE FROM Users Where id=21855694556443 --it doesnt delete user from system but only changes active flag
Search for user with email id [Read more...]
SELECT *
FROM get_search
WITH(
query='type:user email:bob@abc.com'
)
Create Organization [Read more...]
Create a new organization for specified email id and other information. If organization with same email exists then call fails.
INSERT INTO Organizations
(
name
,external_id
,group_id
,tags
,details
,notes
,organization_fields
,domain_names
,shared_tickets
,shared_comments
)
VALUES(
'Abc Inc'
,'zcrm_1558554000052161270' --external_id
,114094762733
,'["paid","trial","solved"]'
,'some details'
,'some notes'
,'{"startdate": "1981-01-23", "revenue": 12000000.50, "somenumber": 1235678}'
,'["aaa.com", "bbb.com"]'
,'false'
,'false'
)
Update Organization [Read more...]
UPDATE Organizations
SET name='Abc Inc'
,external_id='zcrm_1558554000052161270'
,group_id=114094762733
,tags='["paid","trial","solved"]'
,details='some details'
,notes='some notes'
,organization_fields='{"startdate": "1981-01-23", "revenue": 12000000.50, "somenumber": 1235678}'
,domain_names='["aaa.com", "bbb.com"]'
,shared_tickets='false'
,shared_comments='false'
Where id=21863188631451
Upsert Organization (Create or Update) [Read more...]
Creates an organization if the organization does not already exist, or updates an existing organization identified by e-mail address or external ID.
UPSERT INTO Organizations
(
name
--id or external_id can be supplied for UPSERT
,id
--or--
,external_id
,group_id
,tags
,details
,notes
,organization_fields
,domain_names
,shared_tickets
,shared_comments
)
VALUES(
'Abc Inc'
,1234567 --id
--or--
,'zcrm_1558554000052161270' --external_id
,114094762733
,'["paid","trial","solved"]'
,'some details'
,'some notes'
,'{"startdate": "1981-01-23", "revenue": 12000000.50, "somenumber": 1235678}'
,'["aaa.com", "bbb.com"]'
,'false'
,'false'
)
Delete Organization [Read more...]
DELETE FROM Organizations Where id=21855694556443
Search records using query expression (tickets, organization, users) [Read more...]
SELECT *
FROM get_search --limited to 1000 rows max
--OR
--FROM get_search_export --returns more than 1000 rows but no sorting or extra column allowed
WITH(
filtertype='', --can be ticket, organization, user, group. If you set here then no need to put in query (e.g. query='type:ticket ...'). This option is ignored for get_search_Export.
,sort_by='updated_at' --created_at, status, priority, ticket_type. This option is ignored for get_search_Export.
,sort_order='asc' --desc (not valid for get_search_export). This option is ignored for get_search_Export.
--read this for more information
--https://support.zendesk.com/hc/en-us/articles/4408883318554-Searching-users-groups-and-organizations
--https://support.zendesk.com/hc/en-us/articles/4408886879258-Zendesk-Support-search-reference#topic_crj_yev_uc
--https://support.zendesk.com/hc/en-us/articles/4408882086298-Searching-tickets
,query='type:ticket subject:"Upsert Destination"' --search tickets where subject contains phrase "Upsert Destination" (special characters like comma / dash etc ignored in match)
--,query='type:ticket 519872' --search ticket with id 519872
--,query='type:ticket tags:solved,odbc_powerpack updated>1months' --search tickets where two tags set solved,odbc_powerpack and updated in last one month
--,query='type:ticket -tags:odbc_powerpack updated>1months' --search tickets where where tags not like odbc_powerpack and updated in last one month
--,query='type:ticket status<solved created>1months' --search tickets with status not solved and created in last one month
--,query='type:ticket created:2014-08-01' --search tickets created on 2014-08-01 (UTC)
--,query='type:ticket created>2014-08-01T10:30:00Z created<2014-08-01T12:00:00Z' --search tickets created between two datetime (UTC time)
--,query='type:ticket requester:amy@mondocam.com' --search tickets where requester is amy@mondocam.com
--,query='type:ticket description:defective' --search tickets where decription contains word "defective"
--,query='type:ticket description:"product is defective"' --search tickets where decription contains phrase "product is defective"
--,query='type:ticket priority>low' --search tickets where priority greater than low (e.g. medium or high)"
--,query='ZappySys' --phrase match (no type): anywhere in ticket / organization / user contains ZappySys word - If filtertype parameter supplied then only those type included
--,query='ZappySys*' --phrase match (no type): wildcard usage
--,query='type:user "ZappySys"' --search users with term "ZappySys" anywhere in text properties
--,query='type:user email:"@zappysys"' --search users with term "@ZappySys.com" in email field
--,query='type:user name:"zappysys"' --search users with term "ZappySys" in name field
--,query='type:user details:"zappysys"' --search users with term "ZappySys" in details field
--,query='type:organization "ZappySys LLC"' --phrase match: organization name contains ZappySys LLC
)
Bulk Import Mode for Users or Organizations [Read more...]
This example shows how to upsert in bulk mode from external data and import into Zendesk. We used Microsoft SQL Server as source system in below example with static value query (just one row) but it can be any number of rows.
UPSERT INTO Organizations
SOURCE('MSSQL' --ODBC
, 'Data Source=localhost;Initial Catalog=test;Integrated Security=true'
--For bulk input, map columns in External Query (Must use alias column name to match INSERT command Input Column names - see help file)
--If parameter value not same for all input rows then you can prefix some column with $$ to map as parameter (i.e. $$MyParam1)
--'ODBC', 'Driver={ZappySys CSV Driver};DataPath=C:\AccountsToInsert.csv'
--'ODBC', 'DSN=MyDSN'
--'OLEDB', 'Provider=SQLNCLI11;Server=localhost,1433;Database=tempdb;Trusted_Connection=yes;'
, 'select
21863188631451 as id
, ''Abc Inc'' as name
,''zcrm_1558554000052161270'' as external_id
,114094762733 as group_id
,''["paid","trial","solved"]'' as tags
,''some details'' as details
,''some notes'' as notes
,''{"startdate": "1981-01-23", "revenue": 12000000.50, "somenumber": 1235678}'' as organization_fields
,''["aaa.com", "bbb.com"]'' domain_names
,''false'' as shared_tickets
,''false'' as shared_comments
')
Conclusion
In this article we discussed how to connect to Zendesk in Power BI and integrate data without any coding. Click here to Download Zendesk Connector for Power BI and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).
Download Zendesk Connector for Power BI
Documentation
More integrations
Other application integration scenarios for Zendesk
Other connectors for Power BI
Download Zendesk Connector for Power BI
Documentation
How to connect Zendesk in Power BI?
How to get Zendesk data in Power BI?
How to read Zendesk data in Power BI?
How to load Zendesk data in Power BI?
How to import Zendesk data in Power BI?
How to pull Zendesk data in Power BI?
How to push data to Zendesk in Power BI?
How to write data to Zendesk in Power BI?
How to POST data to Zendesk in Power BI?
Call Zendesk API in Power BI
Consume Zendesk API in Power BI
Zendesk Power BI Automate
Zendesk Power BI Integration
Integration Zendesk in Power BI
Consume real-time Zendesk data in Power BI
Consume real-time Zendesk API data in Power BI
Zendesk ODBC Driver | ODBC Driver for Zendesk | ODBC Zendesk Driver | SSIS Zendesk Source | SSIS Zendesk Destination
Connect Zendesk in Power BI
Load Zendesk in Power BI
Load Zendesk data in Power BI
Read Zendesk data in Power BI
Zendesk API Call in Power BI