Claude > GHL WORKFLOW AUTOMATIONS (WRITE)
A
Antonino Piraino
Trying to connect Claude with GoHighLevel sub account so that I can speak automations into existence, but it appears we only have the ability to toggle on "readonly" instead of "write".
This would be a game changing feature and save people hundreds of hours during account setup and ongoing maintenance of sub accounts!
I'm getting tired of manually creating workflow automations over here! (the built in ai inside workflow automations told me he cannot do that yet)
Log In
D
Drew Mcleod
We NEED this feature! It would also be good for GHL because this will lower the barrier to entry for building workflows as well.
B
Benjamin Paquette
use the claude chrome extension and this has been working flawlessly for me in building and deploying very detailed workflows with 5+ branches.
H
Hannah Lomax
Benjamin Paquette seconding this as an interim workaround, especially when integrated with Playwright. Depending on usage limits, though, it can become an issue when deploying multiple sub-agents for several automation builds simultaneously.
If widening the GHL MCP server scopes to allow Claude code to 'write' automations via the server is too complex or disrupting for GHL for whatever reason, we should at least have the ability to export/import automations' JSON/blueprint. This would allow Claude to write several automations at once as JSON files to be imported, using the MCP server to 'read' enough such that it maintains accuracy in node construction, while also saving quite a bit on usage. It'd also just be best practice to allow us to export/import blueprints for back-up and transfer related reasons.
S
Saqib Ali
Honestly this would be a massive game changer for GHL users. Imagine being able to tell Claude: “Build me a lead nurture workflow with SMS, email follow-up, missed call text back, and pipeline updates” — and it creates everything automatically inside the sub account instead of us spending hours building it manually
The built-in AI is helpful, but full write-access automation with Claude/OpenAI would save agencies an insane amount of setup and maintenance time.
C
CLINT WHITNEY
High Level - this is a MUST anymore. Add scopes, allow MCP to read/write automation emails, sms, and build workflows without the 3 layered iFrame chaos for Agents. Thanks
P
Pierce Venzara
Yes why are automations not available to write as functions in code? This is such a crazy way to do automations. Everything should boil down to simple code that an AI can easily interact with. That is already what it is on the backend anyways. Why hide it?
M
Matthew Lee
GHL MCP
R
Raissa Latorre
Matthew Lee cloude with mcp can activate or pause automations but cannot create them. GHL workflows have no endpoints in the API — neither in the MCP connector nor in the GHL public API
D
Duje Žižak
Yes, I agree as well. It would allow us to do crazy automation things with it
R
Rowan Blinde-Leerentveld
Yes, would be cool. For the time being: I gave my ChatGPT access to the account as a user, and she is able to actually build stuff out for me.