Skip to main content

Integrations

Freshservice Integration (via Generic Integration)

Freshservice is a cloud-based IT service management (ITSM) tool that helps businesses manage IT services and employee service.

What can Zenduty do for Freshservice users

With the use of Generic Integration, Zenduty sends new ticket alerts to the right support engineer or team and notifies them based on on-call schedules via email, text messages(SMS), phone calls(Voice), Slack, Microsoft Teams and iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed. Zenduty provides your support engineers with detailed context around the Freshservice ticket alert along with support playbook and a complete incident command framework to triage and remediate and resolve incidents with speed.

To integrate Freshservice with Zenduty, complete the following steps:

On the Zenduty Dashboard:

  1. Create a Generic Integration within the respective Teams --> Services
  2. Click on "Enable custom value mapping" and enter a random string in the Message and click on Save.
  3. Copy the webhook URL, this will be used later.

On the Freshservice Dashboard:

  1. Navigate to Admin --> Automation & Productivity --> Workflow Automator
  1. Select "Ticket" under Modules and "Event Based Workflow" under Workflow types
🚧
You can use any other type in the Modules based on your Business use-case. For the purpose of demonstration, we are using the Ticket module.
  1. Create New Workflow, name the workflow as Zenduty and click on Create
  2. Under the Event trigger, select Ticket is raised and Ticket is updated as the triggers to sync the change in Ticket status with Zenduty. This is auto Ack and resolve the Incident on Zenduty.
  1. Add the Action block and select "Trigger Webhook" option.
  1. Select the Request Type as POST and paste the copied URL in the callback URL field.
  2. Under the Content option, select the necessary fields that you'd like to send to Zenduty.
  1. Click on Test Webhook to trigger an example Incident and check the connection between Zenduty and Freshservice.

On the Zenduty Dashboard:

  1. Navigate to the Generic Integration page and Map the Freshservice payload with the required Zenduty payload to automate the process.
Key Value
Message {{payload.freshdesk_webhook.ticket_subject}}
Entity ID {{payload.freshdesk_webhook.ticket_id}}
Summary {{payload.freshdesk_webhook.ticket_description}}
Alert Type {{payload.freshdesk_webhook.ticket_status}}
Alert Type - Critical Open
Alert Type - Ack'ed Pending
Alert Type - Resolved Resolved/Closed
❗
This is an example of the Mapping to Ack and Resolve the Incident on Zenduty when there is a Status change from Open --> Pending and Pending --> Resolved.
  1. You can use the payload picker to Map the values and also add conditional logic to further automate and optimise the Incident workflow on Zenduty. Refer to Generic Integration document for more details on Custom value mapping.
Zenduty SignUp