Pipedrive
WhatsApp on the Pipedrive person, without wrecking your reports.
Connect the company once. People are matched by number, each message is written as a note on their record, and deals mirror across when you ask for it.
The pipeline is in Pipedrive. The reason it moved is on somebody’s phone.
A deal advances because of what was said on WhatsApp, and Pipedrive records only that it advanced. When it stalls, nobody can reconstruct why without asking whoever owns the phone — assuming they still work here.
Connect the company, then choose what syncs
An OAuth install from Settings, by an owner or admin. Messages and deals are separate switches and both start off.
People matched on the number, not the formatting
The last ten digits are compared, and an exact digit match wins over the first fuzzy hit. Pipedrive’s search is forgiving, and a note on the wrong person’s record is worse than no note at all.
Notes, deliberately — not activities
A Pipedrive activity is a task with a due date. Integrations that log messages as completed activities add thousands of them to your activity reports and quietly ruin the numbers. A note carries the same text and is counted as nothing.
Every note says which way it went
The note names the conversation, the direction and the time before the text, because a timeline of bare quotations is unreadable a week later — you cannot tell what the customer said from what your team replied.
Deals mirrored once, then updated
A deal is created once and updated in place after, linked to the person, with the value and currency. It is never posted twice: a duplicate deal is a forecast counted twice.
What crosses over
- Real inbound and outbound WhatsApp messages, as notes on the matched person.
- A person created in Pipedrive when the number is one your company did not have.
- Deals from the inbox pipeline — title, value, currency and the linked person — once you switch deals on.
What never does
- Internal notes. Checked before every other preference, for the same reason as everywhere else: your team sees them, the customer’s staff should not.
- Private conversations, and numbers somebody excluded. Unreachable in the code rather than filtered out of the payload.
- Activities. Nothing this connector writes will appear in an activity report.
Integrations are a Pro capability. Starter does not include HubSpot, Pipedrive, Zapier, webhooks or the API.
When you would use it
- A deal in Pipedrive with no record of the conversation that created it.
- Handing an account to a new owner who has to start the relationship from scratch.
- An activity report that stopped meaning anything after the last integration.
- Chasing a quote that was agreed on WhatsApp and never written down.
What this leans on
Questions people ask
Which plan is this on?
Pro. Integrations — HubSpot, Pipedrive, Zapier, webhooks and the API — are a Pro capability, and Starter does not include them.
Why notes rather than activities?
Because an activity is counted. Logging every WhatsApp message as a completed activity would tell you your team finished four thousand tasks last month, which is a number nobody asked us to invent. A note renders on the timeline and distorts nothing.
Is there a panel inside Pipedrive?
Not yet. A panel needs a published app manifest and a hosted iframe, and shipping half of one would be worse than not having it. The sync writes to the person and the deal, which is where a Pipedrive user is already looking.
Can we restrict which conversations sync?
Yes, two ways. Incoming messages only, and a label filter that limits the whole connection to conversations carrying labels you choose.