Basic Freshdesk Integration

Question

The following guide is an example of a custom http integration using the Freshdesk API along with some of LogicMonitor's token values.&nbsp;

To start off I would recommend reviewing the following resources.&nbsp;

LogicMonitor Custom HTTP Delivery Documentation:https://www.logicmonitor.com/support/settings/integrations/custom-http-delivery/

LogicMonitor Tokens: NOTE:&nbsp;(In this guide I create a token ##freshdesk.requesterid## using a custom property on the device. This allows me to pass this value through the integration. This can be very useful if you need to use the same integration to create tickets as multiple organizations or users. I've included a screenshot below detailing where this is set on the device.)https://www.logicmonitor.com/support/settings/logicmodules/tokens-available-in-datasource-alert-messages/

&nbsp;

Freshdesk API Documentation:https://developer.freshdesk.com/api/

Complete these steps in Freshdesk prior to creating your integration:

Create a Freshdesk User to be used for authentication.https://support.freshdesk.com/support/solutions/articles/37591-adding-new-support-agents-

&nbsp;

In the below payloads I use the Freshdesk requester_id as a token to create, update and close tickets. You can find the requester_id for a Freshdesk user by checking the following.&nbsp;

&nbsp;

Configure your Freshdesk API key for authentication.https://support.freshdesk.com/support/solutions/articles/215517-how-to-find-your-api-key

Complete these steps in LogicMonitor to create the&nbsp;Integration:

Add a new Custom HTTP Delivery under Integrations using the following payloads as a starting point.

Determine if you would like to use a wildcard for things such as your Freshdesk requester_id or organization_id etc.

Payload Examples:

The following examples will&nbsp;Create, Update and Close FreshDesk tickets with LogicMonitor&nbsp;Alerts.

NOTE:&nbsp;When authenticating with the Freshdesk api, you will only need to enter your api key in the username field, the password is blank.&nbsp;

&nbsp;

Active:&nbsp;

{ "description": "Host: ##HOST##
Datasource: ##DATASOURCE##
Datapoint: ##DATAPOINT##
Level: ##LEVEL##
 Start: ##START##
Duration: ##DURATION##
Value: ##VALUE##
Reason: ##DATAPOINT## ##THRESHOLD##", "subject": "##LEVEL## - ##HOST## ##INSTANCE##", "requester_id": ##freshdesk.requesterid##, "priority": 1, "status": 2 }

Escalated:

{ "description": "Alert Escalated/De-escalated
Host: ##HOST##
Datasource: ##DATASOURCE##
Datapoint: ##DATAPOINT##
Level: ##LEVEL##
 Start: ##START##
Duration: ##DURATION##
Value: ##VALUE##
Reason: ##DATAPOINT## ##THRESHOLD##", "subject": "##LEVEL## - ##HOST## ##INSTANCE##", "requester_id": ##freshdesk.requesterid##}

&nbsp;

Acknowledged:

{ "body":"Note: ##MESSAGE##" }

Cleared:&nbsp;

{ "description": "Alert Cleared
Host: ##HOST##
Datasource: ##DATASOURCE##
Datapoint: ##DATAPOINT##
Level: ##LEVEL##
 Start: ##START##
Duration: ##DURATION##
Value: ##VALUE##
Reason: ##DATAPOINT## ##THRESHOLD##", "subject": "##LEVEL## - ##HOST## ##INSTANCE##", "requester_id": ##freshdesk.requesterid##, "priority": 1, "status": 4 }

&nbsp;

Here we can see the finished product, a ticket generated and cleared using the above payloads.&nbsp;

Active Warn:

Active Error:

Active Critical:

Active Critical Ack:&nbsp;

Cleared: (Note that the Status changes to Resolved)

antony_hawkins · Answer

Further comments... I've just used almost all of this to integrate to:

https://&lt;my-customer&gt;.freshservice.com/api/v2/tickets/

(note, freshservice.com not freshdesk.com)

We needed to also add a "group_id" field and integer value into the JSON payloads (can be tokenised as per requesterID and _api.key values); we also needed to add a&nbsp;"category" field and value as my customer's FreshService setup has this as a mandatory field with a defined list of acceptable values - you may therefore need to do the same or similar additions for any fields your setup defines as mandatory.

Finally, the JSON path for the created ticket ID from FreshService is (certain for my customer's version) at ticket.id, not merely id.

However, all of these things were very easy to learn from the Integration Logs within LogicMonitor and the results of attempting test alert deliveries, so many thanks @Chris Seiber&nbsp;for providing 98% of the necessary work!

s_p · Answer

@Chris Seiber - It looks like this is actually working despite the above now.&nbsp; I think the problem was I had some additional attributes set for Freshdesk that despite being supported by the API didn't seem to go through (which caused the entire update to fail).&nbsp; So I think I'm good now on this but do still think the HTML formatting I mentioned may be helpful to others.

anonymous · Answer

Chris, I'm working on implementing this and the test's all work correctly. &nbsp;However, tickets are not being created when alerts fire. &nbsp;I have case #83246 entered to see if I can get some assistance and hopefully we can get this flushed out.

kurt_wolf · Answer

NM, I was referring to Zendesk, not freshdesk.

s_p · Answer

@Chris Seiber thanks for posting this.&nbsp; I have found a couple of things when setting this up and thought I'd share (and ask for feedback):

1.&nbsp; To properly format the message in the ticket you need to use HTML.&nbsp; In other words you need to use &lt;br&gt; instead of 
 for a line break.

2. The JSON path you have doesn't seem valid.&nbsp; I was able to use $.id to get the ticket ID... however there is an issue with that (see below).

When I get the ##EXTERNALTICKETID## it is coming back like this:

Slack Integration : -1, Freshdesk - Create and Update Tickets : 20018

Where the first part before the colon are the display names of all integrations used on the alert (note the first one is for Slack and the second is for Freshdesk).&nbsp; If I only had the Freshdesk integration configured, it would likely say "Freshdesk - Create and Update Tickets".&nbsp; The part after the colon is the actual ticket number.&nbsp; Do you have any thoughts on how to strip off the first part?&nbsp; I know you support regular expressions but then that doesn't seem to be usable at teh same time as JSON for the ##EXTERNALTICKETID## mapping.&nbsp; Is this a bug in your software that is including this in the property to begin with given I don't see how we could possibly get those values (the integration labels) from the JSON response itself (I don't see them when I do a test).

Forum Discussion

Basic Freshdesk Integration

Related Content

LM Servicenow Integration

Servicenow Integration

Servicenow Integration

Logic Monitor service now integration issue

Plugin update for LogicMonitor to ServiceNow Integration

Recent Discussions

Can anyone help modify this Datasource to be able to use any port?

Dashboard updates

Does anyone monitor their iDracs with LM? Tons of duplicate alerts

How do you monitor Running Services on Linux boxes?

Event Sources SNMP and Windows collectors?