PagerDuty Integrations

  • Create JIRA issues for new or updated PagerDuty incidents

    Want to make sure your development team gets on those incidents the moment they're reported? Activate this PagerDuty JIRA integration and we'll keep everything moving for you. It will trigger with each new or updated incident on PagerDuty once active, automatically creating a JIRA issue for you so you can trust your team will start tackling everything the moment it pops up.

    How It Works

    1. A new incident is added or updated on PagerDuty
    2. Zapier automatically creates an issue on JIRA

    What You Need

    • PagerDuty account
    • JIRA account
  • Add new rows on Google Sheets for new incidents on PagerDuty

    If you're having trouble taking things down for the record while you're busy putting out fires, let this PagerDuty Google Sheets integration do the work for you behind the scenes so you can focus on urgent matters. Just set it up and it will begin triggering for each new incident on PagerDuty, adding every one to a new row on Google Sheets so you can be sure your records stay accurate, even during the busiest times.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically adds a new row on Google Sheets

    What You Need

    • PagerDuty account
    • Google Sheets account
  • Trigger PagerDuty incidents for new messages on Slack

    Want to make sure you can communicate important events on PagerDuty as easily as you carry out the rest of your conversations on Slack? Try setting up this Slack PagerDuty integration between the two to bridge that gap. It will trigger for each new message on Slack, adding a new incident on the requested PagerDuty service with all the details you need.

    How It Works

    1. A new message is sent on Slack
    2. Zapier automatically creates an incident on PagerDuty

    What You Need

    • Slack account
    • PagerDuty account
  • Send emails for new incidents on PagerDuty

    Need to stay in the loop or update others for new incidents on PagerDuty? Use this Zap to leverage our native email service for notifications. It will trigger with every new incident on PagerDuty, sending out an automated email with all the data you need to make sure that everyone is aware of what's going on.

    Note: this integration uses Zapier's native email service. If you want to use your existing email account to send emails, try Zaps with email apps such as Gmail, Mailgun, SMTP or Mandrill.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically sends an email

    What You Need

    • PagerDuty account
  • Trigger PagerDuty incidents for new RSS posts

    Getting critical information for your SaaS via an RSS feed? Set up this Zap and you'll be able to track and report it all on PagerDuty automatically. From then on, it will trigger for every new item on the indicated RSS feed, reliably adding all its information to a new incident on the chosen PagerDuty service from then on.

    How It Works

    1. A new post is made to an RSS feed
    2. Zapier automatically adds an incident on PagerDuty

    What You Need

    • PagerDuty account
  • Send emails through Gmail for new PagerDuty incidents

    Tired of rushing to send updates for new PagerDuty incidents, when you should be working to solve them? Get the best of both worlds by setting up this PagerDuty Gmail integration. It will trigger with each new incident on PagerDuty, sending out an email from Gmail for every one it detected from then on so you never have to worry about that again.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically sends an email through Gmail

    What You Need

    • PagerDuty account
    • Gmail account
  • Create tickets on Zendesk for new or updated incidents on PagerDuty

    If your support team needs to be aware of PagerDuty incidents the moment they happen, this PagerDuty Zendesk integration is an excellent choice. Once active, it will trigger for each new or updated incident on PagerDuty, creating a new ticket on Zendesk with everything you need to ensure nothing critical ever gets overlooked.

    How It Works

    1. A new incident is created or updated on PagerDuty
    2. Zapier automatically creates an account on Zendesk

    What You Need

    • PagerDuty account
    • Zendesk account
  • Call AWS Lambda functions for new or updated PagerDuty incidents

    Want to make sure you deal with any site issues quickly and appropriately? Set up this PagerDuty AWS Lambda integration and we'll plug PagerDuty into AWS Lambda, invoking the function you need for every new or changed PagerDuty incident we detect.

    How It Works

    1. A new incident is detected or one is updated on PagerDuty
    2. Zapier automation calls a function on AWS Lambda

    What You Need

    • PagerDuty account
    • AWS Lambda account
  • Trigger PagerDuty incidents for new webhook payloads

    Want to make sure your SaaS stays responsive to new webhook data? Plug it right into your pipeline with this Zapier automation. Simply direct payloads to the custom webhook URL we provide during setup to trigger it, sending all the data to PagerDuty and adding an incident to your specified service automatically.

    How It Works

    1. A new payload is caught by a webhook
    2. Zapier automatically creates an incident on PagerDuty

    What You Need

    • PagerDuty account
  • Trigger daily incidents on PagerDuty

    Need to make sure that daily activity keeps happening on PagerDuty, even when you're too busy to watch over it? Take advantage of Zapier's trigger scheduling to keep everything organized and regular from the moment you set it up, adding a new incident to your chosen PagerDuty every day at the indicated time with all your information.

    How It Works

    1. A new day passes
    2. Zapier automatically triggers an incident on PagerDuty

    What You Need

    • PagerDuty account
  • Add new JIRA issues to PagerDuty as trigger events

    If your organisation uses JIRA for managing software development issues and PagerDuty for IT operations and incident response, you can use Zapier to automatically add JIRA issues as trigger events in PagerDuty. Once you set up this integration, new JIRA issues from that point forward are individually added as new PagerDuty trigger events. You'll get notified in PagerDuty of everything that happens in JIRA, to give you an easy way to have all of your IT alerts in the same place.

    How It Works

    1. A new JIRA issue is created
    2. Zapier adds that issue data to PagerDuty as a new trigger event

    What You Need

    • A JIRA account
    • A PagerDuty account
  • Create cards on Trello for new incidents on PagerDuty

    Having a hard time making sure your Trello team responds as quickly as possible to new issues on PagerDuty? Try setting up this PagerDuty Trello integration for some automated tasking. Once you do, a new card will be created on Trello for every new incident you create on PagerDuty, containing all the details you need to stay productive.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically creates a card on Trello

    What You Need

    • PagerDuty account
    • Trello account
  • Create a new trigger event in PagerDuty when a Fulcrum record's status value changes

    Keep your team notified of important or critical events in your PagerDuty account just by filling out your Fulcrum form with this integration.

    How it Works

    Zapier will watch your Fulcrum form for new entries. Whenever your form is filled out, Zapier will copy the info and use to trigger a new event in PagerDuty.

    What you Need

    • A PagerDuty account
    • A Fulcrum form

    Got that? Then let's get started.

  • Create cases on FogBugz for new or updated incidents on PagerDuty

    Just because you're busy putting out fires for alerts on PagerDuty doesn't mean the whole development team shouldn't know about it. Set up this PagerDuty FogBugz integration to loop everyone in automatically from then on: a new case will be created on FogBugz every time a new incident is reported or updated on PagerDuty—making sure that, even during an emergency, everything is being tracked accurately.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically creates a new case on FogBugz

    What You Need

    • PagerDuty account
    • FogBugz account
  • Trigger PagerDuty incidents for new JIRA issues found with JQL

    If your apps are particularly sensitive to specific kinds of JIRA issues you find with JQL searches, why not have some Zapier automation to track them for you 24/7 instead of searching for them yourself? This JIRA PagerDuty integration will trigger for every new JIRA issue that matches your JQL search, automatically adding a new incident to the PagerDuty service you define with all that data so you can take action the moment it happens.

    How It Works

    1. A new JIRA issue matches a JQL search
    2. Zapier automatically creates an incident on PagerDuty

    What You Need

    • JIRA account
    • PagerDuty account
  • Trigger PagerDuty incidents for new received emails

    If you're regularly getting emails that have to be converted into PagerDuty incidents, there's an easier way to set up the process. Just activate this Zap to have us do it all for you, triggering with each new email directed to the provided custom address and using the data to create a new PagerDuty incident on the service you indicate.

    Note: this integration uses Zapier's native email service. If you want to use your existing email account to trigger incidents, try Zaps with email apps such as Gmail, Mailgun, SMTP or Mandrill.

    How It Works

    1. A new email is received
    2. Zapier automatically creates an incident on PagerDuty

    What You Need

    • PagerDuty account
  • Trigger incidents on PagerDuty for new Zendesk tickets

    Want to make sure PagerDuty reflects all your support issues accurately? Use this Zendesk PagerDuty integration to connect it with your Zendesk setup, triggering with each new ticket on the system and automatically using the data to create a PagerDuty incident on the service you define, ensuring nothing falls through the cracks from then on.

    How It Works

    1. A new ticket is created on Zendesk
    2. Zapier automatically adds an incident on PagerDuty

    What You Need

    • Zendesk account
    • PagerDuty account
  • Trigger incidents on PagerDuty for new HipChat messages

    Need to be able to post your notices on PagerDuty as effortlessly as possible? Set it up this HipChat PagerDuty integration and it'll be as easy as talking to the rest of your team: it will trigger with every new message you send on HipChat, adding a new incident on the indicated PagerDuty service for each one with the data you define.

    How It Works

    1. A new message is received on HipChat
    2. Zapier automatically triggers an incident on PagerDuty

    What You Need

    • HipChat account
    • PagerDuty account
  • Trigger incidents on PagerDuty for new stories on Pivotal Tracker

    Want to make sure the issues on Pivotal Tracker relevant to your SaaS also make it to PagerDuty? Set up this Pivotal Tracker PagerDuty integration to flexibly connect the two services. Once active, stories on Pivotal Tracker that match your chosen project ID and (optionally) a specific label will automatically trigger a new incident on a PagerDuty service from then on with their information.

    How It Works

    1. A new story is added on Pivotal Tracker
    2. Zapier automatically triggers an incident on PagerDuty

    What You Need

    • Pivotal Tracker account
    • PagerDuty account
  • Trigger incidents on PagerDuty for new Freshservice tickets

    Thinking of ways to ensure your Freshservice tickets always get the attention they deserve? Put this Freshservice PagerDuty integration to work and we'll make sure they're reported on PagerDuty every time. Once active, it will trigger with each new ticket on Freshservice, creating new incidents on PagerDuty for every one so that you can be sure nothing critical will ever escape your attention again.

    How It Works

    1. A new ticket is added on Freshservice
    2. Zapier automatically triggers an incident on PagerDuty

    What You Need

    • Freshservice account
    • PagerDuty account
  • Trigger incidents on PagerDuty for recordings on Twilio

    If you can't afford to let any of those Twilio recordings go unheard on PagerDuty, use this Twilio PagerDuty integration to seamlessly connect the two services. It will trigger for each new recording on Twilio when active, automatically adding an incident to PagerDuty on the relevant service so you can trust in a reliable workflow from then on.

    How It Works

    1. A new recording is made on Twilio
    2. Zapier automatically triggers an incident on PagerDuty

    What You Need

    • Twilio account
    • PagerDuty account
  • Post on Twitter for new incidents on PagerDuty

    Need an easy way to let your followers know about any issues or interruptions with your SaaS service? Set up this PagerDuty Twitter integration to have automatic notifications while you're free to get to working fixing the problem. It will trigger with each new incident on PagerDuty, posting a new tweet to your account with the chosen details so everyone can keep up.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically posts on Twitter

    What You Need

    • PagerDuty account
    • Twitter account
  • Send HipChat messages for new incidents on PagerDuty

    Looking to guarantee your HipChat team knows the moment an incident pops up on PagerDuty? Let this PagerDuty HipChat integration handle those notifications while you focus on solving the issue. Just set it up to have the automation trigger with every new incident on PagerDuty, sending out a new message on HipChat with all the details you need to make sure everyone is in the loop.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically sends a message on HipChat

    What You Need

    • PagerDuty account
    • HipChat account
  • Place Twilio calls for new PagerDuty incidents

    Need to get or send some phone call notifications whenever there's an issue with PagerDuty? No need to have someone do it—Zapier automation can handle it completely. This PagerDuty Twilio integration will trigger with each new incident on PagerDuty once active, automatically placing a call on Twilio for each and auto-speaking your chosen message without fail.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically places a call on Twilio

    What You Need

    • PagerDuty account
    • Twilio account
  • Send emails through SMTP for new PagerDuty incidents

    Looking for an easy way to communicate PagerDuty incident notifications? Forget about sending emails out manually—have this Zap do it for you instead. Set it up and it will trigger with each new incident detected on PagerDuty, automatically sending out an email from your SMTP account with all the details you need to keep your receipient(s) in the loop with no effort on your part.

    How It Works

    1. A new incident is created on PagerDuty
    2. Zapier automatically sends an email through SMTP

    What You Need

    • PagerDuty account
    • SMTP email account

Why Zapier?

Free

Get started for free—14 day trial of premium features and apps.

Easy

No coding required—automate any of 1,000+ apps in minutes.

Secure

Enterprise-level security—connect mission-critical apps.

PagerDuty Integration Details

Launched on Zapier August 31, 2013

Creating a great customer experience requires constant communication within your team. You can use Zapier with PagerDuty to automatically create issues in your project management system and keep records for important tasks so your team can focus on creating and maintaining great customer experiences. You can even use Zapier to remind your team members when they’re on call—so nothing slips through the cracks.

Here are some creative ways to use PagerDuty with Zapier:

  • Make sure your team members know when they’re on call. Set up a weekly or daily trigger to find the user on call in PagerDuty and send a reminder message through Slack.
  • Create JIRA issues for new or updated PagerDuty incidents so your development team can get them resolved faster.
  • The last thing you want to worry about in an all-hands-on-deck situation is record-keeping. You can focus on more important tasks when you use Zapier to add new rows to a Google Sheets spreadsheet when there are new or updated incidents in PagerDuty.

Zapier combines Triggers (like "New or Updated Incident") and Actions (like "Add Acknowledge Event") to complete an action in one app when a trigger occurs in another app. These combos—called "Zaps"—complete your tasks automatically.

The following PagerDuty Triggers, Searches, and Actions are supported by Zapier:

Add Acknowledge Event

Acknowledge the incident with this Incident Key.

Add Trigger Event

Trigger an incident in PagerDuty with this Incident Key.

Add Resolve Event

Resolve the incident with this Incident Key.

New or Updated Incident

Triggers when new incidents are created, or when existing incidents change state.

Find User on Call

Find the user on call for a specific schedule.

Use our free platform to build a single Zapier integration and instantly connect your app with 1,000+ others.

Become a Zapier Integration Partner

PagerDuty is the leading digital operations management platform for businesses, that integrates with ITOps and DevOps monitoring stacks to improve operational reliability and agility. From enriching and aggregating events to correlating them into actionable incidents, PagerDuty provides insights so you can intelligently respond to critical disruptions for exceptional customer experience. With hundreds of native integrations with monitoring and collaboration tools, automated scheduling, advanced reporting, and guaranteed reliability, PagerDuty is trusted by thousands of organizations globally to increase business and employee efficiency.