PagerDuty

The PagerDuty connector lets your automations open, acknowledge, and resolve incidents in PagerDuty as part of an automated response. PagerDuty is in the Alerting connector category - a category dedicated to incident-management platforms that own the on-call lifecycle (trigger → acknowledge → resolve) and escalation policies.

When the connector is configured, automations can use the Trigger Alert, Get Alert, Acknowledge Alert, Add Note to Alert, and Resolve Alert steps from the Alerting tab in the step picker. Each step's Provider field is set to PagerDuty.

Note:

You must generate a PagerDuty General Access Key (an account-wide REST API key) and have one PagerDuty user email address available to attribute incident actions to. See Appendix I - Creating a PagerDuty General Access Key.

To configure the PagerDuty connector:

  1. Access Playblocks and go to Connectors.
  2. In the Alerting section, select PagerDuty.
  3. Turn on the Enabled toggle button.
  4. In the Step 1 - Authenticate section, enter these:

    • API key - The PagerDuty General Access Key that you created.

    • Email - The email address of a real user in your PagerDuty organization. PagerDuty requires a "From" email header on every REST API request that creates or modifies an incident. Playblocks sends this address as the "From" header on every incident action. The email controls only the attribution that shows up in PagerDuty's audit log; it is unrelated to the authentication itself, which is handled entirely by the General Access Key.

    • Service URL - The PagerDuty REST API base URL. Default value is https://api.pagerduty.com.

  5. Click Save.

    Playblocks validates the API key.

    • On success, the connector is marked Connected.

    • On failure, the side panel shows the error and the connector is left in an Error state. Fix the credentials and save again.

  6. In the Step 2 - Default service section, from the Default service list, select the PagerDuty service that new incidents should be created in by default.
    Note:

    The default service is used by the Trigger Alert step unless a specific service is chosen on the step itself.

  7. Click Save.