Skip to content

AI Automation

Lead Qualification Pipeline

Lead Qualification Pipeline is an independent workflow automation project designed to streamline how businesses receive, acknowledge, and organize inbound leads. Built with n8n, Google Forms, Gmail, and Google Sheets, the workflow processes incoming form submissions and sends an immediate acknowledgment email to the person who submitted the form. It then evaluates the submitted email address, distinguishing business email domains from personal and disposable domains. Contacts that meet the business-email criteria are recorded in Google Sheets with their name, email address, role, and submission timestamp. The workflow demonstrates how an inbound lead process can connect form collection, automated communication, rule-based qualification, and structured recordkeeping without requiring a custom CRM application. This is a self-initiated automation case study, not a verified paid client deployment. No lead-conversion improvements or measured time savings are claimed.

Project details

Project type
Lead Qualification & Follow-Up Automation
Role
Automation Engineer
Engagement
Independent · Self-Initiated Case Study
Status
Independent workflow demonstration
Technologies
  • n8n
  • Google Forms
  • Gmail
  • Google Sheets

Context

Project context.

Inbound forms provide businesses with a straightforward way to collect inquiries from prospective customers. However, receiving a submission is only the beginning of the lead-management process. Businesses often need to acknowledge the inquiry, determine whether the contact fits their target audience, and organize relevant information for follow-up. When these activities are handled manually, someone must review each submission, send a response, check the contact's details, and transfer qualifying information into a tracking system. Lead Qualification Pipeline explores how these repetitive steps can be connected through a lightweight automation. I built the workflow using n8n to coordinate Google Forms, Gmail, and Google Sheets. When a form submission is processed, the workflow sends an acknowledgment email through Gmail. It also evaluates the submitted email domain to distinguish business contacts from personal or disposable addresses. Eligible business contacts are recorded in Google Sheets with structured information that can be reviewed during subsequent outreach activities. The workflow relies on explicit filtering rules rather than an AI model to determine qualification. It is an independent demonstration of form-driven lead processing, not a commissioned client implementation.

Project setting

The project focuses on a specific form-to-email-to-spreadsheet process rather than a comprehensive CRM or sales engagement platform. Google Forms provides the submission information, Gmail handles acknowledgment messages, and Google Sheets stores contacts that pass the qualification rules. n8n coordinates these systems and evaluates the submitted email domains. Qualification in this workflow is intentionally narrow. A business email address is treated as an eligibility signal, not proof that the contact has purchasing authority, commercial intent, or a strong fit for a particular product. The workflow does not claim to use machine learning, LLM-based scoring, or predictive lead qualification.

Problem space

  • Businesses need a consistent way to process inquiries submitted through online forms.
  • New contacts should receive timely acknowledgment without requiring an individually written email.
  • Not every submission necessarily represents a relevant business lead.
  • Personal and disposable email addresses may be unsuitable for business-focused prospect lists.
  • Manually reviewing email domains introduces repetitive qualification work.
  • Eligible contacts need to be organized in a consistent format for later review.
  • Copying submission information into spreadsheets creates additional administrative steps.
  • Lead-processing workflows should use clear rules so the reason a contact qualifies can be understood.

Target users

  • B2B businesses collecting inquiries through online forms.
  • Sales teams organizing inbound prospects.
  • Business development teams identifying contacts with company email addresses.
  • Small businesses looking to automate initial lead processing without introducing a dedicated CRM.

Contribution

My contribution.

I independently designed and built Lead Qualification Pipeline using n8n, Google Forms, Gmail, and Google Sheets. My work covered form-submission processing, automatic acknowledgment emails, email-domain filtering, conditional lead qualification, and structured contact logging.

The project focuses on automating the first stages of handling an inbound business inquiry. Rather than requiring someone to acknowledge each submission and manually transfer qualifying contacts into a spreadsheet, the workflow coordinates these activities through defined processing steps. I designed the process to separate initial communication from lead qualification. Acknowledging receipt of an inquiry is distinct from determining whether the submitted contact meets the criteria for the business prospect list.

  1. End-to-End Workflow Orchestration

    Built an n8n workflow that connects Google Forms submissions with automated email acknowledgment, contact qualification, and spreadsheet logging. Organized these activities into a repeatable process for handling incoming inquiries.

  2. Google Forms Integration

    Connected Google Forms to the workflow to process submitted contact information. Used the submitted details as the input for acknowledgment messages and subsequent qualification checks.

  3. Automated Email Acknowledgment

    Integrated Gmail to send acknowledgment emails when form submissions are received. This provides an immediate response to incoming inquiries without requiring someone to prepare each message manually.

  4. Business Email Qualification

    Implemented rule-based email-domain checks to distinguish business addresses from personal and disposable email domains. Used these checks to determine whether a contact should be included in the qualified business lead list.

  5. Conditional Lead Processing

    Structured the workflow so contacts that meet the defined business-email criteria proceed to spreadsheet logging. Contacts that do not meet those criteria are excluded from the eligible business-contact records.

  6. Google Sheets Lead Logging

    Integrated Google Sheets to record qualifying contacts in a structured format. The recorded fields include the contact's name, email address, role, and submission timestamp.

  7. Connected Business Workflow

    Combined form intake, automated communication, qualification rules, and contact recording without building a separate application. The workflow demonstrates how existing business services can support a lightweight lead-management process.

Scope of ownership

The project uses deterministic qualification rules rather than AI-generated lead scores. Its primary engineering focus is integrating existing services and processing incoming data consistently. The workflow is a self-initiated demonstration. It has not been presented as a production-deployed client system, and no performance or conversion metrics have been established.

Implementation

Technical breakdown.

Lead Qualification Pipeline uses n8n to coordinate three Google Workspace services. Google Forms supplies incoming submission data. Gmail delivers acknowledgment messages. Google Sheets stores contacts that meet the business-email qualification criteria. The processing logic uses email-domain checks to determine which submissions qualify for recording.

  1. Form Submission Processing

    • n8n
    • Google Forms

    Connected Google Forms to the n8n automation to process information submitted through an inbound contact form.

    The submission data provides the details required for subsequent workflow stages, including the contact's identity and email address.

    n8n coordinates the processing steps so the acknowledgment and qualification activities can be handled through a connected workflow.

    • Google Forms submission processing.
    • Retrieval of submitted contact information.
    • Handling of email addresses and other form details.
    • Coordination of downstream automation stages.
  2. Automatic Gmail Acknowledgment

    • n8n
    • Gmail

    Integrated Gmail to acknowledge incoming form submissions automatically.

    The acknowledgment step sends a response when a new inquiry is processed, removing the need for someone to manually prepare an initial confirmation email.

    This communication step is separate from deciding whether the contact qualifies for the business lead list.

    The acknowledgment confirms receipt of the inquiry; it does not represent sales acceptance or a completed qualification decision.

    • Gmail integration.
    • Automated acknowledgment messages.
    • Immediate response to submitted inquiries.
    • Separation of initial communication from qualification.
  3. Email Domain Filtering

    • n8n

    Implemented qualification rules based on the email domain associated with each submission.

    The workflow distinguishes business email addresses from personal and disposable email domains.

    These checks determine whether a submitted contact meets the criteria for inclusion in the business prospect list.

    The qualification method is intentionally rule-based. It does not attempt to infer a company's size, a contact's purchasing authority, or the likelihood of converting the inquiry into a customer.

    • Email-domain inspection.
    • Personal email domain filtering.
    • Disposable email domain filtering.
    • Identification of eligible business addresses.
    • Deterministic qualification rules.
  4. Conditional Lead Routing

    • n8n

    Used the qualification results to determine which contacts should proceed to Google Sheets.

    Submissions meeting the business-email criteria are treated as eligible business contacts.

    Submissions that do not meet these criteria are excluded from the qualified-contact records.

    This keeps the logging process focused on contacts that satisfy the workflow's defined rules.

    • Conditional workflow execution.
    • Business-email eligibility checks.
    • Routing of qualifying contacts.
    • Exclusion of contacts that fail the domain criteria.
  5. Google Sheets Contact Logging

    • n8n
    • Google Sheets

    Integrated Google Sheets to store the information associated with eligible business contacts.

    The workflow records each qualifying contact's name, email address, role, and submission timestamp.

    Using a consistent set of fields makes the collected information easier to review and use for subsequent business follow-up activities.

    Google Sheets serves as the structured record of qualifying contacts rather than the destination for every unfiltered form submission.

    • Google Sheets integration.
    • Logging of qualifying business contacts.
    • Contact name.
    • Email address.
    • Contact role.
    • Submission timestamp.
  6. End-to-End Business Tool Integration

    • n8n
    • Google Forms
    • Gmail
    • Google Sheets

    Combined Google Forms, Gmail, and Google Sheets into a connected process using n8n.

    Each service has a defined responsibility: collecting incoming information, sending acknowledgments, or maintaining the list of eligible business contacts.

    n8n provides the orchestration and conditional logic connecting these stages.

    The implementation demonstrates an approach to lightweight business process automation without introducing a custom backend or a separate lead-management interface.

    • Integration of three Google Workspace services.
    • n8n workflow orchestration.
    • Form-driven processing.
    • Automated communication.
    • Rule-based qualification.
    • Structured contact logging.

Outcomes

What the work delivered.

Lead Qualification Pipeline demonstrates a connected inbound lead process that handles form submissions, acknowledgment messages, email-domain qualification, and contact logging. The project delivers a rule-based automation across Google Forms, Gmail, and Google Sheets. Its outcomes are technical deliverables rather than verified business improvements, since the workflow was developed independently and no paid client deployment or measured conversion results have been established.

  1. Deliverable

    Automated Lead Intake

    Built an n8n workflow that processes inbound Google Forms submissions and coordinates the subsequent acknowledgment and qualification steps.

    The workflow connects form data collection with downstream business processes without requiring manual transfer between services for the demonstrated flow.

  2. Deliverable

    Immediate Inquiry Acknowledgment

    Integrated Gmail to send automatic acknowledgment emails when inquiries are processed.

    The acknowledgment step provides a consistent initial response independently of whether a contact qualifies for the business lead list.

  3. Deliverable

    Rule-Based Lead Qualification

    Implemented email-domain filtering to distinguish eligible business contacts from submissions using personal or disposable email domains.

    The qualification logic uses explicit domain rules. It does not constitute predictive lead scoring or comprehensive commercial lead qualification.

  4. Deliverable

    Structured Business Contact Records

    Connected Google Sheets to record qualifying contacts with their name, email address, role, and submission timestamp.

    The spreadsheet provides a consistent record format for reviewing eligible business contacts.

  5. Deliverable

    Three-Service Business Integration

    Integrated Google Forms, Gmail, and Google Sheets into a single n8n workflow supporting lead intake, acknowledgment, qualification, and logging.

    Measured impact

    Connected services
    3

    Google Forms, Gmail, and Google Sheets, orchestrated through n8n.

    Each service supports a specific stage of the process, allowing the workflow to operate without a separately developed lead-management application.

  6. Deliverable

    Independent Automation Case Study

    Developed an independent automation demonstrating form processing, automated communication, conditional logic, and structured contact logging.

    The project is not presented as a paid client implementation. No claims are made about production adoption, lead conversion, revenue generation, or measured operational savings.