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, 06:00 UTC
| 1 | ## How do I set up custom OAuth credentials for PagerDuty? |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | ### Create the PagerDuty app |
| 6 | |
| 7 | You need the **Admin** or **Account Owner** role in PagerDuty to see **App Registration**. |
| 8 | |
| 9 | 1. Sign in to [PagerDuty](https://www.pagerduty.com/). 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. |
| 10 | |
| 11 |  |
| 12 | |
| 13 | 2. 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. |
| 14 | |
| 15 |  |
| 16 | |
| 17 | 3. 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**. |
| 18 | |
| 19 |  |
| 20 | |
| 21 | 4. 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 `read` and `write` scopes the auth config requests. **Scoped OAuth** gives per-resource permissions but doesn't match the default auth config. |
| 22 | |
| 23 |  |
| 24 | |
| 25 | 5. Set **Redirect URL** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field. |
| 26 | 6. Under **Permission Scope**, select **Read & Write**. PagerDuty shows the selected scope as `write`, which includes read. |
| 27 | |
| 28 |  |
| 29 | |
| 30 | 7. 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. |
| 31 | |
| 32 | ### Create the auth config in Composio |
| 33 | |
| 34 | 1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-pagerduty), go to **Auth Configs** → **Create** and select **PagerDuty** with the **OAuth2** badge. |
| 35 | 2. 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**. |
| 36 | 3. Click **Connect Account**, enter a user ID, and sign in to PagerDuty with the account you want to connect. |
| 37 | 4. 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. |
| 38 | 5. 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. |
| 39 | |
| 40 | See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. |
| 41 | |
| 42 | PagerDuty also supports API key auth. Create the key under **Integrations** → **API Access Keys** and paste it when you connect the account. |