What this connection does
Every time Lead Recorder logs a new lead, a Zap creates a Deal in Pipedrive, with a Person attached and the source sitting on both. Six months later, filtering deals by source tells you which channel is actually worth the budget, not just which one generates the most enquiries.
Field mapping
| Lead Recorder field | Pipedrive field | Notes |
|---|---|---|
| nameField + utmSource | Deal title | e.g. "Ella Rossi, Google Ads" |
| emailField | Person email | Used to find-or-create the Person |
| phoneNumber | Person phone | |
| utmCampaign | Custom field: Campaign |
Setting it up
Add a Find Person step before Create Deal
In the Zap, search Pipedrive for an existing Person by email first. Only create a new Person if none is found, see the gotcha below.
Open the Zap template and connect both accounts
Use the embed below, or open the template directly on Zapier. Connect Lead Recorder as the trigger and Pipedrive as the action.
Map the deal and person fields
Match each Lead Recorder field to its Pipedrive field using the table above.
Send a test lead
Submit a form or click-to-call on your own site and confirm exactly one Person and one Deal are created, not two of each.
What catches people out
What catches people out
Pipedrive creates a Person and a Deal as separate objects. A Zap that just creates a new Deal every time, without checking for an existing Person, quietly builds up duplicate Person records for anyone who enquires twice. Use a search-then-create pattern: find the Person by email first, and only create one if the search comes back empty.
What it looks like when it's working
Qualified
Ella Rossi, Google Ads
$0 · Emergency Plumber Sydney
Stop guessing which channel closes.
Start recording.
Your next lead is about to hit your website. Know exactly where it came from, all the way through to the deal.
No credit card required · Included on every plan
Found you via Google Ads · "best plumber near me"
Found you via Organic Search · "emergency electrician"
Found you via Facebook Ads