Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 04:45 UTC
How do I set up custom OAuth credentials for PagerDuty?
Use your own PagerDuty OAuth app when you want the consent screen to show your app name and to keep the client credentials under your control.
Create the PagerDuty app
You need the Admin or Account Owner role in PagerDuty to see App Registration.
- Sign in to PagerDuty. In the top navigation, click Integrations, then under Developer Tools click App Registration. Don't pick API Access Keys; that page is for API keys.

- Click + New App. Apps you register here stay private to your PagerDuty account unless you publish them, and private is what you want for Composio.

- On Info & Functionality, enter a name and description. Under Functionality, check OAuth 2.0. Leave Events Integration unchecked unless you also need it. Click Next.

- On Configure OAuth 2.0, choose Classic User OAuth. It acts on behalf of the signing-in user with broad read and write access, which matches the
readandwritescopes the auth config requests. Scoped OAuth gives per-resource permissions but doesn't match the default auth config.

- Set Redirect URL to
https://backend.composio.dev/api/v1/auth-apps/add. It must exactly match the auth config'soauth_redirect_urifield. - Under Permission Scope, select Read & Write. PagerDuty shows the selected scope as
write, which includes read.

- Click Register App. PagerDuty shows the Client ID and Client Secret once, in a dialog. Copy both now. If you lose the secret, generate a new one and update the auth config.
Create the auth config in Composio
- In the Composio dashboard, go to Auth Configs → Create and select PagerDuty with the OAuth2 badge.
- Choose your own credentials and paste the Client ID and Client Secret. Keep the redirect URI as the value you registered in PagerDuty. Click Create Auth Config.
- Click Connect Account, enter a user ID, and sign in to PagerDuty with the account you want to connect.
- If the user belongs to more than one PagerDuty account (subdomain), PagerDuty lists them. Pick the one whose incidents and services the agent should manage.
- On the consent screen, check the app name and permissions, then click Submit Consent. Confirm the account shows Active on the auth config's Connected Accounts tab.
See custom auth configs for the general flow.
PagerDuty also supports API key auth. Create the key under Integrations → API Access Keys and paste it when you connect the account.