GHL Command · yours to keep
Are you using all of it, and is it all working?
Two questions worth asking about any tool you pay for, and this one now answers both itself. Work down the page in order. It takes about twenty minutes, and everything on it stays true after you close the tab.
Restart Claude first
Do this before anything else. GHL Command updates often, and the checkup in the next section does not exist in older versions. Two minutes.
- Quit Claude completely. On a Mac that is Cmd+Q, not closing the window. On Windows, close it from the system tray as well as the window. Closing the window alone leaves the old version running.
- Open Claude again. It pulls the new version on startup by itself. Nothing to download, nothing to paste, no reinstall.
- Confirm it took. Ask Claude the question below. You want to see 3.68.0 or higher.
Give it a checkup
Point it at your own account and it tells you where you stand. It only reads. Nothing is written, nothing is changed, and it is safe to run on a live client account.
One command, three answers.
Section 1 — Connection
The plumbing. Your licence, your API key, whether your account is reachable, whether the Workflow Builder login is still good. If something fails here, everything below it is suspect, and it says so rather than pretending.
Section 2 — What still works
Every capability area gets one real read against your account, live, while you watch. Contacts, pipelines, calendars, workflows, funnels, forms, invoices, social, phone, the rest.
The whole section turns on one distinction. A clean read that finds nothing means this works, you just do not own any of these yet. A rejected read means GoHighLevel changed something. Those look identical from outside and mean opposite things, so they never get merged into one word.
| Verdict | What it means | Your move |
|---|---|---|
| WORKING | The read succeeded. If it says you have none yet, that is your account, not a fault. | Nothing. |
| BROKEN | GoHighLevel rejected a read that should work. Almost always their change, not yours. | Send us the report. |
| NO-ACCESS | Your API key was created without that permission ticked. | New key in GHL with every scope, run setup again. |
| UNAVAILABLE | That feature is not switched on for your GHL plan. | Nothing. Normal. |
| INCONCLUSIVE | GHL was slow or rate-limited. Proves nothing either way. | Run it again. |
Nothing is reported as a failure until it has failed three separate reads. That is not caution for its own sake: GoHighLevel's user list rejects a perfectly valid key roughly one call in six, so a single-shot check would accuse your key of being broken every sixth run.
Section 3 — What you are not using yet
Worked out from what your account actually contains, never from any record of what you have clicked. Nothing about your usage is collected or sent anywhere. Every line ends with the exact sentence to paste back.
What it can actually do
Thirty written jobs, grouped the way you would think of them rather than the way the software is built. Times are how long the job takes, not how long you spend typing. Anything marked FREE works on the read-only tier too.
Contacts and leads
- Count and report contacts The real number, with the date range printed next to it. FREE · 10 SEC
- Find and list contacts A clean list straight into a spreadsheet. FREE · 1 MIN
- Weekly account report Leads, pipeline and conversations in one ask. FREE · 1 MIN
- Bulk tag and clean up Hundreds of contacts in one instruction, saved as a list. 2 MIN
Automations
- Audit your workflows Find the silent failures before your client does. FREE · 2 MIN
- Build a nurture sequence Texts, emails, waits. Stops the second someone replies. 15 MIN
- Add an exit workflow Pull people out cleanly, tag them, notify you. 5 MIN
- Branch on tags and fields If VIP send this, otherwise send that. Built right first time. 5 MIN
- Send GHL data to another app Slack, Sheets, Zapier, Make, or your own software. 2 MIN
- What your AI bot knows Three places a bot reads from. One ignores your custom values. FREE · 5 MIN
Pipelines and sales
- Stand up a pipeline Stages, fields and tags for a new client in one conversation. 10 MIN
- Track and move opportunities Move deals, update values, see what is stuck. 1 MIN
- Bill a client and see what you were paid Products, invoices, coupons, money reads. 5 MIN
- Documents and contracts Sent for signature and tracked from Claude. 5 MIN
Client builds and pages
- Clone and rebrand a site Rebuild a page for a new client, with a rights check. 30 MIN
- Reuse a build across accounts Share a snapshot, and know what does not travel with it. 5 MIN
- Switch between client accounts Point Claude at any sub-account by name. FREE · 10 SEC
Booking, email and SMS
- Set up a booking calendar Right slots, buffers and the right person attached. 10 MIN
- See and manage appointments Who is booked today, this week, or for one client. FREE · 10 SEC
- Send texts and emails Any contact, in your voice, on the right channel. 30 SEC
- Build email templates Branded and reusable, without the GHL editor. 10 MIN
- Review your conversations Catch up on replies across every channel. FREE · 1 MIN
Forms, reviews and admin
- Create forms and read submissions Built to spec, submissions pulled into a summary. 10 MIN
- Trigger links Tracked links that fire automations when clicked. 2 MIN
- Watch your reviews New reviews across clients without logging into each. FREE · 30 SEC
- Custom fields and objects The records your niche needs, created correctly. 5 MIN
- Account admin basics Users, numbers, exports, and the whole exit package. 1 MIN
- Plan social posts Queue drafts across your connected accounts. 5 MIN
Your guide library
Every one of those thirty jobs is a written guide, and the whole library ships inside your install. You do not need this page to find them, and you do not need to be online.
A single page opens in your browser with all thirty. It is one self-contained file, so it works offline and it updates with the product.
How each guide is built
Every one is a job, not a feature. Same five parts, every time, so you learn the shape once:
| Part | What it gives you |
|---|---|
| What you'll get | The outcome in plain English, before you invest any time. |
| Say this | Two or three short prompts. Start here if you just want the thing done. |
| The pro prompt | The long, precise one we actually use on client accounts. Anything in [brackets] is yours to change. |
| Good to know | The context that stops you making the common mistake. |
| Where people go wrong | Real failures and their fixes, in a table. Read this one first if something already went sideways. |
Three things worth knowing
- Search by what you want, not what it is called. The search box matches on plain words. Type nothing happens and you land on the workflow audit. Type spreadsheet and you get the contact export.
- "Proven live" means exactly that. Where a pro prompt carries that mark, that exact wording was run against a real GoHighLevel account before it was published, and the guide records which account and when. If the wording ever changes, the mark comes off until it is re-proven.
- Some cards are not written yet. They say so, plainly, rather than opening onto something thin. Four are in progress right now.
Five of the guides are also public at ghlcommand.com/skills, if you ever want to send one to somebody who has not installed it yet.
The prompts worth stealing
Plain English, no syntax. Anything in [brackets] is yours to change. These are the ones that earn their keep in the first week.
Find what is already broken
The most common find is a workflow built before somebody deleted a pipeline stage. It looks perfectly healthy in GHL. That is the whole problem.
Stand up a new client
Build the follow-up
Answer a question without opening GHL
Work across all your accounts
When something looks wrong
GoHighLevel ships constantly, and occasionally one of their changes breaks something on our side. Here is how to tell that apart from a problem at your end, in about a minute.
That checks the plumbing only, and it is the faster answer when you suspect your own setup. The full checkup in section 2 covers this plus everything else.
| What you see | What it is | Fix |
|---|---|---|
| "Step 1 of 2 done" | Not a fault. It is being honest. | Say Unlock the Workflow Builder, then restart Claude once. |
| Workflow tools error after login | A new login only loads on a cold start. | Quit Claude fully and reopen. |
| Several areas say NO-ACCESS | Your key was made with only some scopes ticked. | New Private Integration in GHL with every scope, run setup again. |
| Anything says BROKEN | Almost certainly a GoHighLevel change. | Send us the whole checkup. |
| "It says I have no forms, but I do" | Read the verdict, not the count. | BROKEN or NO-ACCESS means it could not read them, not that they are gone. |
There is also a watchdog on our side now: it runs against a test account twice a day and compares every capability against a known-good baseline, so a GoHighLevel change that breaks something raises an alert with us rather than waiting for one of you to hit it. Your checkup is the same mechanism, pointed at your account.
Anything at all: support@ghlcommand.com, and a human answers.
Your first week
Five things, in this order. None takes long, and each one makes the next more useful.
- Today. Run the checkup on your busiest client account and act on the top item it flags. Just the top one.
- Then. Run the workflow audit on every account you manage. This is the one that finds money already leaking.
- This week. Open the guide library once and read the three cards closest to what you do daily.
- Before you build anything new. Pick one client and build a nurture plus its exit workflow end to end, so you have seen the full loop once.
- Monthly, and after any GHL update that feels odd. Run the checkup again. It takes a minute and it is the whole early-warning system.