Pipedrive works because it keeps you looking at the pipeline: every deal in a column, every next step visible. It works less well when the deal never gets into the pipeline in the first place, because the enquiry came in through your website chat at 10pm or a WhatsApp message on Sunday and nobody typed it in.
Klugon can act as a Pipedrive AI assistant for exactly that gap. Once you paste your Pipedrive API token into Klugon, the assistant in your website chat and messaging channels can add the customer to Pipedrive as a person, open a deal for them in the pipeline you choose, attach a note with what they asked for, and later look them up again by email or phone.
Of Klugon's CRM connections, Pipedrive is the one that does the most in a single step, and the one that is quickest to set up. This page explains exactly what it writes, how to connect it, which plan you need and what it doesn't do. Two points to keep in mind from the start: a person and deal are created when the assistant uses its CRM tool in a conversation, not automatically for every lead, and phone calls don't use the Pipedrive connection.
How the Pipedrive AI assistant connection works
With Pipedrive connected, Klugon gives the assistant three Pipedrive tools in its text conversations.
Adding a person and opening a deal
The tool sync_lead_to_crm takes the customer's name and, where they've given them, their email and phone, plus a short note or reason for the enquiry. Klugon then:
- Looks for an existing person in Pipedrive with the same email address. If there's no email match, it tries the phone number. Both are exact-match searches.
- Updates or creates the person. If a match is found, Klugon updates that person's name, email and phone with what the customer gave. If not, it creates a new person.
- Checks for an open deal. If that person already has an open deal, Klugon leaves it alone and doesn't open another. If they have none, it creates a new deal linked to the person.
- Adds the note. If the assistant included a note or reason, Klugon adds it as a Pipedrive note attached to both the person and the deal.
That open-deal check matters. A returning customer who messages twice in a week doesn't end up with two deals cluttering the pipeline.
When lead capture is switched on for the assistant, it is prompted to collect a customer's name, email and phone when appropriate using the CRM tools. So in most enquiries, a person and deal are created once someone has shared their details. It is still the assistant's decision in each conversation, which is why we don't call it automatic sync.
Looking someone up
The tool search_crm_contact searches Pipedrive persons by email or phone, using an exact match, and returns the first person found with their ID, name, email and phone.
Logging a note
The tool create_crm_note adds a note to a Pipedrive person the assistant has found or created. The note begins with the activity type in square brackets, such as "[note]" or "[call]", followed by the assistant's text.
What data goes into Pipedrive
Here is exactly what Klugon writes.
The person
| Pipedrive person field | What Klugon sends |
|---|---|
| Name | The customer's name as given (or their email or phone if no name was given) |
| The customer's email, labelled "work" and marked primary | |
| Phone | The customer's phone number, labelled "mobile" and marked primary |
When Klugon updates an existing person, it sends the email and phone as the primary values. Check how that interacts with people who have several emails or numbers in your Pipedrive.
The deal
| Pipedrive deal field | What Klugon sends |
|---|---|
| Title | The customer's name followed by "deal", for example "Jamie Lee deal" |
| Person | Linked to the person above |
| Pipeline | The pipeline ID you set in Klugon, or your default pipeline if you left it blank |
| Stage | The first stage of the pipeline you set; with no pipeline set, Pipedrive's default applies |
Klugon doesn't set the deal value, currency, expected close date, owner, labels or custom fields. Pipedrive applies its own defaults.
The note
The note or reason for the enquiry, as written by the assistant, attached to the person and the deal.
What doesn't go into Pipedrive
Klugon doesn't create organisations, activities, products or Pipedrive leads (the items in Pipedrive's Leads Inbox). It doesn't move deals between stages, mark them won or lost, or change their value. The chat transcript isn't copied, beyond the notes.
Pipedrive draws a line between leads and deals. Its help article on leads vs. deals describes leads as unqualified prospects and deals as qualified opportunities moving through stages. Klugon goes straight to a deal. If you prefer new enquiries to land somewhere separate from your active sales, set a dedicated pipeline for them, as described below.
What comes back from Pipedrive
Only search results. Klugon doesn't import your Pipedrive people, deals or pipelines into its own lists.
Which conversations use Pipedrive
The Pipedrive tools run in Klugon's chat engine, which handles:
- the AI chatbot on your website;
- WhatsApp, Instagram, Messenger and Telegram conversations (see the WhatsApp AI chatbot).
Phone calls don't use the Pipedrive connection. The AI phone receptionist saves leads into Klugon's own Leads list, but it doesn't have the Pipedrive tools. The Zapier section below covers a route that includes calls.
Setting up the Pipedrive AI assistant connection
This is the simplest of Klugon's CRM connections: one token, one optional pipeline ID.
Step 1: copy your Pipedrive API token
The Klugon setup guide says: "In Pipedrive, open your profile menu → Personal preferences → API." Pipedrive's help article on finding your personal API key gives the same location: Settings, then Personal preferences, then API.
If you can't see the API tab, Pipedrive notes that your permission set may not include it. Ask your Pipedrive admin.
Everything Klugon creates is created as the user whose token you paste, with that user's permissions and visibility. Pipedrive also warns that the key gives access to your account, so treat it like a password.
Step 2: choose a pipeline (optional)
If you leave the pipeline blank, new deals go into your default pipeline. If you want enquiries from the assistant to land somewhere specific, for example a pipeline called "Website and WhatsApp enquiries", create it in Pipedrive first. Pipedrive's guide to using multiple pipelines explains how.
To get the pipeline ID, the Klugon setup guide says: "open the pipeline you want new deals in and copy the number at the end of its URL as the pipeline ID." New deals then go into the first stage of that pipeline, so make the first stage something like "New enquiry".
Step 3: connect Pipedrive in Klugon
- In the Klugon dashboard, open Integrations.
- Find Pipedrive by searching or with the CRM filter.
- Click Connect. The panel shows two fields and a collapsible Setup Guide.
- Paste the token into API token.
- Optionally, enter the number in Pipeline ID (optional).
- Save.
Klugon checks both values with Pipedrive when you save. If the token is wrong, you'll see "Pipedrive rejected that API token. Copy it again from Personal preferences → API." If the pipeline doesn't exist, you'll see a message saying Pipedrive has no pipeline with that ID, with the suggestion to leave it blank. Once it saves, the connection works.
The card then shows Configure, with Update Credentials to change the token or pipeline and Disconnect to remove the connection. The token is masked when you reopen the panel.
Step 4: switch on lead capture
In the assistant's settings, make sure lead capture is on, so the assistant collects details and uses its CRM tools. If you've hand-picked the assistant's tool groups, keep "External CRM" switched on.
Which plan includes Pipedrive
Pipedrive is part of the feature Klugon's billing calls "Google Calendar, HubSpot and Zoho sync" (the label is shorter than the list: it covers Pipedrive too). It's included on:
- Voice plans: Business ($299 a month) and Scale ($499 a month);
- Social plans: Business ($249 a month) and Scale ($449 a month).
It isn't in any chat widget plan or any Starter plan. Without it, the Pipedrive card shows a locked button naming the feature and the Business plan, linked to Billing. Yearly prices are on the pricing page.
The trial is 7 days. A card is required, and you're charged at the end unless you cancel.
Limits of the Pipedrive connection
- Not automatic. A person and deal are created only when the assistant uses its CRM tool in a conversation.
- Exact matching. Emails and phone numbers must match exactly as stored in Pipedrive. "07700 900123" and "+447700900123" are different to an exact search, so a returning customer may become a second person.
- Any open deal blocks a new one. If the person has an open deal anywhere, even in a different pipeline, no new deal is created for the new enquiry. The note is attached to the existing open deal.
- One CRM at a time. With several CRMs connected, Klugon uses one, in this order: HubSpot, Zoho CRM, Salesforce, Pipedrive. Pipedrive is last, so if any of the others is also connected, Pipedrive is ignored.
- No phone calls. The phone assistant doesn't use Pipedrive.
- Single user's token. Records are created as the user who owns the token.
What the Pipedrive AI assistant doesn't do
- It doesn't sync every Klugon lead automatically.
- It doesn't move deals between stages or mark them won or lost. The dashboard has no deal-stage tool for the assistant.
- It doesn't set deal values, owners or close dates.
- It doesn't create organisations, activities or Leads Inbox items.
- It doesn't import Pipedrive data into Klugon.
- It doesn't run on phone calls.
- It doesn't replace Pipedrive's own chatbot or web forms. Conversations stay in Klugon's inbox.
Getting every lead into Pipedrive with Zapier
If you need every enquiry in Pipedrive, including phone calls, add Klugon's Zapier connection. Klugon sends a lead.created event to Zapier whenever a lead is created on any channel. It includes the name, email, phone, intent, source, notes, conversation ID and marketing consent, and a Zap can turn it into a Pipedrive person and deal.
Zapier also needs a Business plan or higher. If you run both routes, decide which one creates deals, or the same enquiry may appear twice.
A sample conversation with Pipedrive connected
This is a sample conversation for a made-up web design studio, Fernlight Studio. It shows the order of steps and is not a real customer.
The next morning, the studio sees "Jamie Lee deal" in the first column of its enquiries pipeline, with the note attached.
Practical tips
Give the assistant's enquiries their own pipeline
A dedicated pipeline, with a first stage called something like "New from assistant", keeps automated enquiries visible and separate. Move good ones into your main pipeline when they qualify.
Standardise phone formats
Because matching is exact, decide on a phone format (for example, international with +44) and ask the assistant, in its instructions, to confirm numbers in that format. It reduces duplicate people.
Ask for an email
Email is the first thing Klugon matches on. Encourage the assistant to ask for one when a customer wants to be contacted.
Watch the open-deal rule
If your business sells repeatedly to the same customers, remember that a person with any open deal won't get a new one. Close old deals promptly, or the new enquiry will be noted on the old deal instead.
Keep Klugon's Leads list in view
Klugon's Leads list has every lead, from every channel. Pipedrive has the ones synced from chat and messaging. Pair it with Slack notifications for a ping on each new lead.
Pipedrive compared with Klugon's other CRM connections
| CRM | What a synced lead becomes | Matching before writing | Klugon plan |
|---|---|---|---|
| Pipedrive | A person, plus a deal if they have no open one | Email, then phone | Business and above |
| HubSpot | A contact | By email | Business and above |
| Zoho CRM | A new lead | None | Business and above |
| Salesforce | A new Lead | None | Scale |
See HubSpot, Zoho CRM and Salesforce for details, or browse every connection on the integrations page. The AI sales assistant page covers how the assistant qualifies enquiries.
Frequently asked questions
Does every Klugon lead go to Pipedrive automatically?
No. The assistant creates the person and deal when it uses its CRM tool in a chat or messaging conversation. For every lead from every channel, use Klugon's Zapier connection, which fires on each new lead.
Does it create a deal every time?
Only if the person has no open deal. If they already have one, Klugon doesn't open another, and the note goes on the existing open deal.
Which pipeline and stage do new deals go into?
The pipeline whose ID you entered in Klugon, in its first stage. If you left the pipeline blank, the deal goes into your default pipeline.
Can the assistant move deals through stages?
No. It can create people and deals, search people and add notes. It can't change a deal's stage, value or status.
Do phone calls create Pipedrive deals?
Not through this integration. The AI phone receptionist saves leads in Klugon only. Zapier's lead.created event includes phone leads, so use that route for calls.
Will it create duplicate people?
It matches on email first, then phone, using exact matches. A customer who gives the same details again is matched. Different spellings or phone formats can create a second person.
Does it use Pipedrive's Leads Inbox?
No. Klugon creates people and deals, not Leads Inbox items.
Which Klugon plan includes Pipedrive?
A voice or social plan on the Business tier or above. It isn't part of the chat widget plans.
For small sales teams that run on Pipedrive, this connection turns a chat or WhatsApp enquiry to Klugon's AI receptionist into a person, a deal and a note in your pipeline while the customer is still in the conversation. Add Zapier if you also want phone enquiries there.