Lead Qualification Engine — Tested n8n Intake Workflow by Stav MLead Qualification Engine — Tested n8n Intake Workflow by Stav M

Lead Qualification Engine — Tested n8n Intake Workflow

Stav M

Stav M

Lead Qualification Engine v1.0.1
A tested n8n lead intake workflow that turns a website enquiry into a validated, stored, and notified lead with predictable responses.
What it solves
Small service teams often receive inconsistent form submissions, create duplicate records, and lose clarity when storage or notification steps fail. This portfolio implementation demonstrates a bounded workflow that makes each stage explicit and testable.
How it works
Successful n8n execution using synthetic test data.
Successful n8n execution using synthetic test data.
Receives one form or webhook submission.
Normalizes and validates the agreed fields before external actions.
Checks normalized email for case insensitive duplicates.
Stores a new lead in Google Sheets.
Sends one Gmail notification only after successful storage.
Returns a structured success or failure response.
Verified evidence
Released as version 1.0.1 on 4 August 2026. Final independent QA was approved. One successful live execution used synthetic data and showed the full path from webhook intake through validation, duplicate lookup, Google Sheets storage, Gmail notification, and the final structured response.
Stored lead row in Google Sheets using synthetic test data.
Stored lead row in Google Sheets using synthetic test data.
Reviewed paths
Gmail notification generated after successful storage using synthetic test data.
Gmail notification generated after successful storage using synthetic test data.
Valid submission; invalid submission; case insensitive duplicate; Google Sheets lookup failure; Google Sheets storage failure; Gmail failure after storage; and notifications disabled.
Canonical structured success response from the tested workflow.
Canonical structured success response from the tested workflow.
Honest limitations
This is an independent portfolio implementation, not a production client deployment. Evidence uses synthetic data. Duplicate control is not concurrency safe exactly once storage. There are no automatic retries, delivery queues, or manual resend features. Gmail API acceptance does not guarantee inbox placement. No client outcomes, ROI, production volume, AI scoring, or CRM synchronization are claimed.
Like this project

Posted Aug 6, 2026

Tested n8n lead intake with validation, duplicate control, Google Sheets storage, Gmail notification, structured responses, and documented limits.

Likes

0

Views

0

Timeline

Jul 24, 2026 - Aug 4, 2026