Integration Guide

The PagerDuty App allows you to trigger incidents within PagerDuty. This allows you to send notifications to your team even if it’s after hours. The PagerDuty system allows you to define how and when members of your team should be notified. If you are having trouble completing the installation, please contact us.

Please note that if you’d like to 1) auto-resolve incidents in PagerDuty when a ticket is closed 2) display the content of tickets in PagerDuty incidents or 3) push tickets with specific conditions to different escalation policy in PagerDuty, you will need to create a generic email integration. Instructions on the email integration can be found at the bottom of this integration guide.

Setting up the PagerDuty / integration

In PagerDuty

Create a “Generic API system” service:

  1. In your account, under the Configuration tab, select Services from the dropdown menu.Home_-_PagerDuty
  2. Click “Add New Service”. Services_-_PagerDuty1
  3. Enter a name for the service and select an escalation policy.
  4. Start typing “” under “Integration Type” to filter your choices. Then, click the Add service button.DeskCom
  5. Click the “Add Service” button.
  6. Once the service is created, you’ll be taken to the service page. On this page, you’ll see the “Service key”, which will be needed when you configure your App to send alarms to PagerDuty. Desk_com_-_PagerDuty


  1. To start Go to, click the PagerDuty button (you’ll see an image like the one below). Click on the Install button and agree to the Terms of Service.Add the PagerDuty App
  2. Accounts

    A App Account is the name you’ll use to refer to this Custom Account when you use it in Actions and Rules (Steps 3 & 4 below). You’ll need to set a name for this account, select PagerDuty Token Auth as the Authentication Method and add the Service API key from your existing PagerDuty Account (See step 4 above). Click on the Create button once you’re done filling out the form.Setup the PagerDuty Action

  3. ActionsNow, we’ll configure to send out messages using your PagerDuty account. (Note: You’ll need to tell PagerDuty who to contact and how to escalate the message – you make this configuration within PagerDuty.) An Action is the actual message you’ll be configuring to send through to your PagerDuty Account when a Rule fires that matches the conditions you set.
  4. An example of an action is the following – you can add Liquid variables (like {{}}) to provide dynamic information about the current case (Make sure to click on Add Action when completed):Configure the action for the PagerDuty AppWhen fired, this Action will use the PagerDuty App to send a message to PagerDuty that a particular case is updated. To trigger this action, we’ll need to attach it to a rule in
  5. Rules

    Business rules in allow you to act without Agent intervention when certain conditions occur at Events specified for a case.Here’s an example rule, run on a “Case Updated” event:Configure the rule for the PagerDuty AppA Business Rule fires when a certain Event occurs (e.g. a Case is Updated) and the conditions specified for that case evaluate to be true. In our example, we’ll fire the rule to post the Case Updated message on an Updated Case Interaction with an All Condition requiring the label “Send to PagerDuty“, and then remove that label at the conclusion of that rule so that the PagerDuty Message will not be sent until that label is added again.In addition, this rule will run anytime (not just during Business Hours). You can use the Advanced Edit to make sure your rule is enabled, and you can also view this rule in the Admin > Case Management > Rules section of’s Admin. Make sure to click on the Update button once you’ve completed filling out the form.

Congratulations! Your PagerDuty App should now be integrated with PagerDuty!


What happens when everything works?

When you update a case in by adding the label “send to PagerDuty“, the Rule will evaluate to be true, and the Action will fire to send a PagerDuty Message using your PagerDuty account. PagerDuty will then take over and notify the contacts you’d like to notify as per the escalation policy that you specify in PagerDuty.

How do I set up an email integration between PagerDuty and

I.Create a Generic Email Service in PagerDuty

Begin by creating a generic email service in PagerDuty. Go to Configurations>> Services>> + Add New Service.

From there you’ll need to:

  1. Name your service
  2. Pick an escalation policy
  3. Choose >> Integration via email
  4. Create an email integration address
  5. Click >> Add Service

Add Service

II. Setup Notifications

Next, navigate to the Admin section of your instance and add a new theme within Notifications.

  1. Admin
  2. Cases
  3. Notifications
  4. + Add Theme

Desk_com_Email_Parsing_Guide_-_Google_Docs will ask you to name your new theme. Once you’ve done that, click Add.


Next, you’ll edit the email template by entering the email integration address you created in your PagerDuty service. The integration email address goes in the To field. 


III. Create Rules in

Now, navigate to the Rules section of In the example below I’m going to tell to send an email to PagerDuty anytime a new ticket is created.

If you already have Rules created, you can simply edit them – or you can create a new rule by clicking + Add Rule.


When creating Rules, think about what type of tickets you want to push to PagerDuty – for example, you may only want to send tickets that have a certain priority to PagerDuty, or tickets assigned to particular groups. To do so, you’ll need to specify the conditions in the rule. 

Once you’ve established the condition(s) in which a ticket should be pushed to PagerDuty, you’ll tell to send an email to your PagerDuty integration address.

Chose Send Notification Emails and chose the notification you previously created.Desk_com_Admin_--_Lauren_Burnett

Since you’re going to be auto-resolving incidents in PagerDuty, you also need to set up a Case Resolved rule – this will send a notification to PagerDuty when a ticket has been resolved.



Now that you have configured, return to PagerDuty and set up your email parsing rules – these rules will allow PagerDuty to auto resolve incidents.

IV. Set Up Email Parsing Rules

To create email parsing rules, navigate to your PagerDuty service and go to Edit.

Desk_com_Email_Parsing_Guide_-_Google_DocsUnder Email Management chose Create and resolve incidents based on custom rules.


For this particular demo, in the first rule you want PagerDuty to trigger an incident if a ticket contains Status: New in the body. (Again, you may choose to specify different conditions based on your use case.)


Next you’ll create the incident key which will be used to append new emails to existing ones. The incident key should always be a unique identifier that appears in both the trigger and recovery email.


If you look at the example Open and Resolved emails from, you can see that the subject line doesn’t change – so you’ll use that as the incident key.


Once you’ve established your conditions and incident key, click +Add Another Rule


Since you want PagerDuty to close incidents when the corresponding ticket has changed to resolved, you will use “Status: Resolved” as your condition, and the same incident key that was used in the previous rule.


And there you go! PagerDuty will now auto-resolve incidents for your integration. If you’d like to double check, you can view an incident’s Incident Log. For Case #29, you can see that PagerDuty auto resolved the incident.


If you have questions or need additional assistance, please contact

All Our Integration Guides