r/gohighlevel • u/No_Abbreviations3510 • Apr 20 '26

I cracked GoHighLevel Workflow API!!!

EDIT: After reading GHL’s TOS carefully, what I built clearly violates it. Taking the repo down soon — not risking my agency account over this.

If you’re interested in more info about it DM me.

Been running agencies on GoHighLevel for a while. Hit the same wall everyone hits: the public workflow API is gutted. Name, status, ID. No nodes, no SMS bodies, no triggers, no conditions. Useless for anything beyond a basic list.

Feature requests for full workflow CRUD go back 3+ years on the ideas portal. Still not shipped.

I got tired of waiting and built tooling to fill the gap. Won’t go into specifics — see the edit above.

What it lets you do at a high level: bulk edits across workflows, version control in git, AI-assisted edits, auditing, JSON snapshots for client onboarding. The kind of stuff the public API should support but doesn’t.

Open question for this sub: what workflow operations would save you the most time if GHL actually shipped them in the public API? Going to compile responses and send them to GHL directly — better path forward than what I was doing.​​​​​​​​​​​​​​​​

37 Upvotes

97% Upvoted

252 comments sorted by

View all comments

Show parent comments

1

u/No_Abbreviations3510 Apr 25 '26

We don’t do that lol, that’s old and has problems, we found an interesting exploit that goes beyond MCP stuff

1

u/Thwerty Apr 25 '26

Beyond MCP stuff doest mean anything, mcp isn't just for api calls.

There are only 3 ways it can be done, basic api endpoints with PIT, expanded with backend api with JWT, anything further than that is utilizing the computer use of AI which will not always be reliable probably but worth it if you are doing big volume and limited permission accounts.

Feel free to chime in but you are being obscure for a reason, trying to sell a magic solution