At a glance
- Availability: Experimental (how to enable).
- Authentication: OAuth 2.0.
- Connection: A user authorizes the connection in the provider’s consent screen.
- Scopes:
base,deals:full,contacts:full. - Provider documentation: Authentication reference.
Credentials
Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.Setup
- Create a Pipedrive developer sandbox: Request a free developer sandbox account at https://developers.pipedrive.com/start-here - apps can only be created from a sandbox or company account with admin rights.
- Create an app in the Developer Hub: In Pipedrive, open Tools and apps → Developer Hub (or https://app.pipedrive.com/developer-hub) and create an app. A private/unlisted app is fine for internal use.
- Set the callback URL and scopes: Set the OAuth callback URL to your app URL ending in /api/auth/pipedrive/callback and enable the deals:full, contacts:full, and search:read scopes (base is always included).
- Copy credentials and verify: Copy the Client ID and Client Secret from the app’s OAuth & access scopes page into PIPEDRIVE_CLIENT_ID and PIPEDRIVE_CLIENT_SECRET, connect your account, and run the List Deals tool.
Provider notes
- The token endpoint authenticates the client with HTTP Basic (base64 of client_id:client_secret)
- Access tokens expire after about 60 minutes; refresh tokens are issued and expire if unused for 60 days
- API calls go to the company-specific host returned as api_domain in the token response (e.g. https://yourcompany.pipedrive.com); tool URLs template it via {{oauth.raw.api_domain}}
Tools
Verify the connection
Call a read tool such aspipedrive__list_deals with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.