CLIENT PROJECT
Lead Qualification Router
Qualification form → phone-match router → Pipedrive deal → Google Sheets log → "Qualified" / "Not Qualified" tag in ActiveCampaign, before a rep opens the inbox.
Read the case →Home › Blog › Sync Pipedrive and ActiveCampaign without duplicates
// blog
Sync Pipedrive and ActiveCampaign without duplicates
Duplicates are not a CRM bug. They happen because leads enter from three doors — a form, an opt-in page, a calendar — and each door creates a record without asking whether the person already exists. The fix is one pattern applied at every door. This is how the three Make.com scenarios in my case studies do it.
Why duplicates happen
- Every entry point calls Create person instead of Find, then create or update.
- The identity key is inconsistent: one form collects email, another only a phone number, the calendar sends a name and an email with different capitalisation.
- Tags in the email tool are added without checking what is already there, so "Lead" becomes "Lead, Lead, Qualified, Lead".
- When an API call fails, the scenario retries from the top and creates the record a second time.
The pattern, step by step
- Normalise the identity key first. Lower-case and trim the email; convert the phone to E.164 (+1…, +44…) before any lookup. Do this in the first module, once.
- Search Pipedrive by email. If nothing comes back and you have a phone number, search by phone. Two lookups cost two operations and save a duplicate every day.
- Router: new vs. returning. Empty result → create the person and a deal in the right stage. Match → update the person's fields that changed, and update the existing open deal instead of opening a second one.
- Tag idempotently in ActiveCampaign. Find the contact by email, read its tags, add only the tag that is missing. "Qualified" / "Not Qualified" are mutually exclusive — remove one when you add the other.
- Log one row per event to Google Sheets (timestamp, source, email, action taken). It is the cheapest audit trail you will ever have, and the first place you look when sales says "where did this lead go?".
- Error handling on every external call. Retry three times with a short back-off; if it still fails, route to an error branch that alerts a human with the payload attached — and stops. Never let a failed update fall through to a create.
Where it is running
- Lead Qualification Router — a qualification form → phone-match router → Pipedrive deal → Sheets → "Qualified" / "Not Qualified" tag.
- Ebook Opt-in Funnel — ClickFunnels opt-in → Pipedrive search by email with a phone fallback → new vs. returning branches → tag.
- Booking Cancellation Recovery — the same lookup used in reverse: a cancelled Cal.com call finds the deal, moves it back a stage and tags the contact so the follow-up happens.
Edge cases that bite
- One person, two emails. Decide the rule up front: phone wins, or the most recent email wins. Write it into the scenario and into the documentation.
- Typos. You cannot fix them automatically; you can catch them — a weekly "possible duplicates" sheet (same phone, different email) that a human reviews in five minutes.
- Deals vs. people. A returning person may legitimately need a new deal (a second purchase). The router checks for an open deal; closed deals do not block a new one.
- Rate limits. Pipedrive and ActiveCampaign both throttle bursts. A batch import should go through a queue, not through the live webhook flow.
What it costs and how long it takes
One entry point with the full pattern — normalise, two lookups, router, tag, log, error branch — is a 2–3 day build at the starting price for CRM integration. Each additional source reuses the same router and adds about a day. Everything lives in your Make.com or n8n account; the field-mapping document and the dedup rules are part of the handoff.
Related work
CLIENT PROJECT
Ebook Opt-in Funnel
ClickFunnels opt-in → Pipedrive lookup by email (phone fallback) → new vs. returning routing → person + deal → Sheets → ActiveCampaign tag.
Read the case →
CLIENT PROJECT
Booking Cancellation Recovery
Cancelled Cal.com call → Pipedrive lookup → cancellation logged → "Call Discovery Cancel" tag → deal moved back a stage so the lead gets a real follow-up.
Read the case →Describe your process
Which tools are involved, what is done by hand today, how often. I reply within 24 hours with a fit/no-fit answer and, if it fits, a fixed quote.