Skip to main content

Pipedrive

Pipedrive is a sales-focused CRM platform that helps businesses manage deals, contacts, activities, and sales pipelines. With Pipedrive, sales teams can track leads through customizable pipelines, manage customer relationships, schedule activities, and gain insights into sales performance. It's designed specifically for salespeople to keep their sales process organized and moving forward.

Authentication Types​

Pipedrive supports 2 authentication methods:

  • OAuth - Secure, app-based authentication with granular permission control.

    • Pros: Secure, per-user tracking, granular scope control, production-ready, supports all Pipedrive features
    • Cons: Requires creating a Pipedrive app in Developer Hub, more complex setup
    • Best for: Organizations wanting full control, compliance requirements, production deployments, marketplace apps

  • API Token - Simple, personal API token for quick integration.

    • Pros: Very simple setup, works immediately, no app registration needed
    • Cons: Full access to all user data, one token per user, less secure for shared environments, legacy method
    • Best for: Personal use, testing, quick prototypes, single-user scenarios

General Settings​

Before using the connector, you need to configure:

  • Company Domain - Your Pipedrive company subdomain (e.g., if your Pipedrive URL is https://mycompany.pipedrive.com, enter mycompany)
tip

You can find your company domain in your Pipedrive URL. It's the part before .pipedrive.com. For example:

  • URL: https://acmecorp.pipedrive.com → Domain: acmecorp
  • URL: https://sales-team-123.pipedrive.com → Domain: sales-team-123

Setting up OAuth​

To use Pipedrive with OAuth, you need to create a Pipedrive app and configure OAuth authentication.

1. Access Developer Hub​

  1. Log in to your Pipedrive account

  2. Click on your profile icon in the top right corner

  3. Select Developer Hub from the dropdown menu

2. Create a New App​

  1. In Developer Hub, click Create an app -> Create private app

  2. Fill in the app details:

    • App name: Enter a descriptive name (e.g., "Webrix Integration")
    • Callback URL: Copy from Webrix platform

  3. Click Save

3. Configure OAuth Settings​

  1. In your app settings, navigate to the OAuth & access scopes tab

  2. Select the scopes your integration needs

  3. Click Save

4. Get Client Credentials​

  1. In the OAuth & access scopes tab, find the Client credentials section

  2. Copy the Client ID

  3. Click Show next to Client secret and copy it

    warning

    Keep your Client Secret secure! Never share it publicly or commit it to version control.

5. Configure in Webrix​

  1. In Webrix, go to Integrations → New → Built-in

  2. Select Pipedrive and click Use

  3. Under General Settings, enter your Company Domain (e.g., mycompany)

  4. Under Authentication Type, select OAuth

  5. Paste your Client ID in the Client ID field

  6. Paste your Client Secret in the Client Secret field

  7. Review and adjust the Scopes if needed

  8. Click Save Changes

6. Test the Connection​

  1. After saving, click Connect to test the OAuth flow

  2. You'll be redirected to Pipedrive to authorize the app

  3. Review the permissions requested and click Allow and Install

  4. You'll be redirected back to Webrix with a successful connection

Setting up API Token​

API Token authentication is simpler but less secure. Use this for personal testing or single-user scenarios.

1. Find Your API Token​

  1. Log in to your Pipedrive account

  2. Click on your profile icon in the top right corner

  3. Select Personal preferences

  4. Scroll down to the API section

  5. Copy your Personal API token

    warning

    Your API token provides full access to your Pipedrive account. Keep it secure and never share it publicly.

2. Configure in Webrix​

  1. In Webrix, go to Integrations → New → Built-in

  2. Select Pipedrive and click Use

  3. Under General Settings, enter your Company Domain (e.g., mycompany)

  4. Under Authentication Type, select API Key

  5. Paste your API Token in the token field

  6. Click Save Changes

3. Test the Connection​

  1. After saving, click Connect to test the connection

  2. If successful, you'll see a confirmation message

Troubleshooting​

Redirect URI Mismatch Error​

If you see "redirect_uri_mismatch" or "invalid_redirect_uri" error during OAuth authorization.

Cause: The redirect URL configured in your Pipedrive app doesn't match the one being used during the OAuth flow.

Solution:

  1. Copy the exact Redirect URI from Webrix
  2. Go to your Pipedrive app in Developer Hub → OAuth & access scopes
  3. Ensure the URI is added exactly as shown (including https:// and any trailing slashes)
  4. Save the changes and try connecting again
  5. If the issue persists, try removing and re-adding the redirect URI

Invalid Client ID or Client Secret​

Authentication fails with "invalid_client" error.

Cause: The Client ID or Client Secret is incorrect or has been regenerated.

Solution:

  1. Go to your Pipedrive app in Developer Hub
  2. Verify the Client ID matches exactly
  3. Regenerate the Client Secret if needed (note: this will break existing connections)
  4. Update the credentials in Webrix
  5. Try connecting again

Token Refresh Failures​

Users are repeatedly prompted to reconnect or get "invalid_token" errors.

Cause: The refresh token may have been revoked, or there's an issue with token storage.

Solution:

  1. Disconnect and reconnect the Pipedrive integration in Webrix
  2. Verify that the app hasn't been uninstalled or disabled in Pipedrive
  3. Check that your Pipedrive app's OAuth settings haven't been modified
  4. Ensure the refresh_token scope is included (it should be by default)

"Access Denied" or "Forbidden" Errors​

API requests fail with 403 errors or "access denied" messages.

Cause: The user doesn't have sufficient permissions, or required scopes are missing.

Solution:

  1. For OAuth: Verify that all necessary scopes are selected in your Pipedrive app
  2. For API Token: Check that your user account has permission to access the requested resources
  3. Reconnect with the correct scopes selected
  4. Verify that the user has the appropriate role in Pipedrive (admin, regular user, etc.)

Rate Limiting​

API requests fail with 429 (Too Many Requests) errors.

Cause: Pipedrive enforces API rate limits to ensure platform stability.

Solution:

  1. Pipedrive typically allows:
    • OAuth apps: 100 requests per 10 seconds per user
    • API Token: 100 requests per 10 seconds per company
  2. Implement retry logic with exponential backoff in your workflows
  3. For batch operations, use list endpoints instead of multiple individual requests
  4. Consider spreading out API calls over time rather than making many simultaneous requests

Cannot Find Company Domain​

Not sure what to enter for Company Domain setting.

Cause: The company domain is not immediately obvious.

Solution:

  1. Log in to your Pipedrive account
  2. Look at your browser's address bar
  3. Your URL will be in the format: https://YOUR-DOMAIN.pipedrive.com
  4. The YOUR-DOMAIN part is your company domain
  5. Enter only the domain part (without https:// or .pipedrive.com)
  6. Examples:
    • URL: https://acme.pipedrive.com → Enter: acme
    • URL: https://sales-team-123.pipedrive.com → Enter: sales-team-123

API Token vs OAuth - Which Should I Use?​

Not sure which authentication method to choose.

Use OAuth when:

  • Building a production integration
  • Multiple users will use the connector
  • You need granular permission control
  • Compliance or security policies require it
  • Building a marketplace app

Use API Token when:

  • Personal use or testing
  • Single user scenario
  • Quick prototype or proof of concept
  • You want the simplest possible setup
  • You trust the environment completely

Missing Custom Fields in Responses​

Custom fields don't appear in API responses.

Cause: Custom fields in Pipedrive are returned with auto-generated keys like abc123def456.

Solution:

  1. Custom fields have dynamically generated keys in Pipedrive
  2. To find custom field keys:
    • Use the "Get Person", "Get Deal", etc. tools to see all fields
    • Or use Pipedrive's web interface: Settings → Data fields
  3. Custom field keys look like: 1234567890abcdef1234567890abcdef12345678
  4. Reference these keys when creating or updating records
  5. The field name (e.g., "Customer Type") is only for display; use the key for API calls