Connect WhatsApp to Pipedrive on a Coexistence number

How does a WhatsApp message reach a Pipedrive person?

Meta posts each message on the number to the webhook destination you set for it, here an n8n Webhook node. The workflow searches Pipedrive persons with the sender's number; Pipedrive's person search covers the phone field and accepts an exact match flag. When a person comes back, the workflow uses that id. When none does, it creates a person with the WhatsApp profile name and the number, then a lead linked to them, so a first message from a stranger turns up in the Leads Inbox for someone to qualify.

The message itself becomes a note. A Pipedrive note needs only its content, which accepts HTML, and at least one of a person, deal, organisation or lead id. Attach it to the open deal when there is one, and to the person otherwise.

Why does the search step hit limits first?

Because Pipedrive gives search its own, much smaller allowance. General API calls are limited per user over a rolling two-second window, from 20 requests on Lite with an API token up to 120 on Ultimate. The Search API is held to 10 requests per two seconds on every plan.

A quiet number never notices. A number that sends a template to a few hundred customers and gets fifty replies in a minute will, because each reply starts with a search. The workflow then sees 429 responses and, without a retry, drops the note.

Two things fix it. Turn on retries with a wait on the Pipedrive search node, and cache the phone to person id mapping in n8n's workflow static data or a small table, so a customer who sends six messages in a row costs one search, not six.

Can replies typed on the phone be logged too?

Yes. Coexistence keeps the WhatsApp Business app working on the same number, and when someone on the team replies from it, Meta sends an echo of the outgoing message to the same webhook destination under the smb_message_echoes field.

Add a branch for those echoes and log them as notes marked outbound, or as completed activities if your team reports on activity counts. A salesperson opening the deal then sees what the customer asked and what the shop answered, in order.

For messages the workflow sends itself, such as a template when a deal moves stage, log the note at the moment of sending. The workflow already has the text and the deal id, so there is no reason to wait for a webhook.

How should the phone number be normalised?

To digits with the country code and nothing else, because that is what Meta sends. A sender arrives as 14155550188, while a person typed into Pipedrive by hand may read +1 (415) 555-0188.

When the workflow creates a person, store the number in that digits-only form so its own records always match. For people created by hand, a one-off cleanup in n8n that rewrites existing phone values into the same form pays for itself the first week. Without it, the exact match search misses people the team entered and the workflow creates a duplicate for each of them.

Keep the original formatting in a second phone entry if the team likes reading it that way. Pipedrive persons can hold more than one phone.

Common mistakes

• Running one search per message with no cache. Bursts of replies run into the 10 per two seconds Search API limit and notes go missing.
• Creating a lead for every message rather than every new person. The Leads Inbox fills with copies of the same customer.
• Attaching notes only to the person when a deal is open. The rep working the deal never sees the conversation.

Frequently asked questions

Keep reading