AskLibra Lead Capture & CRM Automation
A lead operations workflow connecting AskLibra's website, n8n, Google Sheets, HubSpot, and Resend to qualify inquiries, preserve lead context, automate timely communication, and prepare each lead for human follow-up.
Role
Automation Designer, Workflow Architect, AI-Assisted Developer
Category
Business Automation
Status
Completed
Year
2026
Private automation environment
The live workflow contains private lead and CRM data. This case study focuses on the automation architecture, decision logic, safeguards, and human handoff without exposing personal lead records.
Overview
This automation connects AskLibra's website lead forms to an operational workflow that validates inquiries, evaluates lead quality, records structured data, sends immediate confirmation, and prepares the lead for review inside HubSpot.
Follow-up communication is gated by the lead's current status so the system does not continue sending messages after a human has already taken action.
Business problem
Lead handling needed to preserve context, reduce manual transfer, and keep follow-up communication aligned with human review.
- New inquiries could require manual copying between tools
- Lead context could become fragmented across email, sheets, and CRM records
- Response timing depended on manual action
- Lead quality was not consistently evaluated
- Follow-ups could be forgotten
- Automated messages could continue after a lead had already been handled
- Human reviewers needed one structured view of the lead's needs and goals
Automation objective
Build one reliable workflow that captures every inquiry, standardizes its data, evaluates lead quality, records the result across operational systems, sends immediate communication, and keeps a human in control of the final sales action.
- Reduce manual data entry
- Preserve lead context
- Standardize qualification
- Improve response consistency
- Prevent missed follow-ups
- Prevent irrelevant follow-ups
- Give reviewers a structured CRM record
Lead lifecycle
The workflow moves from website intake to qualification, tracking, CRM context, communication, status-aware follow-up, and human review.
- 1
Capture inquiry
Receive the lead from AskLibra's website through a protected API and n8n webhook flow.
- 2
Validate and normalize
Check required fields and normalize submitted values before downstream tools receive them.
- 3
Qualify lead
Evaluate business context, goal, problem, service interest, and timeline.
- 4
Score and classify
Produce a lead score and Hot, Warm, or Cold temperature.
- 5
Log in Google Sheets
Store lead details, score, status, and follow-up tracking fields.
- 6
Create or update HubSpot contact
Find an existing contact by email or create a new record.
- 7
Add HubSpot review context
Attach a structured internal note with lead details, qualification, and review context.
- 8
Send confirmation email
Use Resend to acknowledge the inquiry and confirm that the lead entered the process.
- 9
Wait follow-up interval
Pause for the configured period before follow-up review.
- 10
Check current status
Read the latest status and follow-up fields before sending anything else.
- 11
Send eligible follow-up
Continue only when the current state allows another message.
- 12
Update tracking
Record follow-up sent state and current workflow status.
- 13
Human review
Present the lead and context in HubSpot for the next human sales action.
Automation workflow
The automation reduces manual transfer while keeping final qualification and sales decisions under human control.
Previous manual process
Website inquiry received -> manually review the form -> copy lead details into a tracking sheet -> decide whether the lead is worth pursuing -> create or update the CRM record -> send an acknowledgment -> remember to follow up later.
Connected systems
Trigger
- AskLibra website form submission
Captured inputs
- Name
- Business type
- Goal
- Problem
- Service interest
- Message
- Source
- Timeline
Decision logic
- Evaluate business type, stated goal, stated problem, service interest, requested timeline, and message completeness.
- Classify each lead as Hot, Warm, or Cold.
- Before a scheduled follow-up, check current status and prior follow-up fields.
- Handled, converted, closed, or ineligible leads should not continue through automated follow-up.
Outputs
- Google Sheets operational capture log
- Lead score and temperature tracking
- Current lead status
- Follow-up-one and follow-up-two status
- HubSpot contact and structured review note
- Immediate Resend confirmation email
Human review points
- Review the lead in HubSpot
- Evaluate nuance that scoring cannot fully capture
- Change lead status
- Decide whether to contact the lead
- Handle calls and replies
- Stop or advance follow-up
- Record notes and next actions
Safeguards
- Required-field validation
- Normalized values
- Numeric lead-score conversion
- Contact lookup before creation
- Status checks before delayed follow-up
- Sent flags to avoid duplicate messages
- Structured API payloads
- Production webhook requires an active n8n workflow
- Separate test and production webhook behavior
- Response handling for failed downstream nodes
Automation layers
The workflow is grouped by operational layer so the business process stays readable without exposing private lead records.
Lead intake
Captures and normalizes the website inquiry before qualification begins.
- Website form
- Next.js API route
- n8n webhook
- Validation
Qualification
Evaluates submitted context and creates a consistent score and lead temperature.
- Business context
- Goal and problem review
- Timeline check
- Hot, Warm, or Cold classification
Operational tracking
Keeps a lightweight working record outside the CRM for workflow visibility.
- Google Sheets log
- Lead score
- Current status
- Follow-up tracking fields
CRM handoff
Prepares the lead for human review inside HubSpot without claiming automatic sales action.
- Contact lookup
- Contact creation or update
- Structured internal note
- Follow-up task support as next handoff step
Communication
Sends confirmation and follow-up only when the current lead state allows it.
- Resend confirmation
- Delay nodes
- Status checks
- Duplicate follow-up prevention
Human control
Keeps review, outreach decisions, and lifecycle changes under human direction.
- HubSpot review
- Status updates
- Sales judgment
- Manual next action
Gallery
Product media can be added here without changing the page renderer.
Workflow overview
The automation flow connecting website inquiry, qualification, CRM, and follow-up.
HubSpot CRM handoff
Qualified website leads are added to HubSpot so their contact details, business context, qualification notes, and follow-up status can be reviewed in one CRM workspace.
My role
I designed the lead lifecycle, data flow, qualification structure, integration sequence, follow-up safeguards, and human handoff. I used AI-assisted development to accelerate workflow construction, payload debugging, expression fixes, HubSpot request formatting, and documentation while manually validating the workflow behavior and integration results.
AI-assisted, human-directed development
AI accelerated workflow construction, payload debugging, expression fixes, HubSpot request formatting, documentation, and iteration planning. Business rules, tool selection, safeguards, testing, and final approval remained human-directed.
AI accelerated
- n8n expression construction
- Payload formatting
- Conditional logic scaffolding
- HubSpot JSON debugging
- Webhook troubleshooting
- Data-mapping review
- Documentation
- Iteration planning
Human direction and ownership
- Business objective
- Lead lifecycle design
- Qualification rules
- Tool selection
- Data-field decisions
- CRM handoff design
- Follow-up safeguards
- Manual testing
- Interpretation of errors
- Final workflow approval
Architecture and stack
Technology stack
Technical challenges
Structured n8n expressions
Building dynamic payloads required careful expression handling so submitted fields mapped cleanly across workflow nodes.
HubSpot JSON formatting
Invalid payload errors were resolved by tightening request shape, property names, and value formatting.
CRM contact handoff
Submitted lead data had to map into a useful HubSpot review context without creating unnecessary duplicate records.
Status-aware follow-up
Delayed automation needed to check the latest lead state before sending another message.
Numeric lead-score evaluation
Scoring values needed to be treated numerically so conditional branches behaved predictably.
Test and production webhook behavior
The workflow accounts for n8n's different test and production webhook execution requirements.
Human-in-the-loop design
The system automates preparation and communication without removing human judgment from sales decisions.
Results
Qualitative workflow outcomes
One connected intake workflow
Lead capture, qualification, tracking, CRM context, confirmation messaging, and conditional follow-up are connected in one process.
Structured lead scoring and temperature
Submitted context is evaluated into a consistent score and Hot, Warm, or Cold classification.
Google Sheets operational tracking
Sheets remains the lightweight operational layer for capture logs, status, and follow-up visibility.
HubSpot contact and review context
HubSpot receives contact context and a structured note for human review.
Immediate confirmation email
Resend confirms that the inquiry entered the process without waiting for manual action.
Conditional follow-up sequence
Delayed messages check current status and sent flags before continuing.
Human-controlled CRM handoff
The workflow prepares leads for review while leaving final outreach decisions to a human.
Project takeaways
The main takeaways from turning a website inquiry into a practical, human-reviewed lead operations workflow.
Automation should preserve context
Moving data between tools is not enough. The useful part is preserving the lead's goal, problem, service interest, score, and review context so the next person has enough information to act.
Delayed workflows require fresh state
A follow-up decision should use current lead status, not the status that existed when the lead first entered the workflow.
Human handoff is part of the system
The workflow prepares, prioritizes, and documents the lead, but the final sales judgment remains with a person.
Refinement backlog
Confirm and document HubSpot task creation, add centralized error alerts, formalize follow-up timing, gather verified performance metrics, and expand CRM lifecycle reporting.
What this project demonstrates
This project demonstrates how a website form can become a practical lead-operations system by connecting qualification, CRM context, communication, state tracking, and human review.
- Multi-tool automation architecture
- Lead qualification and branching
- CRM and operational-data synchronization
- Status-aware communication
- Human-in-the-loop workflow design
- AI-assisted automation development
More work is being documented.