Though there is no out-of-the box integration between LiquidPlanner and Zendesk, there are a few ways to connect the two worlds together that will save you time and keep all those details from falling through the cracks.
In many cases, those using Zendesk for ticket tracking find that most individual tickets, incidents, problems, and questions don’t need to be sent into LiquidPlanner since they’re likely to be quick jobs requiring immediate action, rather than needing to be scheduled in with other work. For this reason, it’s common to use an ongoing task to track bulk time spent working on multiple tickets.
For the Zendesk tickets that do require more time to resolve, it can be helpful to have that ticket represented as an individual task in LiquidPlanner. This way, the work can be scheduled and other assigned work can be shifted around it – either now, if it’s an urgent matter or as part of a future project. Decide with your team what constitutes sending a ticket into your workspace. For some, that might mean the ticket requires a developer’s attention. For others, it may mean all tickets reporting a bug with a certain feature should be automatically sent into LiquidPlanner.
The first option is to automatically create tasks in LiquidPlanner by using an email target and trigger in Zendesk.
In this method, Zendesk tickets can be added automatically as tasks into a “Zendesk Inbox” package in LiquidPlanner, created specifically for this purpose. Alternatively, you can also use the workspace “Inbox” or another container for this purpose.
Then, it’s easy to see all the submitted tickets in the same package and triage them as needed. Someone can drag-and-drop them into a project and/or prioritize them into a priority package depending on when the ticket work should be scheduled. When tasks are triaged, this is a good time to open the item’s edit panel and change the project/package while also adding other information, such as assigning the task owner if it isn’t already assigned, estimating effort, adding details, notes, checklists, comments, etc.
Follow these steps to connect Zendesk and LiquidPlanner using email integration:
This first step is to prepare your LP workspace for the Zendesk tickets that come in:
The next step is setting up an email target in Zendesk which will target LiquidPlanner with an email (creating a new task) when a certain action happens in Zendesk. The ticket actions and conditions prompting the new task email will be designated by creating a trigger in Zendesk.
ADDING A TARGET
Click here to see detailed instructions from Zendesk on how to set this up.
ADDING A TRIGGER
Click here to see details instructions from Zendesk on how to set this up.
To create a more automated process, consider using Zapier. If you are not familiar with Zapier – it is a Webapp-Automation Service. It allows you to integrate LiquidPlanner with hundreds of online apps by setting up automations in an easy-to-use graphical interface.
With Zapier, there’s no need to wait for app developers or programmers to build integrations. Zapier helps you use complementary apps side-by-side. It’s pretty much as simple as creating a Zapier account and then setting up some Zaps by filling out forms and selecting from dropdown menus. A Zap is a blueprint for a task you want to do over and over. In brief, a Zap looks like this: “When a new thing happens in X, do this other thing in Y.” The first part is the trigger and the second part is the action. More details can be found in this article on Zapier.
Both Zendesk and LiquidPlanner have multiple triggers and actions available to choose from in Zapier. This means you can create a variety of combinations to automate parts of your process and save you time. Some examples of tasks that can be automated using those triggers and actions are:
You can set up filters to refine conditions under which the trigger is executed.
If you want to develop a more flexible and powerful integration, building a custom integration using Zendesk API and LiquidPlanner API with webhooks is the way to go.
Please note that this option requires development resources from your end in order to set this up.
Here are some developer resources to get you started: