n8n Lead Enquiry Validation & Routing with Code & If Nodes

Validate and route n8n lead enquiries automatically—using Code + If nodes

This n8n workflow generates two safe sample lead enquiries, normalizes and validates key fields (like email), creates a fingerprint for each record, and then routes them into the right operational state—either needs_clarification or ready_for_human_approved_pilot.

What this workflow does

• Runs manually when you start it in n8n (Manual Trigger).
• Creates two fictional lead enquiries for testing: one complete and one missing required details.
• Normalizes key fields (for example, trimming text and lowercasing the email) so validation is consistent.
• Validates required information, including checks for missing/invalid email, task, or owner.
• Generates a fingerprint for each enquiry to support reliable identification during routing.
• Routes incomplete leads to needs_clarification and adds guidance on what to request next.
• Routes complete leads to ready_for_human_approved_pilot and includes a reminder to keep human approval before any customer-facing follow-up.

Use cases

• Test your lead intake logic before connecting real forms or CRM data.
• Prototype an enquiry triage process that sends missing details into a clarification queue.
• Prepare a “human-in-the-loop” pilot flow for SaaS ops, ensuring no customer-facing messaging happens without approval.

Technical details

• No credentials required—the workflow uses only built-in n8n nodes and safe sample data.
• Nodes used: if, set, code, sticky note, manual trigger.
• Expected behavior: sample-complete-001 routes to ready_for_human_approved_pilot; sample-needs-details-002 routes to needs_clarification.

Setup & next step

Run as-is to confirm the routing. If you adapt to real data, replace the sample enquiry generator and map your incoming fields to name, email, task, and owner before enabling any downstream customer-facing actions.