Send chatbot leads to Pipedrive
A person, or a lead in the Leads Inbox
A lead from the chat becomes a person in your account, or a lead in the Leads Inbox with the person already attached to it -- which is what a Pipedrive lead needs and cannot exist without.
What it does
The Leads Inbox, properly
A Pipedrive lead cannot stand on its own. The person is created first and the lead attached to it, so it arrives the way one made by hand does.
Your custom fields
Read from the account, with dropdown choices sent as option ids. A dropdown answered with a label Pipedrive does not have is left out rather than failing the record.
People, organizations and deals too
Route different widgets to different record types: a pricing question into the Leads Inbox, a partner enquiry into an organization.
How to connect it
Read the full guide- 1
Copy your API token
Pipedrive, your profile menu, Personal preferences, then the API tab.
- 2
Connect Pipedrive
Paste the token. We verify it and name the company it belongs to.
- 3
Create a route
Choose which leads it takes and which record type they become.
- 4
Map the fields
Auto-map, then check the dropdowns. The dispatch log keeps every attempt.
Questions people ask
Which token should I use?
A personal API token. It carries the visibility of the person who made it, so make it with a user who can see the pipeline you are writing into.
Will it create duplicates?
It creates a record per lead. Pipedrive's own merge tools are where two records become one; we do not guess that two people are the same person.
Can it move a deal along a pipeline?
No. Creating a deal is one thing; moving it is a sales decision rather than a chat one.
What teams use it for
Upload your documents, get answers that cite them
One knowledge base, an AI chat or an Ask AI search on any site, and every answer with the passage it came from. Free for 14 days.