NEW
For more powerful tools consider the new Zingtree CX Actions instead.
You can use Zingtree workflows to reduce your technical support team’s workload. Customers can either self-solve their issue, or a new ticket can be created automatically in Zendesk that includes all the information from the customer’s tree troubleshooting session. By making it easy to gather background information from the customer via the tree, your support team saves a lot of time by reducing back-and-forth messages.
Zingtree provides a free app for Zendesk to make it easy for your support agents to see the tree transcript. It looks like this inside of Zendesk:
Setup Overview
It’s easy to set this up – here’s a brief overview of the process. Continue reading for detailed steps.
- Add a new Application to Zingtree for creating Zendesk Tickets.
- Create a “Ticket Submitted” node which sends the new ticket info to Zendesk.
- Create a “New Ticket” node to obtain the customer’s name, email, a ticket subject, description, and optional custom fields.
- Make sure Zendesk is properly configured to allow external apps to create requests.
- Optionally install the Zingtree app into Zendesk via the Zendesk App Marketplace.
Notification of Zendesk's Retirement of API Tokens
IMPORTANT
Zendesk is retiring API tokens and migrating to OAuth. If you are currently using the Zingtree Create Ticket App to create Zendesk tickets, you will need to update your authentication method from an API token to OAuth. See details from Zendesk here. Zendesk API tokens will be permanently deactivated on April 30, 2027. You must migrate to OAuth before that date.
Follow the steps below to update your authentication method to OAuth or add a new OAuth client.
Create New OAuth Credentials in Zendesk Admin
- In Zendesk navigate to the Admin Center then APIs > OAuth Clients
- Click create new OAuth Client
- The following screen appears
-
Fill in these required fields:
- Name: This is the name of your OAuth Client. Name it something that describes its purpose. Like Create ticket from a Zingtree workflow. When you fill in this field, the Identifier field is automatically populated with the same value in lowercase with underscores instead of spaces. Copy that Identifier and save it to a note for a later step.
- Client Kind: Switch this from Public to Confidential (Important)
- Click Save. Once you click Save the Secret will populate with your Client Secret. Copy the Secret and save it in a secure location. You'll need it in the next steps. For security reasons, Zendesk displays the full Secret only once.
- Important: Once you have copied and saved the Client Secret, click Save again.
Updating a Current Zingtree App to Use the New OAuth Credentials
Once you have created your OAuth Client in Zendesk Admin, you can now update your existing Zendesk New Ticket App to use the new OAuth credentials without needing to update any of your current workflows that are using the old API credentials.
- In Zingtree, navigate to Apps & Integrations > My Apps
- Locate your existing Zendesk New Ticket App and click the Edit button
You'll see this screen with your current API credentials and a warning about the need to switch to OAuth: - Under Authentication Method near the top, choose OAuth Client Credentials
- Your screen will now look like this:
Your existing Zendesk Domain will be pre-populated for you. - Paste in your OAuth Client Identifier that you copied from step 4.a in the previous section.
- Paste in your OAuth Client Secret that you copied from step 4.c in the previous section.
- Form ID: If you'd like your ticket submitted to a specific form in Zendesk, place the Form ID here.
- Click Save.
- That's it. Your current workflows that are utilizing your old API credentials will now use the new OAuth credentials.
Adding a New Application to Zingtree to create a Zendesk Ticket
A Zingtree application can be called from any node. You’ll need to add the Zendesk New Ticket App first as follows:
- Log into your Zingtree account.
- Go to Apps & Integrations
- Click Install App
- Select the Zendesk: New Ticket App.
- The following screen will appear:
- Fill in these details:
- Zendesk Domain: Your Zendesk domain without the https:// or the .zendesk.com suffix
- Confidential OAuth Client ID: Paste in your OAuth Client Identifier that you copied from step 4.a in the previous section
- Confidential OAuth Client Secret: Paste in your OAuth Client Secret that you copied from step 4.c in the previous section
- Form ID: If you'd like your ticket submitted to a specific form in Zendesk, place the Form ID here
- Click Save
Setting a Brand
If you want to add a new ticket for a specific brand, use the brand subdomain as the Zendesk Domain. (You can see your brand subdomain in your Zendesk Setup, under Manage > Brands.) In this example, the brand subdomain is “astrodemo”):
Create a “Ticket Submitted” Node
When this node appears, a new ticket is added to Zendesk. This is the end result of pressing a “Submit Ticket” button inside the tree. You can create this node as follows:
- Add a new Content Node to your tree.
- Give the node a title, and any text you want to appear in the content area – like “Thanks for submitting a ticket” etc.
- Go to the Apps & Webhooks section of the node.
- Click Add App.
-
Select the Zendesk App you just created. You should see something like this:
Tip: The session transcript is added by default to the ticket description unless a Zingtree Session ID field is present. To disable transcripts, add notranscript to the Message Data area.
Now we’re ready to link a ticket entry page to this “Ticket Submitted” node.
Create a “New Ticket” node
When end-users navigate the troubleshooting tree, if they haven’t been able to resolve the issue, you can direct them to a node which collects data for the ticket. These variables must be named exactly as specified below so that Zingtree knows which fields to include in the new Zendesk ticket.
These variables are mandatory:
- zd_subject – The subject of the request.
- zd_description – The description for the request.
- zd_requester_name – The customer’s full name.
- zd_requester_email – The email of the customer.
These variables are optional:
- zd_type – The type of the request. (Defaults to “question”) – Possible values: “problem”, “incident”, “question” or “task”
- zd_priority – The priority of the request. (Defaults to “normal”) – Possible values: “urgent”, “high”, “normal”, “low”.
You can also add custom fields to your ticket form (see below for details).
To create a new ticket form in your tree:
- Edit the node where you want the customer to submit the ticket.
- Click the Data Entry Fields tab.
- Add fields for zd_subject, zd_description, zd_requester_name and zd_requester_email at minimum.
- Add zt_priority or zt_type optionally.
-
When you are done, your Data Entry Fields will look something like this:
- Go to the Action Buttons section, and add a “Submit” button to go to your submit ticket page.
Bonus: When a ticket is created, the Zendesk ticket ID is returned as a variable named zt_ticket_id.
How to Include Custom Fields
Every field in your Zendesk Ticket from has a unique ID. So to include field #12345 in the ticket form, you would add a variable named like this: zd_custom_field_12345
You can locate the Field ID for your custom ticket fields in Zendesk as follows:
-
In Zendesk Admin go to Objects & Rules > Fields. The Ticket Fields screen appears:
- Copy the Field ID (outlined in yellow above).
Zendesk Configuration
Your Zendesk setup will need to allow anonymous requests. To enable this, the following Customer settings must be set in the Support admin interface:
- Enable “Anyone can submit tickets”
- Disable “Ask users to register”
You can do this via Admin > People > End users. Your setup should look like this:
Add the Zingtree Support App to Zendesk (recommended)
To make a deluxe experience for your support techs, we recommend adding the Zingtree Support app to your Zendesk. In Zendesk, go to Admin > Apps & Integrations > Zendesk Support Apps. Click the Marketplace button and search for “Zingtree”. Be sure to choose the Zingtree Support app: