Quote intake and lead scoring
An 8-node n8n workflow, Elite Lead Scoring, that checks GoHighLevel every 10 minutes, scores new contacts on four details and sends each lead to the right next step.
- Sandbox build
n8n + GoHighLevel. Last updated .
- Build spec8nodes in the n8n scoring workflow
- Build spec10 minbetween scoring runs
- Build spec3routing paths: hot, warm, nurture
- Build spec1 hrdue time for the hot-lead call task
The problem
Renovation companies get estimate requests of very different value. Without scoring, a large kitchen remodel booked for next month waits in the same queue as a small repair someday, and the best leads go cold.
What I built
The Elite Lead Scoring workflow in n8n runs in eight nodes:
- n8nSchedule triggerRuns every 10 minutes.
- n8n + GoHighLevel APIGet contactsFetches contacts from GoHighLevel through the API.
- n8nFilterKeeps only contacts tagged
needs-scoring. - n8nScore four detailsProject Type, Budget Range, Timeline and City.
- GoHighLevelRoute the leadSends each contact down one of three paths based on its score.
How leads are routed
| Tag | What happens next |
|---|---|
hot-lead | A call task is created, due within 1 hour. |
warm-lead | The contact joins the nurture sequence. |
nurture-lead | The contact is added to the newsletter list. |
Why it is built this way
- A tag (
needs-scoring) marks which contacts still need work, so each one is scored once. - Scoring rules sit in one place in n8n, so the business can change what counts as a hot lead.
- The fast path for hot leads is a dated task for a person, not just another automated message.
Before using this for a live business
- Measure the current process first, so any improvement can be compared with a real baseline.
- Agree which accounts, data and workflows the business owns. I work through a role-based team invite.
- Confirm third-party costs, such as GoHighLevel, n8n and messaging plans.
- Test normal, duplicate, missing-data and failure cases with the team's real rules.