GoHighLevel CLI Builder
Manage GoHighLevel from the command line: contacts, workflows, forms, calendars, funnels and campaigns, always as drafts.
- gohighlevel
- cli
- automation
- saas
Video coming soon
This skill's short video goes here.What it does
This skill exposes the most common GoHighLevel operations (contacts, automations, native forms, round-robin calendars, funnels, landing pages, batch email campaigns, smart lists, contract templates, and SaaS sub-account audits) as repeatable commands. It lets you build and version an account's configuration without clicking through the UI, leaving everything ready for human review.
When to use it
- When you need to replicate the same GHL setup across multiple sub-accounts
- When you want to quickly audit workflows, forms, or calendars on an account
- When you're building a new email campaign or funnel and want it staged as a draft before activating
Steps
- Connect the GoHighLevel API using an agency or sub-account key
- List current state: contacts, workflows, existing calendars, funnels
- Define the desired change (new workflow, form, calendar, funnel, or campaign)
- Generate the resource as a draft or staging version inside GHL
- Validate fields, triggers, and round-robin logic before exposing it
- Present a change summary to the user and wait for explicit approval before publishing or activating
The skill
--- name: ghl-cli-builder description: Manage GoHighLevel (contacts, workflows, forms, calendars, funnels, campaigns, payments) from reproducible commands, always leaving changes in draft until approved. --- # GoHighLevel CLI Builder ## 1. Purpose Turn repetitive GoHighLevel configuration work into versionable commands: contacts, native workflows, forms, round-robin calendars, funnels, landing pages, batch email campaigns, smart lists, contract templates, and SaaS sub-account audits. ## 2. When to use it Use this skill if you administer multiple GHL sub-accounts, need to clone configurations between clients, or build funnels and automations often and want to stop depending on the visual editor for every small tweak. ## 3. Connection and scope Connect the API using an agency or sub-account key with the minimum required scopes. Never paste the key directly into chat; always reference it from environment variables or a secrets manager. ## 4. Workflow 1. Inspect the account's current state (contacts, workflows, calendars, funnels). 2. Specify the resource to create or modify. 3. Generate the resource in draft/staging mode. 4. Validate triggers, form fields, and round-robin assignment logic. 5. Show a readable summary of the proposed changes. ## 5. SaaS sub-account audits For SaaS accounts, the skill also runs a periodic audit: checks configured payments, active contract templates, and stale smart lists, producing a report instead of changing anything automatically. ## 6. Safety rules - Every change is generated as a draft first. - Nothing is published, sent, or activated (campaigns, live workflows, charges) without explicit user approval. - Contact data, metrics, or results are never invented: missing information is asked for. - No API key, token, or password is ever written in chat; always via environment variable or managed secret. ## 7. Deliverable A summary of proposed changes, the exact command to apply them, and the staging state in GoHighLevel, waiting for the green light before going to production.
For Claude Code, save it as ~/.claude/skills/ghl-cli-builder/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.
Want to build it together?
Inside PubliExpert AI Guild you get snapshots, live sessions and builders to finish it with.