Skip to content
WbizTool

Integrations

Pipedrive and WhatsApp

Connect Pipedrive to the WhatsApp number you've linked to WbizTool. Message a person when their deal moves to a stage, and log the WhatsApp messages they send you as notes in Pipedrive.

WbizTool has no Pipedrive app. You connect the two with a tool you may already use: Pipedrive's own Automations, Zapier, Make, n8n or Pabbly Connect. This page shows each route step by step, with ready-made templates for Make and n8n.

Who can do it: anyone with a WbizTool API key can send messages. Logging incoming messages needs the Unibox add-on ($20 a month or $200 a year at US list prices for each inbox number, on a paid or lifetime plan) and an Owner or Editor to set up the webhook. In Pipedrive, you need the rights your route asks for (see Pick a route).

What you can do#

DirectionExampleWhat it needs in WbizTool
Pipedrive → WhatsAppA deal moves to Proposal sent: the person gets "Hi Emma, your proposal is in your inbox." A new person is added: they get a welcome message.An API key and a connected WhatsApp number.
WhatsApp → PipedriveA customer writes to your WhatsApp number: the message is added as a note on the person with that phone number, and the person is created if Pipedrive doesn't have them.The Unibox add-on, and the number added on Inbox numbers.

Messages go out from your own WhatsApp number, so WhatsApp's rules apply: message people who expect to hear from you, such as your leads and customers.

Before you start#

Pick a route#

RoutePipedrive → WhatsAppWhatsApp → PipedrivePipedrive plan and rights
Pipedrive AutomationsYes, with no other tool: the automation's webhook action calls the WbizTool API.NoAutomations and their webhook action are on Growth and higher plans. Only global admins create the automated webhook.
ZapierYes, with the WbizTool app's actions.Yes, with the WbizTool Incoming WhatsApp Message trigger.Any plan with Zapier access.
MakeYes, with Make's HTTP module. Blueprint below.Yes, with a Make webhook. Blueprint below.Any plan. The blueprints use Pipedrive's webhooks (all plans) and a Pipedrive API token.
n8nYes, with the Pipedrive Trigger and the WbizTool node. Workflow below.Yes, with a Webhook node and the Pipedrive node. Workflow below.Any plan. n8n needs a Pipedrive API token.
Pabbly ConnectYes, with its API (Pabbly) request action.Yes, with its webhook trigger.Any plan.

Pipedrive's own Webhooks (all plans) post a fixed body that the WbizTool API can't read, so they don't call WbizTool directly. They start a Make, n8n or Pabbly workflow instead, as in the Make recipe.

Phone numbers#

The two sides write numbers differently. Keep these rules in mind when you map fields:

  • To send, pass the Pipedrive phone as it is. The Send message API removes spaces, dashes, dots, brackets and the +. A number written with +, such as +44 20 7946 0018, keeps its own country code. A local number, such as 020 7946 0018, needs country_code (here 44), or it goes to the wrong number or fails.
  • Incoming messages give digits only. In the webhook, contact.phone is the number without +, such as 442079460018. Search Pipedrive with these digits, and add a + in front when you create a person.
  • Pipedrive keeps phones as typed. Its search finds a person by the digits of their number, but a number saved without its country code can be missed. Save numbers with the country code.
  • Hidden numbers and groups. WhatsApp sometimes hides a sender's number: then contact.phone is empty and contact.phone_hidden is true. Group chats have contact.is_group set to true. The recipes below skip both.

Pipedrive Automations#

Pipedrive's Automations can send a webhook request as an action. Point it at the WbizTool Send message API and the automation sends the WhatsApp message itself, with no other tool.

In Pipedrive: a Growth or higher plan. Only global admins can create the automated webhook; creating the automation needs the rights to use Automations.

  1. Create the automated webhook

    In Pipedrive, open the account menu and go to Tools and apps → Webhooks. Click + Webhooks and choose Automated webhook. Name it "WbizTool", and enter https://wbiztool.com/api/v1/ as the endpoint URL. The URL must end with /, because the automation adds the path. Leave the authentication empty: the WbizTool credentials go in the body.

  2. Create the automation

    Open the account menu at the top right, go to Tools and apps → Automations and click + Automation. Select Event trigger, choose deal as the item and set the trigger event to Updated. Select the deal's stage as the field to monitor for changes, and click Apply trigger. Then add a condition specifying the deal stage name, so the automation runs only when a deal moves to that stage.

    For a welcome message, choose person as the item and the Added event instead.

  3. Add the webhook action

    Add the webhook action and choose the "WbizTool" webhook. Set the method to POST and add the path send_msg/.

  4. Fill in the body

    Choose the Key-value body and add the fields below. Use the field button to insert the person's phone and name.

    KeyValue
    client_idYour Client ID.
    api_keyYour API key.
    whatsapp_clientThe WhatsApp Client ID of the number to send from.
    phoneThe contact person's phone, from the field button.
    country_codeOnly if your Pipedrive numbers are local, without a country code: the calling code, such as 44.
    msgYour message, such as Hi [person's first name], your proposal is in your inbox. Reply here if you have questions.

    You can also choose Raw and write the same fields as JSON. With Key-value you don't need to watch for quotes in names.

  5. Test it

    Save the automation, set it to active and move a test deal to the stage. Open Automations → History and the run: it shows the body that was sent. WbizTool answers "status": 1 when the message is queued; an error is answered with HTTP 400 and a message, such as Invalid phone number.

Zapier#

Use the WbizTool app on Zapier with Pipedrive's Zapier app.

A deal changes stage: send a WhatsApp message#

  1. Trigger: Pipedrive Updated Deal Stage

    Choose Pipedrive and the Updated Deal Stage trigger. For a welcome message, use New Person instead.

  2. Filter: only your stage

    Add Filter by Zapier and continue only when the deal's stage is the one you want. The trigger runs for every stage change.

  3. Find the person's phone

    If the trigger's data has no phone for the deal's person, add Pipedrive's Get Person search with the deal's person ID.

  4. Action: WbizTool Send Text-Only WhatsApp Message

    Pick your sending number under WhatsApp Number. Map the person's phone to Phone Number, fill Country Code only if your Pipedrive numbers are local, and write the Message with the person's name.

  5. Test and publish

    A successful step means the message was queued. If WbizTool can't accept it, the step fails with the reason, such as WbizTool: Invalid phone number.

A WhatsApp message arrives: add a note in Pipedrive#

Needs the Unibox add-on. See Trigger requirements.

  1. Trigger: WbizTool Incoming WhatsApp Message

    Pick the number under WhatsApp Number. When you publish the Zap, WbizTool adds the number to the inbox and posts its received messages to Zapier.

  2. Filter: people, not groups

    Add Filter by Zapier: continue only when Is Group is false and Contact Phone Hidden is false.

  3. Find or create the person

    Add Pipedrive's Find or Create Person: it searches people on a field (choose the phone field, with Contact Phone) and creates a person when none is found. For a new person, set the name to Contact Name and the phone to + followed by Contact Phone.

  4. Create the note

    Add Pipedrive's Create Note. Link it to the person from the previous step, and write the content, for example: WhatsApp from Contact Name: Message Content, with Message Time if you want the time.

Make#

There's no WbizTool app on Make. The two blueprints use Make's own Webhooks, HTTP and JSON modules: the HTTP module calls the WbizTool API and Pipedrive's API.

BlueprintWhat it does
pipedrive-deal-stage-to-whatsapp.blueprint.jsonPipedrive's webhook (a deal changed) → filter on your stage → get the deal's person → send them a WhatsApp message.
whatsapp-to-pipedrive-note.blueprint.jsonWbizTool's incoming message webhook → find the person by phone → add a note, or create the person first.

The blueprints are built on Make's generic modules, so they work on any Make plan and need no Pipedrive connection in Make.

You need your Pipedrive API token (in Pipedrive, Settings → Personal preferences → API) and your Pipedrive company address, such as yourcompany.pipedrive.com.

A deal changes stage: send a WhatsApp message#

  1. Import the blueprint

    Create a scenario in Make, click the three dots in the bottom bar, choose Import Blueprint and pick the file.

  2. Create the webhook

    Open the first module (Webhooks → Custom webhook), click Add, save, and copy the address Make shows.

  3. Fill in the placeholders

    • In the filter after the webhook, replace YOUR_STAGE_ID with the ID of your stage. To find it, move a test deal to the stage once and read data.stage_id in the webhook's output.
    • In the Get the person module, replace YOUR_COMPANY and YOUR_PIPEDRIVE_API_TOKEN.
    • In the Send WhatsApp module, replace YOUR_WBIZTOOL_API_KEY in the Authorization header, YOUR_WHATSAPP_CLIENT_ID in the body, and the message text.
  4. Point Pipedrive's webhook at Make

    In Pipedrive, go to Settings → Tools and apps → Webhooks and create a webhook: event action change (updated in older versions), event object deal, and the Make address as the endpoint URL.

  5. Turn it on

    Turn the scenario on and move a test deal to the stage. The HTTP module's output shows WbizTool's answer: "status": 1 means the message was queued.

To build it with Make's Pipedrive modules instead, use Watch New Events (or a Custom webhook as above), Get a Person, and the HTTP module with the same request as the blueprint's Send WhatsApp module. Make's Pipedrive modules return a deal's person as an ID only, so you need Get a Person for the phone.

A WhatsApp message arrives: add a note in Pipedrive#

  1. Import the blueprint

    Import whatsapp-to-pipedrive-note.blueprint.json in a new scenario.

  2. Create the webhook

    Open Webhooks → Custom webhook, click Add, save and copy the address.

  3. Fill in the placeholders

    Replace YOUR_COMPANY and YOUR_PIPEDRIVE_API_TOKEN in the four Pipedrive HTTP modules (search, create the person, and the two notes).

  4. Add the address in WbizTool

    On Inbox numbers, add your number to the inbox, or open Webhook settings on its card. Paste the Make address under Webhook URL, keep only Received messages ticked, and save.

  5. Turn it on and test

    Turn the scenario on and send your WhatsApp number a message from another phone. Within a minute or two the note appears on the person in Pipedrive.

The blueprint skips group chats, hidden numbers and sent messages. To build it with Make's Pipedrive modules instead, use Search Persons on the phone field, a router, Create a Person and Create a Note.

n8n#

Use n8n's Pipedrive Trigger and Pipedrive nodes with the WbizTool community node (n8n-nodes-wbiztool). Install the community node first.

WorkflowWhat it does
pipedrive-deal-stage-to-whatsapp.n8n.jsonPipedrive Trigger (deal changed) → If the deal moved to your stage → Pipedrive Get person → WbizTool Send Message.
whatsapp-to-pipedrive-note.n8n.jsonWebhook (WbizTool's incoming message) → If it's a person's message → Pipedrive Search person by phone → Create a note, creating the person first when none is found.
  1. Import the workflow

    In n8n, create a workflow, open the ⋯ menu and choose Import from File. You can also paste the file's contents on the canvas.

  2. Add the credentials

    Open each Pipedrive node and create a Pipedrive API credential with your Pipedrive API token (Settings → Personal preferences → API in Pipedrive). Open the WbizTool Send Message node and choose your WbizTool API credential (Client ID, API key and the WhatsApp Client ID to send from).

  3. Set your stage and message

    In the first workflow, replace YOUR_STAGE_ID in the If node with your stage's ID (move a test deal to the stage and read data.stage_id in the trigger's output), and edit the Message Text. Leave Country Code empty when your Pipedrive numbers include the country code.

  4. Activate

    Activate the workflow. The Pipedrive Trigger creates its webhook in Pipedrive by itself.

    For the second workflow, copy the Production URL of the Webhook node and paste it under Webhook URL on Inbox numbers, with only Received messages ticked.

The Pipedrive nodes in these files are version 2 of n8n's Pipedrive node. If your n8n is older and shows them as unknown, update n8n or replace them with your version's Pipedrive node, using the same settings.

Pabbly Connect#

There's no WbizTool app on Pabbly Connect: use its general modules.

  • Pipedrive → WhatsApp: start the workflow with Pabbly's Pipedrive trigger, or with its webhook trigger fed by a Pipedrive webhook. Then add API (Pabbly) with Execute API Request to https://wbiztool.com/api/v1/send_msg/, set up as in Pabbly Connect, and map the person's phone and name.
  • WhatsApp → Pipedrive: start with Pabbly's webhook trigger, paste its address under Webhook URL on Inbox numbers, and send a test message to your number so Pabbly sees the fields. Then add Pabbly's Pipedrive steps: find the person by contact.phone, create them if needed, and add a note with message.content.

What arrives from WhatsApp#

Each incoming message is one JSON request. The fields the recipes use:

FieldExampleUse it for
eventmessage_receivedSkip message_sent if you ticked Sent messages too.
contact.phone12125550120The Pipedrive search, and the new person's phone (with +).
contact.nameEmma ThompsonThe new person's name. Can be empty: use the phone then.
contact.is_group, contact.phone_hiddenfalseSkip group chats and hidden numbers.
message.contentCan I add a gift note to it?The note. Photos and files arrive as a label, such as 📸 Image.
message.timestamp2026-10-15T10:30:04+00:00When it was sent, in UTC.

All fields, the signature and the retries are on Inbox numbers and incoming message webhooks.

Troubleshooting#

ProblemWhat to check
Auth Error: invalid api keyThe key was deleted or mistyped, or doesn't belong to the Client ID's workspace. In Make and n8n, check the Authorization: Bearer header or the credential.
Invalid phone numberThe phone field was empty or held something else, such as a name. Check that the person has a phone in Pipedrive and that you mapped the phone field.
The message went to the wrong numberPipedrive has the number without its country code. Save it with the code, such as +44 20 7946 0018, or send country_code.
Invalid JSON format: …A raw JSON body broke, often on a quote or a line break in a mapped field. In Pipedrive Automations use the Key-value body; in Make keep the blueprint's JSON modules.
The automation's run says "Maximum retry limit reached"WbizTool answered with an error. Open the run in Automations → History and read the body that was sent.
No webhook arrives from WbizToolThe number must show Syncing on Inbox numbers, with Received messages ticked, on the Unibox add-on. Make, n8n and Pabbly must answer 2xx within 8 seconds: turn the scenario or workflow on. Messages are posted within a minute or two.
Your server or firewall refuses WbizTool's webhookAllow requests with the User-Agent WbizTool-Webhooks/1. Some hosts block unknown clients with 403.
A note is added but the person isn't found, so a duplicate person is createdThe person's number in Pipedrive is saved in another form, such as without the country code. Save it with the code, then merge the two people in Pipedrive.
Nothing happens for a group messageThat's on purpose: the recipes skip group chats and hidden numbers, which have no phone to match.