Pipedrive is a sales CRM, and Vobiz connects to it as a softphone: agents dial from the panel or a person record, talk in the browser with mute, hold and transfer available while connected, and each finished call lands in the CRM as both an Activity and a Call Log with a signed recording link.
The softphone is a panel you embed in Pipedrive, connected to a small backend you host — it holds the Vobiz credentials, answers the call webhooks and writes to the CRM, and it needs a public HTTPS address. Pipedrive is connected over OAuth, through an app you create in their Developer Hub, requesting read-only access to deals and contacts and write access only where calls are actually recorded.
Why this pairing
Why run Pipedrive calling on Vobiz
Pipedrive is built around a rep working a pipeline, and calling is the part of that day most likely to happen somewhere else — on a mobile, on a desk phone, on a dialler that syncs overnight if it syncs at all. The deal record then holds a summary written from memory, or nothing.
Putting the phone in the CRM fixes the record, and this one also fixes the call: mute, hold and transfer are available while the conversation is live, so a rep can bring in a colleague rather than promising a call back. Vobiz supplies the numbers and carries the calls behind it.
Pipedrive owns
Deals, people, organisations and the pipeline
The Activity and Call Log the call becomes
Users, permissions and visibility
Reporting and forecasting on call activity
The panel the softphone embeds in
Vobiz owns
Phone numbers and instant provisioning
Placing, receiving and transferring the call
The agent's browser audio over WebRTC
Call recording and its signed, expiring delivery
Call detail records, including the backfill
Local regulatory compliance, including India KYC
What you get
What Vobiz adds to Pipedrive
A softphone in the CRM, with the controls a live conversation actually needs.
01
Mute, hold and transfer while the call is running
Call control that ends at connection leaves a rep with one option when a conversation needs someone else: hang up and promise a call back. Here the controls are live for the whole call, so the colleague joins while the customer is still on the line.
02
Two records per call, not one line in a timeline
Each finished call is written as a Pipedrive Activity and as a Call Log. The Activity puts it in the deal's history where a rep looks; the Call Log puts it where call reporting looks. Both, automatically, with duration and a playback link.
03
The caller is matched before you answer
An inbound number is resolved against your Pipedrive people, with a broader search as a fallback, so the matched contact is on screen while the phone is still ringing rather than found afterwards.
04
Numbers in 130+ countries
Local, mobile and toll-free inventory across 130+ countries, including regulated formats where a market demands them — India's 140-series and 1600-series among them. Any number on the account can be the caller ID.
05
Read-only where it can be
The Pipedrive app asks for read access to deals and contacts, and write access only for activities and call logs — the two things it actually creates. For an admin weighing up what a third party can do inside the CRM, the permission list is short and the reasoning for each line is in the guide.
06
Calls made elsewhere can still be reconciled
A backfill command pulls recent call records from your Vobiz account and syncs them into the CRM, so a call placed outside the softphone is not simply missing from the deal.
How it works
How to connect Pipedrive to Vobiz
A developer sets this up once. Reps sign in and dial.
01
Prove the Vobiz account first
Place a call from the Vobiz browser demo before anything else. If that does not work, nothing downstream will, and you will spend a day debugging the wrong layer.
02
Create the SIP endpoint
Create the endpoint the softphone registers as, and keep the username the platform stores rather than the one you submitted.
03
Run the backend and expose it
It holds the credentials, answers the call webhooks and writes to the CRM. Vobiz has to reach it over HTTPS. Verify the answer URL returns the expected instruction before opening any interface — a tunnel error page there kills every call in a way that points elsewhere.
04
Point Vobiz at the backend
Create the application with your answer URL, bind the endpoint, and attach a number for inbound.
05
Connect Pipedrive over OAuth
Create an app in Pipedrive's Developer Hub with your callback URL, request only the scopes listed in the guide, then authorise and confirm the connection reports as live.
06
Sign in and call
Open the panel, sign in with your Vobiz API credentials, pick a caller ID and dial. The call button stays disabled until registration lands, so nobody dials into a dead bridge.
The full setup, the OAuth scopes and why each is needed, the call architecture, the security notes and a troubleshooting table are in the Vobiz docs.
Yes — mute, hold and transfer are all available while the call is connected. That matters more than it sounds: without transfer, a rep who needs a colleague has to end the call and arrange a new one, and the customer has to explain themselves twice.
Two records. An Activity, which puts the call in the deal and contact history where a rep looks, and a Call Log, which puts it where Pipedrive's call reporting looks. Both carry the duration, and a signed playback link when the call was recorded.
Read-only on deals and contacts, write access for activities and call logs, and search access for resolving an inbound caller. Nothing beyond what it creates or reads — the guide lists each scope and what it is used for.
Yes, a small one. It holds the Vobiz credentials, answers the call webhooks, writes to the CRM and signs the recording links, and it needs a stable public HTTPS address because Vobiz calls into it during every call. The panel and backend ship together in one repository.
Yes. A backfill command pulls recent call records from your Vobiz account and syncs them into Pipedrive, so calls placed elsewhere can still be reconciled into the deal rather than lost.
You can provision numbers in 130+ countries — local, mobile and toll-free, including regulated formats where a market requires them, such as India's 140-series and 1600-series. The numbers stay in your own Vobiz account rather than inside the CRM.
Pipedrive is a sales CRM for managing deals, contacts and pipeline activity. Learn more at pipedrive.com. Vobiz is not affiliated with Pipedrive; this integration connects over Pipedrive's public API using an app you create in their Developer Hub.
We use cookies to run this site and, with your permission, to understand how it's used. Read our Cookie Policy.