Skip to content
Last updated

PagerDuty integration

PagerDuty is a digital operations management platform for incident response, on-call scheduling, and real-time alerting. The PagerDuty integration with Frontegg allows your application to access and manage incidents, services, schedules, escalation policies, on-calls, users, teams, and webhook subscriptions on behalf of your users.


Prerequisites

  • A PagerDuty account with admin access
  • Access to the App Registration page in your PagerDuty subdomain

Connect PagerDuty

Step 1: Open the App Registration page

Sign in to your PagerDuty account and navigate to IntegrationsApp Registration, or open https://YOUR_SUBDOMAIN.pagerduty.com/developer/applications directly. The page lists all apps registered under your account and provides a New App button.

PagerDuty App Registration page with New App button highlighted

Step 2: Create a new app

Click New App. Enter the following information:

  • Name: Frontegg Integration
  • Description: A short description of the integration

Under Functionality, check OAuth 2.0 to enable REST API access via OAuth, then click Next.

PagerDuty New App form with OAuth 2.0 functionality selected

Step 3: Choose Scoped OAuth and add redirect URLs

On the Configure OAuth 2.0 step, leave Scoped OAuth selected. Scoped OAuth provides granular read and write access to PagerDuty resources and matches the scopes used by Frontegg.

Under Redirect URL, click Add Redirect URL and enter the following URIs:

  • https://YOUR_MCP_GATEWAY_URL/integration-callback

If only one redirect URL is allowed, use the first one.

PagerDuty OAuth configuration with Scoped OAuth selected and Frontegg redirect URLs added

Step 4: Select permission scopes

Under Permission Scope, select Read Access and Write Access for the following resources:

ResourceScopes
Incidentsincidents.read, incidents.write
Servicesservices.read, services.write
Schedulesschedules.read, schedules.write
Escalation Policiesescalation_policies.read, escalation_policies.write
Oncallsoncalls.read
Usersusers.read, users.write
Teamsteams.read, teams.write
Webhook Subscriptionswebhook_subscriptions.read, webhook_subscriptions.write

Minimum required scopes

For basic incident management, you need at least incidents.read, incidents.write, and services.read. Add more scopes only if your integration needs them.

PagerDuty Permission Scope table with required resources checked

Step 5: Verify selected scopes

Scroll down to the Selected Permission Scope section to confirm that all required scopes are listed in the read-only field. The full list should match the resources selected above.

PagerDuty Selected Permission Scope textbox showing all 15 selected scopes

Step 6: Register the app and copy credentials

Click Register App. PagerDuty displays the OAuth 2.0 Client Information dialog with your Client ID and Client Secret. Copy both values and store them in a safe place.

One-time display

PagerDuty shows the Client Secret only once. If you lose it, you must generate a new one from the app's settings.

PagerDuty OAuth 2.0 Client Information dialog with Client ID and Client Secret

Configure the Frontegg portal

Once you have obtained your Client ID and Client Secret from the steps above, enter them in the integration configuration page of the Frontegg portal:

  1. Open the Frontegg portal and navigate to your environment → IntegrationsPagerDuty.
  2. Enter the Client ID and Client Secret in the corresponding fields.
  3. Select the required scopes.
  4. Click Save.

Keep your credentials secure

Never share or commit your Client Secret to version control.

Additional resources