PagerDuty

The PagerDuty tool lets a workbench agent read incidents from the PagerDuty REST API while a job is running. This is separate from a PagerDuty webhook, which delivers alert payloads into Plural so a job can start — the tool lets that job fetch additional incident context the webhook payload didn't include, such as body.details, notes, or trigger log entry channel details.

Prerequisites

Before you begin, make sure you have:

• Permission in Plural Console to create a configured tool and edit the target workbench.
• A PagerDuty REST API key with permission to read incidents for the services the workbench needs.

Create a REST API key

1. In PagerDuty, go to Integrations → API Access Keys → Create New API Key.
2. Enter a description, and choose read-only access if you only need incident lookup.
3. Copy the key immediately — PagerDuty does not show it again.

Capabilities

• pagerduty_get_incident — Get full incident details, including title, status, urgency, priority, service, assignments, and body.details (the UI description). Pass the incident ID from a webhook payload or from pagerduty_list_incidents.
• pagerduty_list_incidents — List incidents, filtered by status, service, or time range. The response includes pagination fields offset, limit, and more; limit accepts a value up to 100.
• pagerduty_list_incident_notes — List the notes attached to an incident.
• pagerduty_list_incident_log_entries — List timeline log entries for an incident. Trigger entries may include channel details with extra context from manual or integration triggers.

Every call authenticates with the configured REST API key, so the agent can only read incidents and services that key's owner is authorized to see.

Create the PagerDuty tool