Before you start
- A Pipedrive account.
- A Make account, which is free, or a paid Zapier plan.
- Your assistant, with a lead or two already captured.
Steps
- In Make, create a new scenario, add the Webhooks module, choose Custom webhook, create one and copy its address. Make's free plan includes webhooks; Zapier's does not.
- In your dashboard, open Integrations, find "Zapier, Make and CRMs" and paste the address in. Save it, then press "Send a test lead".
- Go back to Make and it will have learned the shape of a lead. If it's still waiting, press "Send a test lead" again.
- Add a Pipedrive module and choose "Create a Person". Map name to lead.name, phone to lead.phone and email to lead.email. Pipedrive needs a name, so if lead.name is sometimes blank, set a fallback such as the phone number.
- Add a second Pipedrive module, "Create a Lead", and connect it to the person from the step before. A Pipedrive lead has no notes field of its own, so to keep lead.addressOrArea, lead.preferredTime and the dashboard link, add a "Create a Note" module after it and attach the note to the lead.
- Set the lead's title. Pipedrive refuses an empty one, so if lead.serviceType is sometimes blank, use your business name and the customer's name instead.
- Switch the scenario on. A scenario that's saved but switched off receives nothing, which is the step almost everyone forgets.
- Look in your CRM for a contact named "Test lead" on +44 7700 900000, then delete it. Then leave a real inquiry on your own website and watch that arrive too.
Platform steps checked on October 1, 2026 against Make: Pipedrive CRM integration
Good to know
- Use "Create a Deal" instead of "Create a Lead" if your pipeline starts at deals. The mapping is the same.
- The title is the field that most often breaks this. A customer who says "can someone call me" leaves no service type, and Pipedrive rejects the record.
- Each lead also says where it came from. source.page is the page it was asked from, source.referrer the site that sent the visitor and source.utm.campaign the campaign tag on your link. lead.qualifying holds the answers to your own questions, and lead.serviceArea says inside, outside or unknown if you've listed the places you serve. Map any of them to a custom field.
- The test lead is marked type "test" and a real one "lead.created". That's useful for keeping tests out of a live CRM, but if you add that filter before testing, the test button will look broken. Test first, filter afterwards.
- A lead that's refused is retried after 5, 10, 20, 40 and 80 minutes. Fix the problem within about two and a half hours and the lead still arrives on its own.
- Every retry of one lead carries the same id, so a repeat is safe to ignore.
Can't edit your website?
Every assistant has its own chat page. Link to it from your website's menu, your Google Business Profile, social media or email signature. Or use "Email this to my web person" on your Widget page to send the code to whoever runs your site.
Questions
Why does this take two steps when HubSpot takes one?
Pipedrive stores the person and the opportunity separately, so the person is created first and the lead is attached to them. It's how Pipedrive is built rather than anything about the chatbot. The HubSpot guide shows the one-step version.
Should I create a lead or a deal?
A lead, if you qualify inquiries before they enter your pipeline. A deal, if every inquiry goes straight into the pipeline. Both work the same way here.
What happens if the title is empty?
Pipedrive rejects the record and your Integrations page shows the connection as failing, with a count. Set the title to something that is always present, such as your business name and the customer's name.