uxie-ghl-factory

Use when programmatically creating, building, or publishing a GoHighLevel / HighLevel workflow, or adding triggers/actions/steps to one, via the internal builder API — e.g. "create a GHL workflow", "add a webhook/email step via API", "build a HighLevel automation programmatically", or when a workflow step created via API saves but won't open in the builder. Write counterpart to get-ghl-workflow-json (read-only). Draft-first; publish is opt-in and gated on user confirmation.

Capture, export, and validate GoHighLevel / HighLevel workflow JSON from the workflow builder's read-only internal endpoints. Use when the user asks to get, download, export, inspect, archive, harvest, or troubleshoot raw workflow JSON/config; workflow trigger JSON; sticky notes; step counts; workflow settings; trigger/action catalogs; or when they provide an app.gohighlevel.com location/workflow URL and want the underlying JSON. Uses browser JWT interception, human-paced throttling, and read-only GET requests only.

Read the RUNTIME of a GoHighLevel / HighLevel workflow — its execution logs, enrollment history, and per-step contact counts — from the builder's read-only internal endpoints. Use whenever the user wants to know what a workflow actually DID at runtime rather than how it's configured — for example "why are contacts stuck", "did this workflow actually send the email/SMS", "show me the execution logs", "run history", "enrollment history", "which step is everyone sitting at", "why did this step fail / get skipped", "is this branch dead", "how many contacts went down this path", "who exited early and why", or when they give an app.gohighlevel.com workflow URL and ask what happened to the contacts in it. This is the runtime sibling of get-ghl-workflow-json (which exports the static config). Uses browser JWT interception, human-paced throttling, and read-only GET requests only — never mutates enrollments.

GoHighLevel AI Studio — the AI website builder, internally called `vibe`. Use when a task involves reading, auditing, building, iterating on or publishing a site that was made in AI Studio, or when someone names a site and you do not know which GHL surface owns it. Also use when a GHL site cannot be found in funnels/websites — AI Studio is a separate collection and querying the wrong one returns an empty list.

Record a finding about GoHighLevel's internal API into the operator's Surface Console backlog, so it is not lost when the session ends. Use whenever you notice something worth keeping while working on the internal API — an endpoint that behaves differently than documented, a gap in the corpus, a stale or wrong claim, a rule nobody has proven, a capture that was never fed into the generator, a tool standing on evidence weaker than it looks. Also use when the operator says "note that", "add that to the backlog", "we should look at that later", or "don't lose that". ALWAYS propose the finding and wait for the operator's yes before writing anything.

GoHighLevel Conversation AI (the chat 'AI Employee') — bot config, the three-part prompt, actions (human handover, transfer, follow-up, contact-field updates, workflow triggers, appointment booking), knowledge-base triggers, channels, and the per-contact AI on/off switch. Use when the user says 'set up a chat bot', 'AI Employee', 'my bot isn't replying', 'it should hand over to a human', 'turn the AI off for this one contact', or names a Conversation AI agent. READS AND MOST WRITES GO THROUGH THE PUBLIC RAIL — see Rail routing below.

Build and operate GoHighLevel Events — create ticketed or RSVP events, add tickets, add-ons, schedule sessions and speakers, configure the event page's branding and check-in, publish, and read attendees. Use when the user says 'create an event', 'set up ticketing', 'sell tickets', 'add a session or speaker', 'my event page', 'RSVP', 'attendee list', 'check people in', or names a GHL event. Internal API — the public rail has no events surface at all.

GoHighLevel forms, surveys and quizzes — the builders under Sites. Use when a task involves listing, reading, creating, editing, duplicating, foldering or embedding a form, when a form_submission trigger needs the form's real field tags, or when someone asks why a form edit lost fields, why a survey is not on the forms list, or what a form's public URL is. Also use before writing to any form by raw_request — the save replaces the whole document and there is no undo.

Build GoHighLevel funnels, pages and websites via the internal API — create the funnel and its steps, author page content from native elements (not just custom HTML), art-direct it with the compiled stylesheet, bind calendars and products, set tracking and SEO, attach a domain, fix the public path, and audit a site for the references a template install leaves broken. Use when the user asks to build/create a GHL funnel, landing page, website, sales or booking funnel, to restyle one, to add custom HTML, to set tracking, SEO or routing, or when a GHL page renders wrong, 404s, says "Unable to find form", or shows different content in the builder than in public.

Build and manage GoHighLevel knowledge bases — the content that feeds both Conversation AI and Voice AI. Covers rich-text documents, FAQs, web crawling, web search, files, tables and Google Drive/Sheets sources, plus the trigger conditions that tell an agent WHEN to use each knowledge base. Use when the user says 'add a knowledge base', 'train the bot on this', 'the AI isn't using my KB', 'add FAQs', 'crawl my website', 'upload docs for the agent', or asks why an agent answers from the wrong source. Internal API — five of the nine source types have no public equivalent.

Build and operate GoHighLevel Memberships via the internal API — courses, chapters with drip/gating, lessons (text, video, audio, PDF, embed), quizzes with questions, assignments, offers, themes, credentials, enrollment, progress and submissions, plus community groups. Use when the user asks to build a GHL course or membership site, create an onboarding/client portal, add quizzes or assignments, enroll or revoke a member, issue a certificate, collect learner-submitted documents, or read course progress.

GoHighLevel platform fluency — the GHL object model, terminology, which API surface (public MCP vs internal) fits a job, and cross-domain gotchas (calendars, forms, custom fields, tags, snapshots). Use at the start of any GHL task, when unsure what a GHL term means, where a thing lives in GHL, or which API/tool can touch it.

GoHighLevel pipeline architect — designs opportunity pipelines and stages, diagnoses stuck/leaking pipelines, and wires stage↔automation interplay. Use when the user wants to build, redesign, review, or fix a GHL pipeline, stages, or opportunity flow ("set up a pipeline for X", "why do opportunities pile up in stage N"). Recons + reads the client brief before proposing anything. Public-API only (ToS-clean).

Set up, scope, or repair the public GoHighLevel MCP server (`@uxieee/ghl-mcp`) — install it in a folder, add sub-accounts with a Private Integration Token, point a folder at one client, or diagnose why a GHL tool can't see an account. Use when the user says "set up GHL here", "add a sub-account", "add a PIT", "connect this client", "why can't I see <client>", "no GHL tools in this folder", or when a GHL call fails with 401/403 or an unknown-location error. Covers both Claude Code and Codex. Public API only (ToS-clean) — the internal rail is /uxie-ghl-factory:internal-connect instead.

Re-prove the plugin's tools live on the designated sandbox, record a proof run per tool the suites exercised, and record failures in the backlog. Use when the operator invokes /ghl-recheck or asks to re-check, re-prove or refresh proofs. Records only — never fixes.

Map a GoHighLevel internal surface exhaustively — enumerate every screen, panel, control and save path a feature has, capture the real request behind each one, prove what each field does by differential, and write the result into the corpus. Use when the user wants to understand how a GHL feature works under the hood, extend an engine to an object the public API can't reach, re-sweep a surface that already has partial coverage, or asks to reverse-engineer / sniff / capture / trace anything internal. GHL permits inspecting your own account's traffic. This is a MAPPING skill, not a lookup: it finishes when the surface is exhausted, not when the first endpoint is found.

GoHighLevel snapshots — capturing a sub-account's assets into a reusable snapshot, refreshing one, curating what it carries, and checking load conflicts. Use when a task involves creating or updating a snapshot, deciding what an account template should include, asking why a snapshot came out empty or is stuck processing, or planning a rollout onto other sub-accounts. Read it BEFORE calling any /snapshots path by raw_request — two of the write endpoints silently do the wrong thing.

House conventions for building GoHighLevel systems — workflow naming and structure, tag/field/custom-value discipline, pipeline and opportunity decisions, copy rules, and the pre-build approval document the operator signs off before anything gets created. Account-agnostic, for ANY GHL sub-account. Use whenever designing, building, editing, reviewing, or discussing GHL workflows, automations, pipelines, stages, opportunities, tags, custom fields, custom values, calendars, or AI agents — even if the user never says "conventions" or "standards". Load it BEFORE proposing a design or creating any GHL object, so the proposal already looks the way the operator wants it.

Build and configure GoHighLevel Voice AI phone agents — the prompt, the voice, the actions (appointment booking, call/agent transfer, contact-field extraction, SMS, workflows, custom API), knowledge bases, MCP servers, working hours, and outbound consent. Use when the user says 'set up a voice agent', 'build a phone agent', 'my AI should answer calls', 'book appointments over the phone', 'outbound calling', 'the agent isn't transferring calls', 'change the voice', or names a Voice AI agent. Internal API — the public rail exposes only how the agent sounds, not what it does.

Fast-forward contacts parked at a GoHighLevel / HighLevel workflow WAIT step to the next step — the builder's "Action statistics → move to next step" control, driven via the internal API. Use to accelerate end-to-end workflow testing (drive a multi-day wait ladder to completion in minutes instead of waiting real time), to unstick contacts stranded at a wait, or when the user says "fast-forward this wait", "skip the wait", "move parked/stuck contacts to the next step", "requeue stuck contacts", "test this long delay without waiting days", or gives an app.gohighlevel.com workflow URL and asks to push contacts past a wait. This MUTATES live enrollments (it fires whatever steps come next, i.e. real SMS/email to real people) — it is a WRITE skill and follows the plugin's write-rails. It is the mutating counterpart to the read-only get-ghl-workflow-logs.

Senior GoHighLevel workflow architect — designs and builds automations (nurture, speed-to-lead, no-show recovery, internal ops, data hygiene, routing) grounded in the full trigger/action catalog and known anti-patterns. Use when the user wants to build, design, fix, or review a GHL workflow/automation, or asks "what automation should I set up for X". Recons + reads the client brief before proposing anything.