How WhatsApp Sync Works with Pipedrive Deals and Contacts
TimelinesAI syncs WhatsApp to Pipedrive by phone number: each chat matches an existing Person, or creates one. Messages log as custom activities on that Person and on the most recent active Deal or Lead.
TimelinesAI syncs WhatsApp to Pipedrive by phone number: each chat matches an existing Person, or creates one. Messages log as custom activities on that Person and on the most recent active Deal or Lead. You choose whether new chats create a Deal, a Lead, or nothing. Setup takes about five minutes and needs no WhatsApp API.
Most guides to connecting WhatsApp and Pipedrive tell you which buttons to press. Very few tell you what actually happens to your data afterwards — which record a message lands on, what happens when a number matches nothing, and which of three open deals a conversation attaches to.
That matters, because almost every sync problem people hit is a consequence of the matching logic rather than the setup. This guide covers the mechanics first, then the configuration.
TimelinesAI runs as a native Pipedrive Marketplace app — 4.5 stars across 269 reviews — rather than a workflow built on a third-party automation layer. That distinction is what makes a direct object mapping possible, and it is where we will start.
What actually syncs: the object map
Every WhatsApp conversation resolves to Pipedrive records through a fixed sequence. Understanding it takes about a minute and will save you most of the troubleshooting below.
One chat produces four things in Pipedrive:
- Person — matched by phone number, or created from the number if nothing matches.
- Custom activity — every message in and out, logged on the Person and on the associated Deal, grouped by date.
- Deal or Lead — the chat attaches to one, according to your settings.
- Files — voice notes, images and attachments upload to the Files section of the Person and the Deal.
Calls on a connected number are logged too, and group chats sync if you enable them. More on both below.
The matching sequence
When a message arrives, TimelinesAI resolves it in this order:
- Existing association. If the chat is already linked to a Pipedrive record, the message goes there.
- Phone number match. Otherwise it compares the WhatsApp number against Person records. Matching is fuzzy — it handles numbers with or without the plus sign, and with or without country codes, so +44 7700 900123, 447700900123 and 07700 900123 all resolve to the same Person.
- Creation. If nothing matches, it creates a new Person from the WhatsApp number.
Why it matters: the phone number is the join key for the entire integration. Every record that ends up in the wrong place got there at step two — which is also why the most common fix is a dedupe rather than a reconfiguration.
Which Deal a conversation lands on
This is the mechanic that surprises people most, and it is worth stating plainly: TimelinesAI syncs a chat into the most recent active Deal. Older deals and closed deals are skipped.
So a customer with three open deals does not get their messages spread across all three. Everything lands on the newest one, unless you pin the chat somewhere specific.
Before you start
- Pipedrive admin rights. Required to install the app at company level, and required for the sync to see all records.
- The same email address on both accounts. TimelinesAI uses matching emails to auto-assign record ownership. Mismatched addresses are a common cause of chats syncing under the wrong owner.
- Any WhatsApp account type — regular WhatsApp, the WhatsApp Business app, WhatsApp Business API, or Coexistence. No WhatsApp API access is required, and you do not migrate or delete your existing number.
- About five minutes.
That third point is worth dwelling on if you are comparing tools. Most WhatsApp–CRM products are built on the WhatsApp Business API, which means the number you use has to be registered to a WABA — and a number registered for the Business API can no longer be used with regular WhatsApp or the Business app. For a sales team already running deals from existing WhatsApp numbers, that means giving up those numbers and their history. TimelinesAI connects the account you already use.
Step 1: Connect your WhatsApp account
Scan the QR code from your TimelinesAI workspace, exactly as you would for WhatsApp Web.
Why it matters: this is where the “no API required” property becomes concrete. You are connecting the account your team already runs, so existing conversations come with it. Nothing is migrated and no number is re-registered.
Step 2: Authorize the Pipedrive connection
Install the app from the Pipedrive Marketplace and authorize it with an admin account.
Why it matters: authorization scope determines what the sync can see. Installing with a restricted user is the most common cause of “some chats sync and others don’t” — the integration cannot see records outside that user’s visibility group.
Step 3: Choose what new chats create
Open the integration settings. Four controls decide how records are created:
- Auto-Add Chat as New Person — whether unmatched numbers create Person records.
- Action on New Chat — Create New Deal, Create New Lead, or Do Nothing.
- Choose Pipeline for New Deals — where auto-created deals land.
- Import Messages from Groups — whether group chats sync at all.
The Action on New Chat setting behaves as follows. Create New Deal links to the most recent active Deal and creates one if none exist. Create New Lead links to the most recent non-archived Lead and creates one if none exist. Do Nothing links to the most recent Deal only, and creates nothing.
Why it matters: this is the decision you are most likely to regret. Create New Deal on a high-volume support number will manufacture a deal for every enquiry and distort your pipeline reporting within a week. If most inbound chats are not sales opportunities, choose Do Nothing and pin deliberately instead.
Step 4: Exclude personal chats, and decide about groups
Turn off auto-creation for numbers that should not become CRM records, and leave Import Messages from Groups off unless you actively want group threads in Pipedrive.
Groups work differently from one-to-one chats, and the difference is worth knowing. A group has no contact number, so it is matched by its unique group ID and synced to a Pipedrive Person named after the group, with each member’s messages logged as activities. You can sync WhatsApp group chats into Pipedrive on any QR-connected number.
Why it matters: the WhatsApp account your reps connect is the one they already use. Without this step, family threads and delivery-driver chats arrive in Pipedrive as Persons, and in some configurations as Deals. It is far easier to prevent than to clean up.
Step 5: Pin a chat to a specific Deal
Open the chat in TimelinesAI and pin it to the Deal it belongs to.
Why it matters: pinning overrides the most-recent-active-Deal default. For any customer with more than one open opportunity — a renewal alongside an upsell, two properties, two projects — pinning is the only way to guarantee the thread lands on the right one. If you take one action from this guide beyond setup, make it this.
Step 6: Decide how messages appear in the activity feed
Messages log as custom activities on the associated Person and Deal, grouped by date. You can disable activity creation if you do not want them appearing in the Pipedrive calendar.
Why it matters: left at defaults on a busy number, WhatsApp activity can crowd out scheduled calls and meetings in the calendar view. Teams that rely on Pipedrive’s calendar for planning usually turn this off; teams that use it as an audit trail leave it on.
Step 7: Reply from inside Pipedrive
Open a Person or Deal and use the WhatsApp panel to read the thread and reply without leaving the CRM. Message templates are available from the same panel, and you can send WhatsApp messages from Pipedrive as part of your normal deal workflow.
On a QR-connected number those replies are free-form. You type what you want to say, in your own words, without an approved template — templates stay available for starting a conversation rather than answering one. Tools built on the WhatsApp Business API work the other way round, which is why their replies so often read like form letters.
Why it matters: sync alone still leaves reps switching windows to answer. Replying in place is what actually removes WhatsApp from the tab bar.
Watch it in practice: WhatsApp messages syncing inside Pipedrive — a short walkthrough of the panel, the activity record and a reply sent from the deal.
Common sync problems and how to fix them
Some chats sync and others don’t. Visibility groups or permission sets are restricting what the connected user can see. Connect with an admin account and check Visibility Groups and Permission Sets in Pipedrive.
Messages land on the wrong Person, or a duplicate appears. Duplicate Person records already exist in Pipedrive. When two Persons share a number, the matching step cannot resolve which one wins.
Dedupe in Pipedrive first. The integration’s matching is format-tolerant, so this is nearly always pre-existing duplicates rather than a formatting problem.
Messages go to the wrong Deal. The default targets the most recent active Deal. Pin the chat, as in Step 5.
A message sent from Pipedrive doesn’t appear in the feed. Usually connection state rather than the message itself. Check the connection is active and authorized under an admin account, then check the chat’s Sync Log.
Nothing has synced since a certain date. The workspace connection dropped or lost admin privileges. Reconnect and confirm admin rights.
Personal contacts appearing as Pipedrive Persons. Auto-add was left on for a number that also handles personal chats. See Step 4.
There is more detail in the Pipedrive help centre, and a wider set of process pitfalls in our guide to avoiding common WhatsApp–Pipedrive mistakes.
How to verify the sync is working
A 60-second test, before you trust it with live deals:
- Send a WhatsApp message from a number that does not exist in Pipedrive.
- Confirm a new Person appears with that number.
- Confirm the message appears as an activity on that Person.
- If Action on New Chat is set to create a Deal or Lead, confirm the record was created in the expected pipeline.
- Pin the chat to a different Deal, send another message, and confirm it lands there instead.
- Reply from inside Pipedrive and confirm it arrives on the phone.
Where to look when a step fails: open the chat’s Sync Log. It records where each message was routed and why, which resolves most issues faster than checking Pipedrive.
Going further: AI agent access to the same data
Once WhatsApp and Pipedrive share a data layer, the natural next question is whether an AI agent can act on it. The WhatsApp MCP connects your WhatsApp workspace to Claude, ChatGPT, Cursor or your own agent framework — browsing chats, drafting replies, applying labels and assigning conversations from a prompt. Pipedrive ships its own MCP offering, so the two sit naturally alongside each other for teams building agent-driven sales workflows.
Frequently asked questions
How long does it take to set up WhatsApp–Pipedrive sync?
About five minutes. Connecting WhatsApp is a QR scan, authorizing Pipedrive is an app install, and the remaining time goes on choosing what new chats should create. No development work and no API access are involved.
Do I need Pipedrive admin access?
Yes. Admin rights are required to install the app at company level, and the connected account’s visibility determines which records the sync can reach. Installing under a restricted user causes partial syncing.
Does it sync existing chat history or only new messages?
Because you connect your existing WhatsApp account rather than registering a new number, your conversations come with it. Historical messages are available in the TimelinesAI workspace, and ongoing messages log to Pipedrive from connection onward.
What happens if a WhatsApp number doesn’t match any Pipedrive contact?
A new Person is created automatically from that number, provided Auto-Add Chat as New Person is enabled. What happens beyond the Person depends on your Action on New Chat setting — a Deal, a Lead, or nothing.
Which Deal does a conversation sync into if a customer has several?
The most recent active Deal. Closed and older deals are skipped. To override this, pin the chat to a specific Deal.
Do I need approved message templates to reply?
No. On a QR-connected number you reply in free-form text, exactly as you would in WhatsApp itself. Templates remain available for starting new conversations. This differs from Business API tools, where an approved template is required to send outside an open conversation window.
Can I use my existing WhatsApp number, or do I need a Business API account?
Any account type works — regular WhatsApp, the WhatsApp Business app, WhatsApp Business API, or Coexistence. No number migration and no deleting an existing WhatsApp account. This differs from tools built exclusively on the Business API, where an existing number must be de-registered before it can be used.
Can I sync WhatsApp group chats to Pipedrive?
Yes, via the Import Messages from Groups setting. A group is matched by its group ID rather than a phone number, and synced to a Pipedrive Person named after the group. It is off by default, which is usually the right choice unless group threads are genuinely part of your sales process.
Get started
Connect your existing WhatsApp account to Pipedrive in about five minutes, with no API access and no number migration. Start a free trial of the Pipedrive WhatsApp integration — no credit card required.