Jubril Toheeb
AI Automation, GoHighLevel & AI Web Dev | Bubble, n8n
Your GoHighLevel automations are running right now.
Do you actually know what's in them?
Agencies build workflows fast. A client asks for a follow-up sequence, you duplicate an old one, tweak it, ship it. Six months later there are 125 workflows in the sub-account, half of them drafts nobody remembers, and two with the exact same name, so nobody's sure which one is live.
That's how leads get the same message twice. Or none at all.
So I built Automation Guardian.
It connects to a HighLevel sub-account, reads every workflow, and gives you:
ā A health score for the whole account
ā Findings ranked by severity, most urgent first
ā A plain-English explanation of each issue, written by AI, plus the business impact and how to fix it
ā A shareable audit report you can hand to a client
On a real test account it audited 125 workflows in under a second.
And the part I care about most: it's read-only. It never edits, publishes or deletes anything in your HighLevel account. Tokens are encrypted. You stay in control and make every change yourself.
I'm also honest about what it can't see. When HighLevel doesn't share the data a check needs, the report says "Not checked" instead of pretending it passed.
It's launching on the HighLevel Marketplace soon, with a free plan.
If you run a GHL agency and want early access, comment "AUDIT" or send me a DM. š
#GoHighLevel #HighLevel #MarketingAutomation #AgencyOwners #SaaS #BuildInPublic #AI
2
2
48
Project update: a safer way to move cards to "Paid" in a CRM
For a financial advisory firm, I built a feature in GoHighLevel that makes paying referral partners faster and harder to get wrong.
What it does: when a card is dragged to Paid, the system finds every other card due for the same partner and shows a checklist. The assistant ticks the cards to pay together and confirms once. With a single card, it asks a simple confirmation instead.
How I made it reliable: a small backend on Vercel re-checks every card before moving it (same partner, still due, only into Paid). A failed card is named in a message while the others still move. If the list can't be loaded, the plain question is asked, so nothing moves silently.
What I did: designed the flow, wrote the browser script and the backend, and tested the cases that go wrong, not only the happy path.
Tools: GoHighLevel, JavaScript, Node.js, Vercel, GitHub.:
3
2
75
Your CRM can't do math. This one couldn't either.
An insurance advisory firm pays its referral partners under four different commission rules. It was all tracked in an Excel sheet, and every partner needed an email with their total and the clients they referred.
GoHighLevel can't add up amounts across several opportunities on its own. The obvious fix, a Custom Code step, is a premium feature they don't have, and the script they had in mind used GHL's old v1 API, which is past end of support.
So I built it outside GHL:
ā A small scheduled job reads the Referral Payments pipeline every morning
ā It adds up each partner's Pending and Due cards, applying the right rule per group (including a tiered formula for one group)
ā It writes the total and client list onto the partner's contact, then reads it back to confirm it saved
ā Workflows send each partner one email using plain merge fields. No premium actions needed.
A few choices that matter:
ā¢ Totals are recalculated from the cards every run, not appended, so a cancelled sale drops out on its own and a paid partner resets to 0
ā¢ Manual runs are dry runs by default, so nothing changes by accident
ā¢ English and French partners each get their own formatting
ā¢ A heartbeat check means a missed run can alert the owner
Tested live on their account: a test card went from Pending to Due to Paid, and the partner's total followed it at every step, back to 0, verified each time. Plus 41 simulated checks on the edge cases.
While I was in there, an audit of their workflows found five bugs, like cards bouncing back to Pending 10 days after moving to Due, and a client's second sale being silently dropped. The fixes are built as drafts for the client to review, with nothing live touched.
If your CRM still needs a spreadsheet sitting next to it, that's usually fixable. Free 30-minute automation audit: cal.com/jubril-toheeb-rgh9vp/30min
0
25
Warehouse Booking-to-Payment Automation (n8n + Stripe)
0
8