Case study · GHL + n8n
From site visit to supplier quote
An n8n workflow connected to GoHighLevel that matches active suppliers by trade and city, sends each one a quote request, and records the result and next follow-up in the CRM.
Last updated:
Training project. Built as a LOOP Institute of Applied AI assignment for Elite Home Renovations, a practice account, using test data. It is not a paid client deployment, and no savings have been independently audited.
The problem
In renovation and home-service work, jobs get lost between inquiries, appointments, suppliers and follow-up. After a site visit, someone has to choose the right suppliers and send each one the project details. Suppliers get missed, and the customer's quote waits.
What I built
- Site visit doneA job reaches the site-visit stage in GoHighLevel.
- Check the projectn8n reads the project details and checks the request has not already been sent.
- Match suppliersActive suppliers are matched by trade and city.
- Send requestsEach matching supplier gets an individual quote request.
- Record the resultA CRM note and a dated follow-up task are added in GoHighLevel.
How it handles problems
- Duplicate-safe request cycles, so the same job is not sent twice.
- Partial matches and send failures are visible instead of hidden.
- CRM notes and dated follow-up tasks keep the team informed.
What was tested
These results come from the published LOOP project page and describe one sample run.
| Check | Result | Evidence level |
|---|---|---|
| Matching suppliers found | 4 | Tested |
| Emails accepted by Gmail | 4 | Tested |
| Send failures in that run | 0 | Tested |
| CRM follow-up recorded | Yes | Tested |
| Delivery to supplier inboxes | Not confirmed | Not tested |
Estimates
Estimate, not a measured result: about 17 hours of manual work saved per month, assuming eight site visits each week.
A real business would need its own baseline first: how long supplier requests take today, and how many site visits it handles.
Before using this for a live business
- Measure the current process before estimating any time saved.
- Agree which accounts, data and workflows the business owns.
- Confirm third-party costs, such as GoHighLevel and n8n plans.
- Test normal, duplicate, missing-data and failure cases with the team's real rules.
See the published project
The full write-up is on the LOOP Institute of Applied AI student projects page.