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.

Benjamin Paquette I tried letting Claude run in th browser like that, but it took forever for it to do anything in the system around workflows. Have you found a way to get Claude moving faster through that process? I'm honestly just wanting Claude to quickly view all my workflows nodes from start to finish to see if there are any gaps/issues, and log everything that is in the workflows so we can cleanup/consolidate some things.

Tyler Pozun hey Tyler, can you elaborate what slow is for you? I do have Claude write a review only chrome extension prompt from desktop then paste it into chrome extension and it goes to work with safe guards so it doesn’t publish anything and report back to me areas I’ve missed, areas to improve based off other builds I’ve done and then paste that response back into desktop project for it to digest and create a new prompt for chrome to act on and build.

I wouldn’t say it’s fast by any means, but it’s still a huge time save for me and 100% of the time while it’s building out the workflow msg / email branches copy etc i move to another task and come back to it being finished.

One thing you do have to be aware of is this will eat your limits quickly and depending how in depth your workflow is you’ll have to compact the conversation to continue.

I’ve also found having multiple chrome extension tab groups running at once for a workflow speeds it up but also eats ur limits faster too but overall quality of Claude chrome extension building has been superior and allows me to take that time into other tasks.

Let me know if you have any other questions.

Benjamin Paquette That sounds incredible! I tried just having the claude extension review and look for gaps, and I figured it would go into each node of the workflow to see what filters or configurations are in it. But it goes into a node and then it can’t manage to exit out of that node and move forward with the task I’ve given it. I have been telling Claude code to do it from my desktop app and then it opens a browser and takes it over, so it’s not directly being prompted through the extension chat. Does that make a difference in output?

Tyler Pozun personally I’ve never had a problem with what you are explaining by using the chrome extension. TBH If i were you I’d try this. Explain the end goal of reviewing all nodes / steps in workflow x and in Claude chat or cowork and ask Claude to provide you with a chrome extension prompt and you might find that it builds out a much in depth prompt that allows it to move from node to node easier. It sounds rudimentary but for me personally this is working smoothly and it doesn’t get hung up digesting workflows until it hits limits then i just push it to compact the conversation and move forward and i get some more juice out of the squeeze until my usage limits reset.

Let me know if you have any other questions or if this does in fact help you.

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