Installing and using the Zendesk apps tools

Developing Zendesk apps without some local testing tools is possible but not easy. For example, each time you want to test a change, you have to package and upload the app and then install and run it remotely in Zendesk Support. To get around this problem, you can use a collection of local development tools called Zendesk Apps Tools (ZAT). Among other tasks, ZAT lets you do the following:

• Automatically create all the necessary files and folders for a new app
• Test your app locally in a browser
• Validate your app
• Package your app for upload

This article explains how to install and use the tools on the command line in macOS, Ubuntu for Windows 10, and Windows. It covers the following topics:

• Using the command line
• Installing Ruby
• Installing ZAT
• Updating ZAT
• Using ZAT
• ZAT server limitations

Windows 10 users: Zendesk recommends using Ubuntu for Windows 10 as your apps development environment. Ubuntu is an open-source Linux operating system you can install in Windows 10 from the Microsoft Store. For installation instructions, see Setting up a Bash shell in Windows 10.

See the known issues if you run into any problems installing or using the tools.

If you're just starting out building apps, see Building your first Zendesk app, a five-part tutorial series that teaches you how to build an app from start to finish.

Using the command line

ZAT is a command-line application. You type commands at the command line to accomplish different tasks. Example:

$ zat new

Note: In Windows, the prompt is C:\> instead of $.

This section describes how to open the default command line interface of each operating system.

Working in macOS

In macOS, you can run ZAT commands using Terminal, which is a Bash shell.

To open Terminal

• Double-click the Terminal application in your Applications/Utilities folder.

Working in Ubuntu for Windows 10

In Ubuntu for Windows 10, use the default Bash shell to run ZAT commands.

To open the Bash shell

1. Open the Windows Start Menu, type cmd in the search box, press Enter to open the command prompt.
2. Run the following command at the command prompt:

   c:\> bash

   Example:

   

Working in Windows

In native Windows, use the command prompt to run ZAT commands.

To open the command prompt

• Open the Start Menu, type cmd in the search box, and press Enter.

  Example:

  

Installing Ruby

ZAT is a Ruby gem -- a self-contained package of Ruby code that extends Ruby. You don't need to know Ruby to use the tools but you do need to install Ruby to install the gem.

ZAT supports Ruby 2.1 or later.

Ruby may already be installed your system. Open your command-line interface and run the following command:

$ ruby -v

You should see something like the following response:

If you get an error, Ruby is not installed. If the result is a Ruby version earlier than 2.1, you'll need to update it. If the result is Ruby 2.1 or better, you don't need to do anything. Skip to Installing the ZAT gem.

Important: Zendesk can't provide support for third party technologies like package managers and Ruby installers. If you run into trouble, try searching for the error message in Google. User forums provide the answers to most Ruby questions.

Installing Ruby in macOS

Ruby is included with all modern versions of macOS (10.9 and later). If you have Ruby 2.1 or later, you can skip this section and go to Installing ZAT.

If you need to update Ruby, see Managing Ruby versions.

Installing Ruby in Ubuntu for Windows 10

Ruby is included with Ubuntu for Windows 10. If you have Ruby 2.1 or later, you can skip this section and go to Installing ZAT.

If you need to update Ruby, see Managing Ruby versions.

Installing Ruby in Windows

Note: Ruby 2.4 or later for Windows has a dependency issue that prevents ZAT from working. Install an earlier version such as Ruby 2.2 or 2.3, or consider using Ubuntu for Windows 10 as your development environment. For installation instructions, see Setting up a Bash shell in Windows 10.

You need to install both Ruby and the Ruby Development Kit (DevKit) on Windows. Ruby 2.2 is used as an example. (Ruby 2.4 or later is not supported.)

To install Ruby

1. Go to http://rubyinstaller.org/downloads/ and download the Ruby 2.2 or later installer.
   Note: As of March 2017, the 32-bit version of Ruby is recommended even for 64-bit systems.
2. Double-click the downloaded file and follow the instructions.
3. Add the Ruby bin folder (C:\Ruby22\bin) to your system Path variable.

   At the end of the path, add a semi-colon (;) to the last entry and then add C:\Ruby22\bin:

   ...;C:\Ruby22\bin

   See How to set the path and environment variables in Windows on the computerhope.com website.

4. Test the installation by checking the version number at the command line:

   C:\> ruby -v

To install DevKit (Ruby 2.2)

1. Return to http://rubyinstaller.org/downloads/ and download the Development Kit.
2. Double-click the DevKit installer and extract the files to C:\Ruby22.
3. At the command line, navigate to your Ruby folder and run the following command:

   C:\Ruby22> ruby dk.rb init

4. Install the DevKit with the following command:

   C:\Ruby22> ruby dk.rb install

5. Finally, update your gems with the following command:

   C:\Ruby22> gem update --system && gem update

   If prompted, update rake.

Installing ZAT

Note: If you're using macOS or Ubuntu and any of the following commands complains that you don't have write permissions for a directory, start the command with sudo to request admin privileges, then enter the password for your system when prompted. Example: $ sudo gem install rake.

First, install rake, a build automation tool, with the following command in your command-line interface:

$ gem install rake

Next, install ZAT with the following command:

$ gem install zendesk_apps_tools

The ZAT gem and a number of supporting gems are installed, along with related documentation.

Updating ZAT

Zendesk updates ZAT from time to time. To get the latest version, run the following command:

$ gem update zendesk_apps_tools

Using ZAT

The ZAT tools let you do the following:

• Create starter files for a new app
• Test your app locally in a browser
• Validate your app
• Packaging your app for upload to Zendesk Support

Creating starter files for a new app

You can automatically create basic starter files and folders for a new app.

To create the files

1. In the command-line interface, navigate to the folder where you want the app files to be saved in a subfolder.

   Use the cd command (for change directory) to navigate to a child folder. Example:

   $ cd zendesk_app_projects

   To back up one directory, use cd followed by a space and two periods. Example:

   cd ..

2. Run the following command:

   $ zat new

   The command creates a set of starter files to use with the Zendesk Apps framework v2 (ZAF v2). To learn more, see the ZAF v2 documentation.

3. At the prompts, enter your name and email, the app's name, the URL of the file to be iframed (if any), and a folder name for the app.

   ZAF v2 apps are iframe apps. If you don't specify the URL to an iframe file, ZAT will create a basic HTML file that you can use in an iframe.

   The tool creates and lists the files. The window should look as follows in macOS:

   

Testing your app locally in a browser

You can start a local HTTP server and run your app locally. This ability is essential for testing and debugging your app. You don't have to package and upload the app to Zendesk Support first.

This feature is supported in Chrome and Firefox, but not Safari 9 or later. To test your app locally, ZAT runs a local http server and loads the app in the Zendesk Support https page. This results in mixed content. Chrome and Firefox block mixed content but provide a way to turn off the blocking. Starting with version 9, Safari also blocks mixed content but doesn't provide a way to turn off blocking.

Some features may not work locally. See ZAT server limitations.

To test your app locally

1. In the command-line interface, navigate to the folder containing the app files.
2. Start the local HTTP server with the following command:

   $ zat server

   If you get an error, make sure you navigate to your app's folder using the command line. You can start the server from a different folder by specifying the relative path to the files:

   $ zat server --path /tmp/test-app

   After a moment, a status message appears informing you that the server has started. Example:

   

   Note: The command prompt is unavailable until you shut down the server later.
3. In your favorite browser, navigate to any ticket in Zendesk Support. The URL should look something like this:

   https://subdomain.zendesk.com/agent/tickets/321

4. Append ?zat=true to the ticket URL, and reload the page.

   The URL should look like this:

   https://subdomain.zendesk.com/agent/tickets/321?zat=true

   Tip: Bookmark the modified URL for easy access in the future. You might also want to create a dummy ticket for app testing.

5. If you're using Chrome or Firefox and now see a shield icon in the Address bar, click the shield icon and agree to load an unsafe script (Chrome) or to disable protection on the page (Firefox). If you don't do this, the browser will block your app from being loaded into Zendesk Support.

   

   In Firefox, the shield icon is located on the left side of the Address bar.

6. Click the Reload Apps icon in the upper-right side of the Apps panel to load your local app into the panel.

   

   Even if the app appears in a Zendesk Support page, it's actually running locally on your machine.

   Note: If nothing happens, check for a shield icon in the Address bar. See step 5.
7. Work iteratively to develop and test features in your app. For example, make some changes to your app's source code, save the changes, then click Reload Apps on the ticket page to test the changes.

   

8. When you're done for the day, press Control+C to shut down the local server.

Validating your app

When you're finished developing your app, you should run validation tests to catch any problems before uploading it to Zendesk Support. The ZAT validation tool runs the same tests that are run when an app is uploaded to the Zendesk App Market.

To validate your app

1. Run the following command in the folder containing the app files:

   $ zat validate

2. When prompted, enter the URL of the Zendesk Support instance where you plan to install the app. The command doesn't actually install the app. Specify http instead of https in the URL. Example: http://yoursubdomain.zendesk.com.
3. Fix any problems reported by the tool.

Packaging your app for upload to Zendesk Support

When you're ready to upload your app to your instance of Zendesk Support, use the ZAT tool to package the app for uploading.

1. Run the following command in the folder containing the app files:

   $ zat package

2. When prompted, enter the URL of the Zendesk Support instance where you plan to install the app. The command doesn't actually upload and install the app. Also, specify http instead of https in the URL.

   Example: http://yoursubdomain.zendesk.com.

   The ZAT tool packages the app and saves it in a tmp folder. Example:

   

3. Grab the zip file (app-20130110164906.zip in the example) and upload it to Zendesk Support. For instructions, see Uploading.
4. To clean up the tmp folder, run the following command:

   $ zat clean

ZAT server limitations

A few things don't work when running an app locally on the ZAT server:

• secure requests - the ZAT server won't render the settings
• requirements - the requirements aren't installed, so the framework's requirement() method won't work either

To get around these limitations, you can install the app as a private app and then use the zat update command to make updates to the installed app. See Updating an installed app.

For other limitations, see also Zendesk app tools - Known issues.