Skip to main content
PagerDuty logo

Overview

Add PagerDuty to any ModuleX agent or workflow. Incident management, on-call scheduling, and alerting via the PagerDuty REST API (api.pagerduty.com).
Categories: Monitoring & Observability · Incident Management · Developer Tools & Infrastructure · Auth: OAuth2 · Actions: 4

Authentication

OAuth2 Authentication

Connect using PagerDuty OAuth (recommended)

Required Credentials

OAuth Configuration

  • Authorization URL: https://identity.pagerduty.com/oauth/authorize
  • Token URL: https://identity.pagerduty.com/oauth/token
  • Scopes: read, write

Available Actions

Parameters

string
required
A succinct description of the nature, symptoms, cause, or effect of the incident
string
required
The ID of the PagerDuty service to trigger the incident on
string
The urgency of the incident: high or low
string
Additional incident details
string
A string which identifies the incident. Subsequent requests with the same key and service will be rejected if an open incident matches
string
The ID of the escalation policy to assign
array
List of user IDs to assign to the incident
string
Phone number for the conference bridge (format: +1 415-555-1212,,,,1234#)
string
URL for the conference bridge (e.g. a web conference or Slack channel link)

Response

Parameters

string
required
The ID of the incident to acknowledge

Response

Parameters

string
required
The ID of the incident to resolve

Response

Parameters

string
required
The ID of the on-call schedule
string
required
The ID of the user to search for in the schedule

Response

Limits & Quotas

  • Rate limits: PagerDuty REST API allows up to 960 requests per minute (varies by account tier).
  • Throttling: Requests exceeding the rate limit receive HTTP 429; implement client-side backoff.
  • Error model: non-2xx responses raise httpx.HTTPStatusError (Pattern A). The caller should handle retries.

Datadog

Sentry

Algolia