n8n Lead Intake Validation with Code & Switch Decision Workflow

Validate and triage incoming leads in n8n—before they hit your CRM

This n8n workflow demonstrates how to diagnose malformed or incomplete lead payloads using a Code + Switch decision workflow. It runs nine fictional edge-case examples and produces explainable review decisions so you can see exactly why each lead is accepted, held, or flagged.

What this workflow does

• Manual execution: The workflow runs when you manually execute it (Manual Trigger).
• Generates 9 synthetic lead examples: It creates fictional leads covering common issues such as missing contact details, invalid email, duplicate IDs, malformed fields, and bad UTM values.
• Preflight validation in JavaScript: A Code step normalizes text fields and validates key fields like event IDs, emails, and phone numbers.
• Duplicate detection per run: It detects duplicate event IDs or email addresses within the current run.
• Assigns status + reason codes: Each lead is labeled with a triage status, reason codes, and normalized output fields for clear review.
• Routes via Switch: Items are routed into review/hold paths using a Switch node, including a fallback route for unexpected statuses.
• Inspectable branch outcomes: Each routed item is labeled with a route decision so you can inspect the final outcome per lead in the corresponding branch.

Use cases

• Sales Ops builders validating lead ingestion rules before CRM handoff
• n8n learners learning Code + Switch patterns for data triage
• SaaS operators testing preflight handling for incomplete form submissions and tracking data issues

Technical details

• Nodes used: Manual Trigger, Set, Code, Switch, Sticky Note
• Workflow behavior: Generates nine fictional test rows, evaluates them in Evaluate Lead Preflight, then routes them through Decision paths
• Setup approach: Import the workflow JSON into an isolated n8n instance, keep it inactive, then run the Manual Trigger to inspect the nine-row outcomes