Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 40 lines 3.41 KB
Rendered Raw
1 ## How do I set up custom OAuth credentials for Pipedrive?
2
3 Use your own Pipedrive OAuth app when the managed app isn't available to your users, or when you want your app name on the consent screen and control over its scopes.
4
5 ### Create the Pipedrive app
6
7 1. Sign in to the [Pipedrive Developer Hub](https://app.pipedrive.com/developer-hub) with your developer sandbox account and click **Create an app**.
8
9 ![Pipedrive Developer Sandbox welcome page with the Create an app button](/images/toolkits/pipedrive/create-an-app.webp)
10
11 2. Choose the app type. A **Private** app works only for users you select and doesn't need Pipedrive's review. A **Public** app is open to any Pipedrive user, needs a name that's unique across Pipedrive, and must be approved by Pipedrive before others can use it.
12
13 ![Pipedrive Select app type dialog comparing public and private apps](/images/toolkits/pipedrive/select-app-type.webp)
14
15 3. On the **Basic info** tab, enter an **App name** and set **Callback URL** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field. Click **Save**.
16 4. On the **OAuth & access scopes** tab, under **Access scopes**, choose **Read only** or **Full access** for each area your tools need, such as deals, contacts, activities, leads, products, or projects. By default, Pipedrive grants only basic access to the user's settings.
17
18 ![Pipedrive Access scopes with per-area toggles and Read only or Full access options](/images/toolkits/pipedrive/access-scopes.webp)
19
20 5. Scroll down to **OAuth credentials** and copy the **Client ID** and **Client Secret**.
21
22 ![Pipedrive OAuth & access scopes tab showing the Client ID and Client secret](/images/toolkits/pipedrive/oauth-credentials.webp)
23
24 6. For a public app, submit it from the **App review info** tab. Private apps skip review.
25
26 ### Create the auth config in Composio
27
28 1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-pipedrive), go to **Auth Configs** → **Create** and select **Pipedrive**.
29 2. Choose **OAuth2** and your own credentials, then paste the Client ID and Client Secret. Keep the redirect URI as the value you registered in Pipedrive.
30 3. Click **Create Auth Config**, then click **Connect Account** and approve access in Pipedrive. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
31
32 See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
33
34 Start the connection from Composio. Don't use **Install and Test** in Pipedrive's app settings: that button runs Pipedrive's own install flow and sends the user to the callback URL without the Composio auth config context.
35
36 ## Why am I seeing "App not found" when connecting Pipedrive?
37
38 Pipedrive usually shows "App not found" when the OAuth app used for the connection is not approved or available for that user/workspace.
39
40 If you are using managed Pipedrive OAuth, this means the managed OAuth app is still under Pipedrive review/verification. If you are using your own Pipedrive OAuth app, check the app's approval/verification status in Pipedrive and make sure the user is authorizing the same app configured in the auth config. Also check that the client ID and secret come from that same app and that the callback URL matches the auth config's redirect URI. After the app is approved or corrected, start a fresh connection.