Zendesk Connector for PowerShell Zendesk Connector can be used to integrate Zendesk REST API in your App / BI Tools. You can read/write data about Tickets, Activity, Users, Organizations and more. In this article you will learn how to quickly and efficiently integrate Zendesk data in PowerShell without coding. We will use high-performance Zendesk Connector to easily connect to Zendesk and then access the data inside PowerShell. Let's follow the steps below to see how we can accomplish that! Download Documentation Zendesk Connector for PowerShell is based on ZappySys API Driver which is part of ODBC PowerPack. It is a collection of high-performance ODBC drivers that enable you to integrate data in SQL Server, SSIS, a programming language, or any other ODBC-compatible application. ODBC PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few.

Connect to Zendesk in other apps Connect to Zendesk in SSIS Connect to Zendesk in SQL Server Connect to Zendesk in Power BI Connect to Zendesk in SSRS Connect to Zendesk in Informatica Connect to Zendesk in MS Access Connect to Zendesk in MS Excel Connect to Zendesk in SSAS Connect to Zendesk in C# Connect to Zendesk in Python Connect to Zendesk in JAVA Connect to Zendesk in Tableau Connect to Zendesk in SAP Crystal Reports Connect to Zendesk in Azure Data Factory (Pipeline) Connect to Zendesk in Azure Data Factory (SSIS) Connect to Zendesk in Talend Studio Connect to Zendesk in UiPath Connect to Zendesk in ODBC

Create ODBC Data Source (DSN) based on ZappySys API Driver

Step-by-step instructions

To get data from Zendesk using PowerShell we first need to create a DSN (Data Source) which will access data from Zendesk. We will later be able to read data using PowerShell. Perform these steps:

1. Download and install ODBC PowerPack.

2. Open ODBC Data Sources (x64):

   

3. Create a User data source (User DSN) based on ZappySys API Driver

   ZappySys API Driver

   
   • Create and use User DSN if the client application is run under a User Account. This is an ideal option in design-time, when developing a solution, e.g. in Visual Studio 2019. Use it for both type of applications - 64-bit and 32-bit.
   • Create and use System DSN if the client application is launched under a System Account, e.g. as a Windows Service. Usually, this is an ideal option to use in a production environment. Use ODBC Data Source Administrator (32-bit), instead of 64-bit version, if Windows Service is a 32-bit application.

4. 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:

   ZendeskDSN

   Zendesk

   

5. 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.

    Token Authentication [Http]

   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 reference]

   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:

   ZendeskDSN

   Zendesk

   Token Authentication [Http]

   https://[$Domain$].zendesk.com/api/v2

   Required Parameters
   Sub Domain (e.g. mycompany)	Fill-in the parameter...
   UserId	Fill-in the parameter...
   Token	Fill-in the parameter...
   Optional Parameters
   RetryMode	RetryWhenStatusCodeMatch
   RetryStatusCodeList	429
   RetryCountMax	5
   RetryMultiplyWaitTime	True

   

    OAuth Authentication [OAuth]

   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 reference]

   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:

   ZendeskDSN

   Zendesk

   OAuth Authentication [OAuth]

   https://[$Domain$].zendesk.com/api/v2

   Required 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	RetryWhenStatusCodeMatch
   RetryStatusCodeList	429
   RetryCountMax	5
   RetryMultiplyWaitTime	True

   

    UserID/Password Authentication (2FA must be OFF) [Http]

   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 reference]

   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:

   ZendeskDSN

   Zendesk

   UserID/Password Authentication (2FA must be OFF) [Http]

   https://[$Domain$].zendesk.com/api/v2

   Required 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	RetryWhenStatusCodeMatch
   RetryStatusCodeList	429
   RetryCountMax	5
   RetryMultiplyWaitTime	True

   

6. Once the data source connection has been configured, it's time to configure the SQL query. Select the Preview tab and then click Query Builder button to configure the SQL query:

   

   ZappySys API Driver - Zendesk

   Zendesk Connector can be used to integrate Zendesk REST API in your App / BI Tools. You can read/write data about Tickets, Activity, Users, Organizations and more.

   ZendeskDSN

   

7. Start by selecting the Table or Endpoint you are interested in and then configure the parameters. This will generate a query that we will use in PowerShell to retrieve data from Zendesk. Hit OK button to use this query in the next step.

   SELECT * FROM Tickets

   
   Some parameters configured in this window will be passed to the Zendesk API, e.g. filtering parameters. It means that filtering will be done on the server side (instead of the client side), enabling you to get only the meaningful data much faster.

8. Now hit Preview Data button to preview the data using the generated SQL query. If you are satisfied with the result, use this query in PowerShell:

   

   ZappySys API Driver - Zendesk

   Zendesk Connector can be used to integrate Zendesk REST API in your App / BI Tools. You can read/write data about Tickets, Activity, Users, Organizations and more.

   ZendeskDSN

   SELECT * FROM Tickets

   
   You can also access data quickly from the tables dropdown by selecting <Select table>.
   A WHERE clause, LIMIT keyword will be performed on the client side, meaning that the whole result set will be retrieved from the Zendesk API first, and only then the filtering will be applied to the data. If possible, it is recommended to use parameters in Query Builder to filter the data on the server side (in Zendesk servers).

9. Click OK to finish creating the data source.

Video Tutorial

Read Zendesk data in PowerShell

Sometimes, you need to quickly access and work with your Zendesk data in PowerShell. Whether you need a quick data overview or the complete dataset, this article will guide you through the process. Here are some common scenarios:

• Quickly peek at Zendesk data
• Monitor data constantly in your console

• Export data to a CSV file so that it can be sliced and diced in Excel
• Export data to a JSON file so that it can ingested by other processes
• Export data to an HTML file for user-friendly view and easy sharing
• Create a schedule to make it an automatic process

• Store data internally for analysis or for further ETL processes
• Create a schedule to make it an automatic process

• Integrate data with other systems via external APIs

In this article, we will delve deeper into how to quickly view the data in PowerShell terminal and how to save it to a file. But let's stop talking and get started!

Reading individual fields

1. Open your favorite PowerShell IDE (we are using Visual Studio Code).
2. Then simply follow these instructions:
   "DSN=ZendeskDSN"

   

   For your convenience, here is the whole PowerShell script:

   # Configure connection string and query
   $connectionString = "DSN=ZendeskDSN"
   $query = "SELECT * FROM Customers"
   
   # Instantiate OdbcDataAdapter and DataTable
   $adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
   $table = New-Object System.Data.DataTable
   
   # Fill the table with data
   $adapter.Fill($table)
   
   # Since we know we will be reading just 4 columns, let's define format for those 4 columns, each separated by a tab
   $format = "{0}`t{1}`t{2}`t{3}"
   
   # Display data in the console
   foreach ($row in $table.Rows)
   {
       # Construct line based on the format and individual Zendesk fields
       $line = $format -f ($row["CustomerId"], $row["CompanyName"], $row["Country"], $row["Phone"])
       Write-Host $line
   }
   

   Access specific Zendesk table field using this code snippet:

   $field = $row["ColumnName"]

   You will find more info on how to manipulate DataTable.Rows property in Microsoft .NET reference.
   For demonstration purposes we are using sample tables which may not be available in Zendesk.
3. To read values in a console, save the script to a file and then execute this command inside PowerShell terminal:
   You can also use even a simpler command inside the terminal, e.g.:

   . 'C:\Users\john\Documents\dsn.ps1'

Retrieving all fields

However, there might be case, when you want to retrieve all columns of a query. Here is how you do it:

"DSN=ZendeskDSN"

Again, for your convenience, here is the whole PowerShell script:

# Configure connection string and query
$connectionString = "DSN=ZendeskDSN"
$query = "SELECT CustomerId, CompanyName, Country, Phone FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Display data in the console
foreach ($row in $table.Rows) {
    $line = ""
    foreach ($column in $table.Columns) {
        $value = $row[$column.ColumnName]

        # Let's handle NULL values
        if ($value -is [DBNull])
        {
            $value = "(NULL)"
        }
        $line += $value + "`t"
    }
    Write-Host $line
}

SELECT * FROM Customers LIMIT 10

Using a full ODBC connection string

In the previous steps we used a very short format of ODBC connection string - a DSN. Yet sometimes you don't want a dependency on an ODBC data source (and an extra step). In those times, you can define a full connection string and skip creating an ODBC data source entirely. Let's see below how to accomplish that in the below steps:

1. Open ODBC data source configuration and click Copy settings:
   

   ZappySys API Driver - Configuration [Version: 2.0.1.10418]

   ZappySys API Driver - Zendesk

   Zendesk Connector can be used to integrate Zendesk REST API in your App / BI Tools. You can read/write data about Tickets, Activity, Users, Organizations and more.

   ZendeskDSN

   
2. The window opens, telling us the connection string was successfully copied to the clipboard:
3. Then just paste the connection string into your script:
4. You are good to go! The script will execute the same way as using a DSN.

Limitations of using a full connection string

Despite using a full ODBC connection string may be very convenient it comes with a limitation: it's length is limited to 1024 symbols (or sometimes more). It usually happens when API provider generates a very long Refresh Token when OAuth is at play. If you are using such a long ODBC connection string, you may get this error:

"Connection string exceeds maximum allowed length of 1024"

But there is a solution to this by storing the full connection string in a file. Follow the steps below to achieve this:

1. Open your ODBC data source.
2. Click Copy settings button to copy a full connection string (see the previous section on how to accomplish that).
3. Then create a new file, let's say, in C:\temp\odbc-connection-string.txt.
4. Continue by pasting the copied connection string into a newly created file and save it.
5. Finally, the last step! Just construct a shorter ODBC connection string using this format:

   DRIVER={ZappySys API Driver};SettingsFile=C:\temp\odbc-connection-string.txt

6. Our troubles are over! Now you should be able to use this connection string in PowerShell with no problems.

Write Zendesk data to a file in PowerShell

Save data to a CSV file

Export data to a CSV file so that it can be sliced and diced in Excel:

# Configure connection string and query
$connectionString = "DSN=ZendeskDSN"
$query = "SELECT * FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Export table data to a file
$table | ConvertTo-Csv -NoTypeInformation -Delimiter "`t" | Out-File "C:\Users\john\saved-data.csv" -Force

Save data to a JSON file

Export data to a JSON file so that it can ingested by other processes (use the above script, but change this part):

# Export table data to a file
$table | ConvertTo-Json | Out-File "C:\Users\john\saved-data.json" -Force

Save data to an HTML file

Export data to an HTML file for user-friendly view and easy sharing (use the above script, but change this part):

# Export table data to a file
$table | ConvertTo-Html | Out-File "C:\Users\john\saved-data.html" -Force

Actions supported by Zendesk Connector

Learn how to perform common Zendesk actions directly in PowerShell with these how-to guides:

• Create Organization
• Create Ticket (Single)
• Create Tickets (Bulk)
• Create User
• Delete Attachment
• Delete Organization
• Delete Ticket
• Delete Tickets (Bulk)
• Delete Upload Session
• Delete User
• Read Attachment
• Read Brands
• Read Current User Info
• Read Groups
• Read Macros
• Read Organization Count
• Read Organization Fields
• Read Organization(s) by ID
• Read Organizations (All)
• Read Organizations (Incremental) changed after a specified date
• Read Requests
• Read Requests Search
• Read Sessions
• Read Tags
• Read Ticket ActivityStream
• Read Ticket ActivityStream Details
• Read Ticket Attachments
• Read Ticket Comments
• Read Ticket Events (Incremental) changed after a specified date
• Read Ticket Fields
• Read Ticket Forms
• Read Ticket Metric Events (Incremental) changed after a specified date
• Read Ticket Metrics
• Read Ticket(s) by ID
• Read Tickets (All)
• Read Tickets (Incremental) changed after a specified date
• Read Tickets (Recent)
• Read Tickets Count (All)
• Read Tickets Count (for Organization)
• Read Tickets for Organization
• Read Tickets for User (Assigned)
• Read Tickets for User (CCed)
• Read Tickets for User (Requested)
• Read User Fields
• Read User Sessions
• Read User(s) by ID
• Read Users (All)
• Read Users (Incremental) changed after a specified date
• Read Views
• Search Records - NO Sorting (Allows more than 1000 rows)
• Search Records - WITH Sorting and Extra Columns (Max 1000 rows)
• Update Organization
• Update Ticket (Single)
• Update Tickets (Bulk)
• Update User
• Upload Attachment (Single file)
• Upsert Organization - Create or Update
• Upsert User - Create or Update
• Upsert Users (Bulk) - Create or Update
• Generic Request
• Generic Request (Bulk Write)

Conclusion

In this article we showed you how to connect to Zendesk in PowerShell and integrate data without any coding, saving you time and effort. It's worth noting that ZappySys API Driver allows you to connect not only to Zendesk, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

We encourage you to download Zendesk Connector for PowerShell and see how easy it is to use it for yourself or your team.

If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.

Download Zendesk Connector for PowerShell Documentation

More integrations

Other connectors for PowerShell

Amazon Ads

Amazon Athena

Amazon Selling Partner (SP-API)

Apache Derby

Apache Hive

Apache Spark

Asana

Azure DevOps

Cosmos DB

DropBox

ElasticSearch

FastSpring

Google Ads

Google BigQuery

Google Calendar

Google Drive

Google Sheets

Hubspot

Infor Data Lake

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

MariaDB

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Starburst

Stripe

Trino

YouTube

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

Other application integration scenarios for Zendesk

SSIS

SQL Server

Power BI

SSRS

Informatica

MS Access

MS Excel

SSAS

C#

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

ODBC

Common Searches: