HighLevel already has an AI Funnel Builder and an AI Workflow Builder, but they're locked inside the UI. Many of us now run our businesses from Claude, Codex, Cursor or our own agents. Having to stop, log in and drive the builder by hand defeats the purpose of having an agent.
This is different from the existing "add workflow/funnel CRUD to the API" requests, which I also support. Raw endpoints force every agent to learn GHL's internal page and workflow JSON from scratch. The faster, safer win is to expose the builders you've already built as agent tools.
WHAT I'M ASKING FOR
  1. AI Builder as MCP tools
  • build_funnel: takes a goal, offer, audience, brand kit and steps (e.g., opt-in > VSL > book a call > thank you), and returns a draft funnel with real native elements (forms, surveys, calendars, order forms), not static HTML.
  • build_workflow: takes a plain-language description or structured spec, and returns a draft workflow with triggers, waits, if/else branches, tags and emails/SMS.
  • revise_funnel_page / revise_workflow: applies natural-language edits to an existing draft.
  1. Spec-as-code
Export any funnel, page or workflow to a documented JSON/YAML schema, and import it to create or update. Agencies can then version-control builds in Git and reuse them across sub-accounts without snapshots.
  1. Safe-by-default guardrails
  • Agent-created work lands as a draft and is never auto-published.
  • validate and dry_run endpoints catch problems like a missing calendar or a broken merge field before anything is saved.
  • Every build returns a preview URL and a screenshot.
  • Publishing is a separate publish call with its own scope, and audit logs show which agent and token made each change.
  • Everything an agent builds stays fully editable in the normal UI builder. API-first, UI-optional, so humans can fine-tune anything by hand.
  1. Scoped access
Location-level tokens with granular scopes (funnels:write without contacts:delete), with AI credits billed the same as in-app usage.
WHY THIS MATTERS
  • Agencies can spin up a client's funnel and follow-up workflow in minutes from one prompt instead of an hour of clicking.
  • It ends fragile browser automation (Selenium, Playwright, computer use) driving the UI.
  • HighLevel becomes the platform AI agents build on, not one they work around.
EXAMPLE
From Claude: "In the Smith Law sub-account, build a free-consultation funnel for uncontested divorce: opt-in, booking page using the 'Consult' calendar, thank-you page. Then create a workflow that texts the lead within 1 minute, emails a reminder 24h before the call, and tags no-shows." A minute later, both exist as drafts with a preview link.
Related ideas I support: "API to create Workflows," "Create funnels and workflow automations through API," "GHL MCP API - Critical Gaps."