ERPNext Documentation

This guide will show you how to set up your new Helpdesk Buttons with ERPNext in as few as 15 minutes.

Integration

ERPNext integration requires three main parts:

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

2) set up the API integration.

3) configure helpdeskbuttons account.

Video Walkthrough

1) Create an Unregistered User

Create a Customer to recieve ‘Catch All’ tickets and add a Contact to that Customer with the email address

unregistered@helpdeskbuttons.com

../../../_images/ERPNext-contact.png

This is in case someone puts in an email that is not already in ERPNext, this will also prompt the GUI to ask for identifying information from the end user.

2) Create an API KEY and SECRET

To create the API KEY for ERPNext:

Click Settings -> My Settings -> API Access

You can create a key by clicking the “Generate Keys” Button.

Copy down the API Secret as it cannot be viewed again.

../../../_images/ERPNext-secret.png

If the API Key does not show up try logging out, then back in.

You should see something like this when you have successfully created a key pair.

../../../_images/ERPNext-key.png

Copy the API Key as you will need that to complete the integration.

3) Helpdeskbuttons.com Settings

Enter your Ticket System API endpoint as shown (do not add add https:// or the path after the url)

for cloudhosted instances: business_name.erpnext.com

Your API key is formatted as shown

api_key:api_secret

Click Update and the Integration Test button to send a test ticket.

Anti-Virus and AntiMalware

It is not always necessary, but we recommend whitelisting the tier2tickets installation folder (C:\Program Files(x86)\tier2tickets). 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.

Read/Write Read Only
priority selections
issue_type hostname
status name
priv_append email
message ip
subject mac
owner

input_cell

 

input_phone

 

input_company

 

input_email

 

input_name

Field Definitions

priority

The ticket priority level (Urgent, Low, ect):
../../../_images/ERPNext-priority.png


status

Refers to the ticket status (New, In Progress, etc):
../../../_images/ERPNext-status.png


issue_type

The issue type (this will depend on the types you create):
../../../_images/ERPNext-type.png


owner

The agent that will be assigned this ticket:
../../../_images/ERPNext-owner.png


priv_append

Allows you to append information to the internal ticket note:
../../../_images/ERPNext-priv_append.png


input_*

Additional information provided if the user is not found in ERPNext
../../../_images/ERPNext-input.png

other

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

Webhook Walkthrough

To setup a webhook in ERPNext, click Administration -> Integrations -> Settings -> Webhook

Click New to Create a new webhook.

Fill out the webhook as follows:

  • DocType to Issue (Support)
  • Doc Event to on_update.
  • Request URL should be listed on your Integration Settings Page. under the Ticket Notification section.
  • Request Structure to Form URL-Encoded

Click Save

Doing this will lock some of the choices in and provide more options for the rest of the webhook.

../../../_images/erpnext-webhook1.png
  • Set the webhook header to application/json
  • Add these fields to the webhook data area
  • Name
  • Customer
  • Raised By
  • Description
  • Subject
  • Contact
  • Status

Save Again and you should be all set

../../../_images/erpnext-webhook2.png