Send website inquiries to Pipedrive
Pipedrive is built around the pipeline, and the pipeline starts with a person. This puts each inquiry from your site into Pipedrive as a person the moment it arrives, with their name, email address and phone number, so the first thing you do with a new lead is add them to a deal rather than type them in off an email.
It is a copy, not a move: the inquiry still lands in your Webkio Inbox, and the notification email you already get still goes out. Send your website inquiries to your CRM covers what is shared by every destination; this page is the Pipedrive part.
What you need
| Field | Where it is |
|---|---|
| Company domain | The first part of the address you log in at. If you log in at acme.pipedrive.com, enter acme, nothing else. |
| API token | Click your avatar (top right) > Company settings > Personal preferences > API. Copy the token shown there. |
The token acts as you in Pipedrive, with everything you can do, so it is stored encrypted and never shown again. If it leaks, generate a new one on the same page; the old one stops working at once. Paste the new one into the destination.
Setting it up
- Open Project settings > CRM for the site.
- Choose Pipedrive under CRM.
- Enter the company domain and the token.
- Tick which inquiries to send. Contact forms and property inquiries are the two kinds that exist; orders and bookings are never sent, for the reason the shared page gives.
- Add destination, then Send test.
There is no field mapping to check. A person in Pipedrive has fixed fields, and every one of ours that fits goes into the one with the same meaning.
What arrives
| In Pipedrive | From the inquiry |
|---|---|
| Person name | Their full name. If the form had no name, their email address stands in. |
| Email (work, primary) | Their email address. |
| Phone (work, primary) | Their phone number, when the form asked for one. |
| Owner | You, because the token is yours. |
The person is created with the API's persons call on your own company domain, which is why the domain is a field: Pipedrive answers each company at its own address.
What does not arrive
Their message. A person in Pipedrive has no free-text field it could go in. The place Pipedrive keeps a message is a note or a lead, and both have to be attached to a person that already exists, which is a second step this integration does not take: it makes one write per inquiry, by design, so that nothing can half-succeed. The message is in your Webkio Inbox in full, and in the notification email.
Their company, for the same reason: an organization is its own record in Pipedrive, created separately.
A deal. Nothing is added to a pipeline stage. You decide who becomes a deal.
De-duplication. A second inquiry from the same person makes a second person. Pipedrive's own Merge duplicates tool (under Contacts) finds them by email, and a merge keeps everything from both.
When something fails
Pipedrive answers every failed call with a short JSON message, and the destination card shows it word for word.
| What the destination shows | What it means | What to do |
|---|---|---|
A 401 answer, "success":false |
The token is wrong, has been regenerated, or belongs to a different company than the domain you entered. | Copy the token again from Personal preferences > API, and check the domain is the first part of your login address and nothing more. |
| A web page rather than an API response | The company domain is wrong: Pipedrive sent back its login page. | The domain is only the part before .pipedrive.com. "acme", not "acme.pipedrive.com" and not "https://acme". |
A 403 answer with a code naming a limit |
Your Pipedrive plan has hit a cap on what it can create. | That is a Pipedrive plan matter; the test will pass again once the cap is lifted. |
| Accepted, but no person appears | Pipedrive did store it, under the user whose token this is. | Check Contacts > People, with no filter and sorted by date added. If another person on the account owns the token, the new person is theirs. |
Four failures in a row with the same answer pause the destination, so a dead token does not keep knocking. Fix the value and Resume.
Frequently asked questions
Can I send the message too?
Not with a single write, which is what this does. If the message matters more than the person record, Pipedrive takes a plain JSON webhook through its own automations and through Make or n8n; the webhook destination sends everything, message included, to any of those.
Does it create a deal or a lead?
No. It creates a person. Deals and leads in Pipedrive need a person first, and which stage a new inquiry belongs in is your call, not ours.
Which user owns the new people?
Whoever generated the token. If you want inquiries owned by a particular salesperson, use a token generated while logged in as them.
What happens if Pipedrive is down?
The inquiry waits and is retried with growing gaps. It was in your Webkio Inbox before the first attempt, so nothing is lost either way.
Does it work on every Pipedrive plan?
API access is on every Pipedrive plan. If a plan limit stops a person being created, Pipedrive says so in the answer and the destination shows it.
Can I send to Pipedrive and to Slack at the same time?
Yes. Add both destinations; each inquiry goes to each one, once.
Related reading
- Send leads to your CRM - the switchboard every destination hangs off.
- All your customers in one place - the record that stays here whatever is sent on.
- Understanding notifications - the email and bell alerts that fire alongside a delivery.
- Integrations - every destination and connector on one page.
- The automated emails every business should send - the follow-up once a lead is in your CRM.