When I started with Lucky Credit, a lending company, I took over automations built before my time, with no documentation and no list of what ran. I'm Eric Forte, a GoHighLevel and n8n AI Automation Engineer based in the Philippines. This is the GoHighLevel workflow audit I ran on that setup, the part I found hardest, and what I built for them after.
Key Takeaways
- I took over Lucky Credit's GoHighLevel, n8n and Zapier automations with no documentation and no list of what ran.
- Before fixing anything, I audited every automation: what runs, what's needed, and what each one does. Then I fixed or rebuilt it.
- The hardest part was figuring out which automation did what, especially workflows running under logins the business didn't own.
- The builds for Lucky Credit included a dialer sync, a rebuilt booking flow, faster client onboarding, bad-fit cleanup, re-qualifying no-shows and recovering missed form leads.
What does an inherited automation setup look like?
At Lucky Credit there were automations in three places: GoHighLevel, Zapier and n8n. There was no document saying what each one did and no list of what ran. Some had stopped running and some were broken, and I had to find out which before touching anything. So the first job wasn't building anything. It was finding out what was there.
How do you run a GoHighLevel workflow audit on an inherited setup?
Audit first, change things second. Here's the order I worked in at Lucky Credit:
- List every automation in every tool: GoHighLevel workflows, Zaps and n8n workflows.
- Find out which ones actually run.
- Work out what each one does and whether the business still needs it.
- Fix the broken ones that are needed.
- Rebuild the ones that are needed but too tangled to fix.
GoHighLevel helps with step 2. Its Execution Logs and Enrollment History show how contacts moved through a workflow and every action they hit, so you can see what a workflow really does instead of guessing from its name.
What do you do with automations tied to someone else's account?
This was the hardest part for me. Lucky Credit's n8n account had a lot of broken workflows, and many of them ran under logins the business didn't own. That made both the audit and the rebuild harder.
If you're in the same spot, it's worth moving workflows and their logins over to an account the business owns before changing anything else. Then, the next time someone leaves, the automations stay.
What did I rebuild for Lucky Credit?
Here's what I built for them. Each one has its own case study:
- Re-qualifying no-shows: stale no-shows got flagged in GoHighLevel and the dialer, and cleared out of outreach. Re-Qualify Lifecycle Automation
- Recovering missed form leads: a catch-up path found leads whose form event didn't fire. Typeform Lead Pipeline with Catch-Up Recovery
- Client onboarding: setup went from 30 to 60 minutes per client to about 2. Drive and Airtable Client Onboarding Pipeline
- Dialer sync: each lead update went from 10 to 15 minutes to one dropdown change. GoHighLevel and Dialer Real-Time Sync
- Booking flow rebuild: two days from audit to a tested n8n workflow. Calendly Booking to GoHighLevel Native Pipeline
- Bad-fit cleanup: one tag now clears bad fits out of outreach. Bad-Fit Lead Cleanup System
What did Lucky Credit say?
Great response time, very knowledgeable with various complex automations with n8n, GoHighLevel, Zapier. Saved me a ton of time and stress! (Leo Berlingieri, Lucky Credit)
What can a small business take from this?
You don't need a crisis to do this. A few habits keep an automation setup from turning into a mystery:
- Keep a simple list of your automations and what each one does.
- Run them under accounts the business owns, not one person's login.
- Before adding something new, check what's already running.
That last habit is the heart of Elon Musk's 5-step algorithm: question it and delete what isn't needed before you automate anything.
Frequently asked questions
How do you run a GoHighLevel workflow audit?
List every workflow, then check which ones actually run using GoHighLevel's Execution Logs and Enrollment History. For each one, write down what it does and whether the business still needs it. Only then fix or rebuild. Doing it in that order keeps you from rebuilding something that should simply be deleted.
What happens to your automations when your developer leaves?
In my experience, the knowledge leaves with them. If some automations ran under their own logins, those can stop or become hard to change. Moving them to accounts the business owns, and keeping a short list of what each one does, saves a lot of trouble later.
Should you fix broken automations or rebuild them?
Fix it if it's needed and the fix is small. Rebuild it if it's needed but nobody can follow how it works. At Lucky Credit I did both, and the audit is what told me which was which.
Is GoHighLevel good for lending companies?
It can be. At Lucky Credit, GoHighLevel was the CRM at the center, with Zapier and n8n connecting it to their dialer, their forms and their booking tool. Whether it fits your team depends more on your process than on the tool.
Should you use Zapier or n8n with GoHighLevel?
Both work. At Lucky Credit I kept Zapier where the client preferred it and it did the job, like the dialer sync, and moved from Zapier to n8n for the booking flow when they asked for it. Pick per job, not per brand.
Want a second pair of eyes on your setup?
If you've inherited automations nobody can explain, you can book a call and tell me what you're running. I'm happy to take a look with you.
Sources
- HighLevel, Workflows: Improved Execution Logs and Enrollment History, retrieved 2026-11-17: help.gohighlevel.com/support/solutions/articles/155000003992.
- Testimonial from Leo Berlingieri, Lucky Credit, shown on the ericforte.com homepage: ericforte.com.



