Skip to main content

Connect the Pipedrive private app

Audience: admins (with your Beta-Calco contact) · Scope: signing an environment into Pipedrive with the private app, and re-connecting it when asked · Last reviewed: 2026-08-24

What this does — Newer setups talk to Pipedrive as a private app the site "signs into", instead of a personal API token. Connecting is a one-time step per environment (live, staging, dev each sign in on their own), done together with your Beta-Calco contact. You'll also come back here if the connection ever needs to be renewed.

Before you start​

  • Do this with your Beta-Calco contact — the app's details have to be in place first.
  • You need a Pipedrive login that is an admin of the Pipedrive account being connected.

Steps​

  1. Your Beta-Calco contact confirms the app details are filled in under Custom Settings → Pipedrive Integration (client id/secret and the expected company id — a safety catch that refuses a credential from the wrong Pipedrive account).
  2. Open the site's install link they give you (it ends in /cb-api/bcpipedriveoauth/install) while logged into Pipedrive as that admin.
  3. Pipedrive shows a consent screen naming the app and what it may access — Allow. You land back on the site; the connection is stored.
  4. Your contact flips the Connection mode setting to the app and checks the connection panel on Diagnostics → Pipedrive Change Log shows it healthy.

What happens next​

  • The connection renews itself; a daily watchdog exercises it and raises an alarm if a human is needed.
  • Everything else (the sync, imports, provisioning) uses the new connection automatically.

Good to know​

  • "Needs re-authorisation" in the connection panel means the stored sign-in has expired or been revoked — repeat the install link step. Nothing is lost; the sync catches up once reconnected.
  • Wrong-account protection: if someone installs the app from a different Pipedrive account, the site refuses every call rather than mixing data — that's the company-id check doing its job.
  • Rollback is a setting, not a deploy: flipping the connection mode back to the API token restores the old behaviour instantly.

Screens and labels can differ slightly between environments — if a label doesn't match what you see, check with your Beta-Calco contact.

For developers → docs/pipedrive/oauth-app.md (the credential layer) and docs/pipedrive/go-live-private-app.md (the go-live runbook).