anchor.diff:  # PagerDuty
   
  -The [PagerDuty](http://pagerduty.com/) integration in Buildkite lets you send [change events](https://developer.pagerduty.com/docs/events-api-v2/send-change-events/) when your builds pass and fail.
  +The [PagerDuty](http://pagerduty.com/) integration in Buildkite can send [change events](https://developer.pagerduty.com/docs/events-api-v2/send-change-events/) to PagerDuty when your builds finish.
   
   <%= image "overview.png", width: 2202/2, height: 638/2, alt: "Screenshot of the recent events in PagerDuty" %>
   
   {:toc}
   
  -## Generating an PagerDuty Integration API Key
  +## Generating a PagerDuty Integration API Key
   
  -In PagerDuty, go to the "Service Directory":
  +Before using the integration you'll need to generate a PagerDuty Integration API Key.
  +
  +In [PagerDuty](http://pagerduty.com/), go to the "Service Directory":
   
   <%= image "menu.png", width: 854/2, height: 324/2, alt: "Screenshot of the Service Directory link in the menu" %>
   
  
positive.code: 
  Once you've filled out this form, select "Add Integration".
  
  Now that the integration has been created, you should be able to see it in your Integrations list. Copy the "Integration Key", as you'll need it in the next step.
  
  <%= image "integration-with-key.png", width: 2262/2, height: 822/2, alt: "Screenshot of the Buildkite integration in PagerDuty" %>
  
  ## Sending Change Events from your pipeline
  
  The PagerDuty integration inside Buildkite can be setup using the [`notify` YAML attribute](/docs/pipelines/notifications).
  
  Using an Integration Key, add the following `notify` attribute to your pipeline.yml file:
  
  ```yaml
  steps:
  
negative.code: ```
  {: codeblock-file="pipeline.yml"}
  
  <%= image "change-event.png", width: 2304/2, height: 1096/2, alt: "Screenshot of a Change Event inside PagerDuty sent from Buildkite" %>
  
  To send Change Events only when the build passes, add a [condition](/docs/pipelines/conditionals) to your build configuration:
  
  ```yaml
  notify:
  