APIs

With the rise of AI agents, we need the ability to fully manage Workflows via API — not just trigger them, but create, update, clone, and delete them programmatically. Use cases: AI agents that auto-build onboarding or follow-up sequences based on client data Automated provisioning of workflows when a new sub-account is created Dynamic workflow generation from templates without manual intervention Today, every workflow must be built manually in the UI. This is a hard blocker for teams building AI-native stacks on top of GHL. Full CRUD API for Workflows would unlock an entirely new tier of automation and make the platform significantly more competitive against tools that already expose this.

GoHighLevel must become the leader in being an API first company ie anything that can be done via GUI can be accomplished via API so that soon with GHL you can do more via APIs than the GUI.

Manually working with workflows is incredibly time-consuming for complex workflows. I would like API access to the workflows so I can get an AI agent to: read the existing workflows so it can understand: how they are used, how they connect together, what each is doing; change the workflow as needed through API requests, instead of requiring use of the Automations UI. The AI Agent within GoHighLevel is too dumb and can't perform detailed modifications across multiple nodes, and it is unable to understand the context of what a workflow is doing and how it connects to other workflows. On that topic, there needs to be a workflow description field, so the creator of a workflow can give a brief message of what the workflow is designed to do and why it's there, which should appear in the workflow index view.

I want the ability to create a funnel and associated workflows through the API. Is this something that can be done and if so, how soon can it be included in an update?

At the moment we can manually add in appointment notes. However, the ability to push appt. additional data via API into the notes field would be fantastic.

Use an endpoint like POST /smart-lists to create a smart list in order to be able to automate this

Right now the Calendars API only lets us update Weekly Working Hours (the PUT /calendars/schedules/event-calendar/:calendarId endpoint, using wday type rules). That pattern applies to every future date until it's changed again. Date-Specific Hours, which can override a single date without touching the recurring pattern, only exists in the app UI. There's no way to set, update, or remove a date-specific override through the API. This makes it impossible to automate a very common scheduling pattern: a calendar whose available hours shift for one specific week, without disturbing every other week. My use case: I keep two scheduling links open in the same daily block, from 1 to 2 PM. Most weeks, Behind the Numbers gets 1 PM and Partner Networking gets 2 PM. But when a partner can only meet at 2 PM for one particular week, three or four weeks out, I swap the times just for that week. With only the Weekly Working Hours API, there's no way to automate that swap. Updating the recurring pattern to reflect one week's exception ends up changing the pattern for every week, not just the one I meant to adjust. Request: Add API endpoints (or extend the existing schedule endpoint) to create, update, and delete Date-Specific Hours for a given event calendar, the same way Weekly Working Hours can already be managed. Something like passing a date type rule alongside the existing wday type would fully solve this. This would let anyone with a calendar that shifts around occasional appointments automate those one-off changes instead of manually editing the UI every time, or accepting a recurring pattern that's wrong for most of the weeks it applies to.

When a field is updated via it can't be used as a trigger, when that same field is update manually and save it is used in the automation. This is crucial for scaling. PLEASE prioritise this, a tiny chang to allow API user updates used as well

Ask AI should have official API or MCP access so it can safely read, analyze, create, and update elements inside a HighLevel sub-account. The goal is for Ask AI and connected AI agents to do more than answer questions. They should be able to help build, audit, and improve real systems inside HighLevel, such as contacts, opportunities, pipelines, workflows, calendars, forms, surveys, funnels, websites, custom fields, tags, tasks, invoices, payments, and reports. This access should be secure and controlled by permissions. Agencies should be able to decide what each AI agent can read, create, edit, or delete inside each sub-account. Needed controls: Read-only mode Approval mode before changes are applied Permissions by sub-account/location Permissions by module API/MCP tokens with specific scopes Audit logs Action history Rollback or restore options Clear error messages when an action is not allowed Example: An agency should be able to ask Ask AI or an external agent connected through MCP/API to review a sub-account, detect why leads are not moving forward, suggest improvements, and prepare the workflows or pipeline changes needed. The agent should show the changes first and only execute them after approval. This would make Ask AI a real operational layer inside HighLevel, not just a chat assistant. It would help agencies build faster, reduce manual work, improve account audits, and safely use AI agents inside real client accounts.

It would be nice to be able to customize cloned sites with API integration. Updating things like colors, visual assets but working in a templated format, allowing GHL SAAS account holder the ability to expeditiously clone and update with automation