CRM Lead CSV Validation & Duplicate Reconciliation n8n Workflow

Validate lead CSVs, normalize contact fields, and reconcile duplicates—automatically

The CRM Lead CSV Validation & Duplicate Reconciliation n8n workflow lets you upload a lead CSV via an n8n form, then processes each row to validate required fields, normalize name/email/phone, and merge duplicates into a single, audit-ready result.

What this workflow does

• Receives a CSV upload through an n8n form trigger.
• Parses CSV rows into structured lead records.
• Applies your configured policy for required fields and identity/duplicate keys, including normalization of email casing and phone formatting.
• Validates each lead for missing required contact details and basic email format, separating results into accepted leads vs. rejected rows with reason codes.
• Reconciles duplicates by grouping leads using your configured email or phone keys, filling missing values from duplicates.
• Detects field-level conflicts when two duplicates contain different non-empty values, recording disagreement details for review.
• Returns an audit package indicating whether the output is ready for import (no rejects or conflicts) or requires review, including counts, accepted leads, rejected leads, and conflict details.

Use cases

• Prepping inbound lead lists before importing into your CRM to prevent bad contacts and accidental duplicates.
• Cleaning submissions from marketing campaigns where email/phone formatting and casing are inconsistent.
• Reconciling duplicate identities (same email or phone) while preserving accurate field values and flagging mismatches.

Technical details

• Nodes used: if, set, code, merge, sticky note, form trigger.
• Setup: update field names and rules in the lead-quality configuration (required fields, email field, phone field, duplicate keys) to match your CSV headers.
• Output: accepted lead list for downstream CRM import when status is ready; otherwise resolve rejections/conflicts from the audit payload.