PagerDuty integration

Quick start

Call PagerDuty from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to PagerDuty's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "PAGERDUTY_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

OverSkill hosts the OAuth application for PagerDuty. End-users click Connect on the integration card in your app, complete the OAuth flow with PagerDuty, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2, API_KEY.

Available actions

368 actions exposed via the PagerDuty integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• PAGERDUTY_ADD_SERVICE_TO_INCIDENT_WORKFLOW_TRIGGER
• PAGERDUTY_AGGREGATE_ESCALATION_POLICY_INCIDENT_METRICS
• PAGERDUTY_AGGREGATE_INCIDENT_METRICS_WITH_FILTERS
• PAGERDUTY_ASSOCIATE_SERVICE_DEPENDENCIES
• PAGERDUTY_ASSOCIATE_TEAM_WITH_AUTOMATION_ACTION
• PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDS
• PAGERDUTY_CONVERT_SERVICE_RULE_BY_ID
• PAGERDUTY_COUNT_PAUSED_INCIDENT_REPORTS
• PAGERDUTY_CREATE_A_CUSTOM_FIELD_FOR_AN_INCIDENT_TYPE
• PAGERDUTY_CREATE_A_FIELD_OPTION_FOR_A_CUSTOM_FIELD
• PAGERDUTY_CREATE_AND_MANAGE_CUSTOM_INCIDENT_FIELDS
• PAGERDUTY_CREATE_AN_INCIDENT_TYPE