Your CRM can't do math.

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