Azure Data Factory (ADF) Zendesk Connector
In this article you will learn how to integrate Using Zendesk Connector you will be able to connect, read, and write data from within Azure Data Factory (ADF). Follow the steps below to see how we would accomplish that. Driver mentioned in this article 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. |
See also
|
Create ODBC Data Source (DSN) based on ZappySys API Driver
To get data from Zendesk using Azure Data Factory (ADF) we first need to create a DSN (Data Source) which will access data from Zendesk. We will later be able to read data using Azure Data Factory (ADF). Perform these steps:
-
Install ZappySys ODBC PowerPack.
-
Open ODBC Data Sources (x64):
-
Create a System Data Source (System 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. Furthermore, a User DSN may be created instead, but then you will not be able to use the connection from Windows Services (or any application running under a Windows System Account). -
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 [Read more..]
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:
ZendeskDSNToken Authentication [Http]https://[$Domain$].zendesk.com/api/v2Required Parameters Domain 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 [Read more..]
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:
ZendeskDSNOAuth Authentication [OAuth]https://[$Domain$].zendesk.com/api/v2Required Parameters Domain 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 [Read more..]
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:
ZendeskDSNUserID/Password Authentication (2FA must be OFF) [Http]https://[$Domain$].zendesk.com/api/v2Required Parameters Domain 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.
Read data in Azure Data Factory (ADF) from ODBC datasource (Zendesk)
-
To start press New button:
-
Select "Azure, Self-Hosted" option:
-
Select "Self-Hosted" option:
-
Set a name, we will use "OnPremisesRuntime":
-
Download and install Microsoft Integration Runtime.
-
Launch Integration Runtime and copy/paste Authentication Key from Integration Runtime configuration in Azure Portal:
-
After finishing registering the Integration Runtime node, you should see a similar view:
-
Go back to Azure Portal and finish adding new Integration Runtime. You should see it was successfully added:
-
Go to Linked services section and create a new Linked service based on ODBC:
-
Select "ODBC" service:
-
Configure new ODBC service. Use the same DSN name we used in the previous step and copy it to Connection string box:
ZendeskDSNDSN=ZendeskDSN -
For created ODBC service create ODBC-based dataset:
-
Go to your pipeline and add Copy data connector into the flow. In Source section use OdbcDataset we created as a source dataset:
-
Then go to Sink section and select a destination/sink dataset. In this example we use precreated AzureBlobStorageDataset which saves data into an Azure Blob:
-
Finally, run the pipeline and see data being transferred from OdbcDataset to your destination dataset:
Create Custom Store 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 Store 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 Store Procedure and write the your desired store procedure and Save it and it will create the custom store 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 Store 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 store 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 store 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.
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 store 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 store procedure and provide you the response.
Conclusion
In this article we discussed how to connect to Zendesk in Azure Data Factory (ADF) and integrate data without any coding. Click here to Download Zendesk Connector for Azure Data Factory (ADF) 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 Azure Data Factory (ADF)
Documentation
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 |
|
Parameter | Description | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Start Time (e.g. yyyy-MM-dd -OR- yyyy-MM-ddTHH:mm:ss) |
|
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 |
|
Parameter | Description |
---|---|
User ID |
|
Parameter | Description |
---|---|
User ID |
|
Parameter | Description |
---|---|
User ID |
|
Parameter | Description |
---|---|
Organization ID |
|
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 |
---|---|
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 |
|
Parameter | Description |
---|---|
Url |
|
Body |
|
IsMultiPart |
|
Filter |
|
Headers |
|
Other App Integration scenarios for Zendesk
Other Connectors for Azure Data Factory (ADF)
Download Zendesk Connector for Azure Data Factory (ADF)
Documentation
How to connect Zendesk in Azure Data Factory (ADF)?
How to get Zendesk data in Azure Data Factory (ADF)?
How to read Zendesk data in Azure Data Factory (ADF)?
How to load Zendesk data in Azure Data Factory (ADF)?
How to import Zendesk data in Azure Data Factory (ADF)?
How to pull Zendesk data in Azure Data Factory (ADF)?
How to push data to Zendesk in Azure Data Factory (ADF)?
How to write data to Zendesk in Azure Data Factory (ADF)?
How to POST data to Zendesk in Azure Data Factory (ADF)?
Call Zendesk API in Azure Data Factory (ADF)
Consume Zendesk API in Azure Data Factory (ADF)
Zendesk Azure Data Factory (ADF) Automate
Zendesk Azure Data Factory (ADF) Integration
Integration Zendesk in Azure Data Factory (ADF)
Consume real-time Zendesk data in Azure Data Factory (ADF)
Consume realtime Zendesk API data in Azure Data Factory (ADF)
Zendesk ODBC Driver | ODBC Driver for Zendesk | ODBC Zendesk Driver | SSIS Zendesk Source | SSIS Zendesk Destination
Connect Zendesk in Azure Data Factory (ADF)
Load Zendesk in Azure Data Factory (ADF)
Load Zendesk data in Azure Data Factory (ADF)
Read Zendesk data in Azure Data Factory (ADF)
Zendesk API Call in Azure Data Factory (ADF)