Docs
WebsiteLoginFree Trial
  • Getting Started
    • OnCall Users
    • Team Admins
    • Account Admins
  • Architecture Guide
  • Common UI Design Patterns
  • Alerts
  • Teams
  • Schedules
  • Escalation Policies
  • Integrations
  • Broadcasts
  • Users
  • Notifications
  • Reports
  • Billing
  • Accounts
  • Stakeholders
  • Maintenance Windows
  • Routers
  • Notification Rules
  • Single Sign On (SSO)
  • Integration Guides
    • Introduction
    • 66uptime
    • Apex Ping
    • AppDynamics
    • Auvik
    • AWS CloudWatch
    • Azure Monitor
    • Cloudflare
    • Cronitor
    • Datadog
    • Dead Man's Snitch
    • Echoes HQ
    • ElastAlert
    • Email
    • Form
    • Freshdesk
    • Freshservice
    • Google Hangouts Chat
    • Grafana
    • Healthchecks.io
    • HetrixTools
    • Honeybadger
    • Hydrozen
    • Jira Server
    • JotForm
    • Kapacitor
    • LogicMonitor
    • Mattermost
      • Outgoing Webhook
      • Post to Channel
    • Meta Workplace
    • Microsoft Teams
    • New Relic
    • Outgoing Webhook
    • Pingdom
    • Prometheus
    • PRTG Network Monitor
    • Pulsetic
    • Sentry
    • ServerGuard24
    • Site24x7
    • Slack
      • Notifications
      • Outgoing Webhook
      • Post to Channel
    • SolarWinds
    • Stackdriver
    • StatusCake
    • Twilio
      • Incoming SMS
      • Live Call Routing
    • Typeform
    • Uptime
    • Uptime Kuma
    • UptimeRobot
    • Webhook
    • Zendesk
  • API
    • Introduction
    • Authentication
    • Errors
    • Pagination and Filters
    • Common Model Attributes
    • Account Users
    • Alerts
    • Broadcasts
    • Comments
    • Escalation Policies
    • Events
    • Integrations
    • Logs
    • Maintenance Windows
    • Notification Rules
    • Routers
    • Schedules
    • Teams
    • Users
  • Command Line Interface (CLI)
    • PagerTree CLI: Command Line Interface
Powered by GitBook
On this page
  • What is Freshservice?
  • How It Works
  • Integration Walkthrough
  • In PagerTree
  • In Freshservice
  • Freshservice Webhook Format
  • Troubleshooting

Was this helpful?

  1. Integration Guides

Freshservice

Connect your Freshservice tickets to PagerTree using our Freshservice Integration.

PreviousFreshdeskNextGoogle Hangouts Chat

Last updated 1 year ago

Was this helpful?

What is Freshservice?

is a cloud based ITSM software for your service desk. It provides automation tools to manage incidents, assets, and more.

How It Works

Freshservice creates tickets.

  • When a ticket is created in Freshservice, an alert is created in PagerTree automatically.

  • When a ticket is pending (ticket_status === 'Pending') in Freshservice, the alert is acknowledged in PagerTree automatically.

  • When a ticket is resolved or closed (ticket_status === 'Resolved' || ticket_status === 'Closed') in Freshservice, the alert is resolved in PagerTree automatically.

Integration Walkthrough

In this integration tutorial we will show you how to send tickets from Freshservice into PagerTree. The estimated time for this integration is 5 minutes. We assume that you already have a PagerTree and Freshservice account setup.

In PagerTree

  1. by clicking the Freshservice logo.

  2. .

In Freshservice

  1. Click the Gear Icon in the left side navigation menu to go to the admin page.

  2. On the admin page, navigate to Automation & Productivity -> Workflow Automator.

  3. Click the New Automator button and select Ticket.

  4. On the New Ticket Automator form:

    1. Title - PagerTree

    2. Click Create

  5. In the new Event form:

    1. When any of these events occur:

      1. Ticket is raised

      2. Status is changed from Any Status to Any Status

    2. These events can be performed by Anyone

    3. Name - Ticket is Created or Updated

    4. Click Done.

  6. On the Web Request Form:

    1. Request Type - POST

    2. Endpoint - Paste the PagerTree endpoint URL you copied earlier.

    3. Credentials - Inline Credential

    4. Authentication Type - No Auth

    5. Label - PagerTree Webhook

    6. Click Done.

  7. Click Activate.

  8. Click Confirm.

You have successfully completed the Freshservice Integration.

Freshservice Webhook Format

The root node of this payload "freshdesk" is not a mistake. The Freshservice application used to send webhooks in this format. For legacy reasons, it has been kept as "freshdesk".

{
  "freshdesk_webhook":{
    "ticket_id":"{{ticket.id}}",
    "ticket_status":"{{ticket.status}}",
    "ticket_subject":"{{ticket.subject}}",
    "ticket_description":"{{ticket.description | sanitize_html}}",
    "ticket_url":"{{ticket.url}}",
    "ticket_public_url":"{{ticket.public_url}}",
    "ticket_priority":"{{ticket.priority}}",
    "ticket_email":"{{ticket.from_email}}"
  }
}

Troubleshooting

If you are running into issues where the rules are not firing, please check the following in Freshservice:

  1. Ensure you created the rules by clicking the New Ticket Automator button.

  2. Ensure you are diagnosing only new tickets. Old tickets will not be processed by new automators.

  3. Try disabling and reenabling the rule.


Drag the Web Request action, connecting it to your event.

Body - Copy and paste the into the text box.

Freshservice Webhook Format (see below)
Freshservice
Create the integration
Copy the Endpoint URL
Navigate to Automation & Productivity -> Workflow Automator
Click the New Automator button and select Ticket
Freshservice PagerTree Automator
Ticket Automator Event
Freshservice PagerTree Web Request
Click active on the Ticket Automator
Click confirm
Freshservice Automation and Productivity
Freshservice new Automator
Freshservice PagerTree Automator
Freshservice Ticket Automator Event
Freshservice PagerTree Web Request
Freshservice Ticket Automator
confirm button