Freshdesk / Freshservice Integration

This guide will show you how to set up FreshDesk / FreshService to work with your new Helpdesk Buttons.

Freshdesk/FreshService integration requires two main parts:

1) set up an unregistered user as a catchall account as a contact in your PSA

2) set up the API integration.

This video shows the Freshdesk integration, but Freshservice should be very similar.

Unregistered User

By default, our software attempts to pair users with their contact information by checking with Freshdesk/Freshservice. If the user is not already found in the system a catch all account submits the ticket instead. This can be disabled for PSA’s that allow users to create accounts on ticket submission. Look at the Integration Defaults below.

This guide assumes you want to use the catch all contact: To start you will need to set up a contact that uses the email address of “unregistered@helpdeskbuttons.com” for the purposes of catching any unregistered users. You can name the account whatever you want. In our system it’s “Mystery Human”.

Getting an API Key

On the left of your screen, click the admin button.

../../../_images/fd-image-1.png

Scroll down and select Agents

../../../_images/fd-image-2.png

Click ‘New Agent

../../../_images/fd-image-4.png

And then fill out the information needed. This account needs the Administrator and Agent Roles roles.

After you have created that account, sign into it and go to the profile. You can get there by clicking your account picture and then selecting profile.

In the upper right, you will see ‘Your API Key’

../../../_images/fd-image-5.png

Please take note of this API Key, you will need it in a little bit.

Helpdeskbuttons.com Setup

The next step is to sign into your Helpdeskbuttons.com account and enter this information under Settings->Backend Information

../../../_images/fd-image-3.png

Enter your Ticket System API endpoint and the Ticket System API Key. Your Ticket System API endpoint is the main URL that you use to log into FreshDesk / FreshService. In this instance

../../../_images/fd-image-6.png

Click update once you are done. At this point, your Freshdesk / FreshService instance will be ready to go with your Helpdesk Buttons.

Access Restrictions

As of 0.5.x: The agent needs to have Administrator and Agent Roles.

Integration Defaults

The “auto_reg” flag allows users to be auto_registered by thier email address instead of added to an unregistered/catch all user. Keep in mind that if a user mistypes their email they will create a user.

Anti-Virus and AntiMalware

It is not always necessary, but we recommend whitelisting the helpdeskbuttons installation folder (C:\Program Files(x86)\Helpdesk Button). We regularly submit our code through VirusTotal to make sure we are not getting flagged, but almost all AV/M interactions cause some sort of failure. Webroot in particular can cause issues with screenshots.

Dispatcher Rules

This is the list of variables that can be accessed when using the Dispatcher Rules.

FreshDesk

Read/Write Read Only
priority selections
status name
group email
type ip
message mac
subject hostname
source  
agent  
append  

Freshservice

Read/Write Read Only
priority selections
status name
department email
agent ip
message mac
subject hostname
source  
impact  
urgency  
append  
group  
priv_append  

Field Definitions

priority

The ticket priority level (Urgent, Low, ect):

FreshDesk:

../../../_images/fd-priority.png

FreshService:

../../../_images/fs-priority.png


impact & urgency

Can set priority via the SLA priority matrix:

FreshService:

Impact:
../../../_images/fs-impact.png

Urgency:
../../../_images/fs-urgency.png


status

The ticket status (New, In Progress, etc):

FreshDesk:

../../../_images/fd-status.png

FreshService:

../../../_images/fs-status.png


group

The group the ticket will be put in:

FreshDesk:

../../../_images/fd-group.png

FreshService:

../../../_images/fs-group.png


type

Refers to the issue type (Service Request, Incident, Problem, Alert):

FreshDesk:

../../../_images/fd-type.png


department

The department the ticket will be put in:

FreshService:

../../../_images/fs-department.png


agent

The agent that will be assigned this ticket:

FreshDesk:

../../../_images/fd-agent.png

FreshService:

../../../_images/fs-agent.png


source

The ticket source (Web Portal, Etc):

FreshDesk:

../../../_images/fd-source.png

FreshService:

../../../_images/fs-source.png


priv_append

Allows you to append information to the internal ticket note:

FreshDesk:

../../../_images/fd-priv_append.png

FreshService:

../../../_images/fs-priv_append.png


other

There are additional variables which are common to all integrations. Those are documented here