@elitedcs/ghl-mcp 3.88.1 → 3.89.0-beta.1

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # Changelog
 
+## 3.89.0-beta.1: test build with safer workflow changes, one-click fixes and branded reports
+
+This is a beta, a test build for members who want the next release early. It is published under the "beta" label, so a normal install stays on 3.88.2 until the full release. Everything below is new since 3.88.2.
+
+**How to try the beta.** Paste this in a terminal: `npx -y @elitedcs/ghl-mcp@beta cli install --beta`, then quit Claude fully and open it again. If you build client accounts from the cockpit, also paste `npx -y @elitedcs/ghl-mcp@beta cli install --claude-code --beta` (it switches an existing GHL Command entry in Claude Code to the beta and says what it changed). To go back to the normal release, paste `npx -y @elitedcs/ghl-mcp@beta cli install --latest`, which points the Claude app back at the normal release and keeps your settings. If you added the beta to Claude Code, also paste `claude mcp remove ghl -s user` and then `claude mcp add --scope user -t stdio ghl -- npx -y @elitedcs/ghl-mcp@latest`. If you installed the cockpit's desktop launcher from the beta, run `npx -y @elitedcs/ghl-mcp@latest install-launcher` once so it falls back to the normal release too. When the full release comes out, a beta install does not move to it by itself: it stays on the beta until you run those go-back lines. Asking Claude for the GHL Command version on a beta says whether you are ahead of the normal release or whether a full release is out, and gives the go-back line.
+
+**Switching a workflow on is checked first.** Before a workflow goes live, GHL Command runs the same checks as validate_workflow on exactly the version that would go live. If any check finds an error, nothing is switched on and each error is named. Changes to a workflow that is already live get the same check before they are saved, so a broken step never reaches real contacts. Warnings never block.
+
+**A workflow update can no longer delete steps by accident.** When Claude saves a workflow's steps, the list it sends replaces the whole workflow. If that list would remove steps that are there now, the save is refused and the steps are listed, unless the exact number being removed is confirmed. A save also keeps the workflow's sender phone number, which some saves used to clear.
+
+**Webhook keys stay hidden.** Any reply that shows a workflow now hides the keys, tokens and passwords inside its webhook steps, showing only the last four characters. Sending that workflow back unchanged keeps the real keys, and a hidden key pasted anywhere else is refused.
+
+**Reports can carry your brand.** Each report can show your agency's name, colour and logo, a neutral look, or the GHL Command look, and the choice is remembered for each client. Your logo can be a file on your computer, so it prints and travels with a saved copy.
+
+**Secret Shopper for prospects (part of the cockpit plan).** Ask Claude to "run the Secret Shopper on" a prospect's website and it builds a one-page sales report: what a visitor would find missing, scored the same way every time. Gaps are pitched only under services you say you sell, and the report can end with a "Book the walkthrough" button that opens your own booking link, set in your agency profile.
+
+**One-click fixes on the Workflow Audit Pro report (part of the cockpit plan).** Some problems on the report now have a fix button, for example a message that greets a lead with a blank name. The button shows the exact change first and writes nothing until you approve. After you approve, it writes the change, reads it back from GoHighLevel to check it held, and offers Undo. If leads are waiting at that step, the fix stops and tells you why. On a live workflow, a fix is refused only if it would add a new problem; problems that were already there are listed as "already there, not changed by this fix" and do not block it.
+
+**Add your staff first (part of the cockpit plan).** Each client card now has an "Add your staff" step before Intake. List who works at the client; the cockpit checks the account's users by email, and Intake and Build wait until everyone listed is there, saying who is missing. With an agency key, "Add them for me" adds them; otherwise the step shows exactly where to add them in GoHighLevel. When a calendar is held back because its people are missing, the build says so in one plain sentence instead of building it with a blank name.
+
+**Clearer first steps for new members (part of the cockpit plan).** The cockpit's readiness check now also checks that GHL Command is added to Claude Code, which every client-build stage runs through, and `npx -y @elitedcs/ghl-mcp@beta cli install --claude-code --beta` adds it during the beta (on the full release it is the same line with `@latest` and without `--beta`). Every place that tells you where to find the Private Integration key, the Location ID or the staff page now gives the same directions, checked on a real GoHighLevel screen. A missing workflow builder login now says "Unlock the Workflow Builder", and the Verify step says it only reads, since builds no longer make pages.
+
+**Zoom in the cockpit (part of the cockpit plan).** Zoom is now on the Connections page. It reads only, and your recent recordings show in the daily brief.
+
+**Two clinics in one sub-account.** Blueprint can build a second clinic into a sub-account that already holds one. Each clinic's records carry its own short prefix, the cockpit keeps each clinic's records apart, and a build never changes the other clinic's live workflows.
+
+**Smaller changes.** Claude Desktop's menu now lists the server as GHL Command, and running the installer again renames an old entry instead of adding a second one. get_custom_values and export_account now show each custom value's value. The clinic preset says privacy instead of naming a specific privacy law.
+
+**What to try:** switch on a workflow that has a known error and see it named; ask Claude to change one step of a live workflow; run Workflow Audit Pro on a sandbox client and try a fix, then Undo; pick a brand for a report and save it as a PDF; ask Claude to run the Secret Shopper on a prospect's site; add a client's staff from the new step before Intake.
+
+## 3.88.2: a workflow waiting on a calendar is never switched on
+
+When a build asks to switch its workflows on, any workflow whose calendar could not be made yet now stays a draft, and the build lists it as a step for you with the reason. Before this fix such a workflow could be switched on without its calendar filter, so it would have reacted to bookings on every calendar in the account. Set up the calendar, then switch the workflow on.
+
 ## 3.88.1: light or dark, your choice
 
 The circle at the top right of the cockpit now opens your menu: your agency, connections, the Members Hub, and Appearance. Choose Light or Dark to keep that look whatever your computer is set to, or Auto to follow it. The choice is remembered on this computer and applied before the page appears, so it never flashes the other way.

package/README.md

@@ -113,7 +113,7 @@ Open Claude Desktop → **Settings...** → **Developer** → **Edit Config**. T
 ```json
 {
   "mcpServers": {
-    "ghl": {
+    "GHL Command": {
       "command": "npx",
       "args": ["-y", "@elitedcs/ghl-mcp@latest"]
     }
@@ -121,7 +121,9 @@ Open Claude Desktop → **Settings...** → **Developer** → **Edit Config**. T
 }
 ```
 
-If it already has other tools in it, do **not** paste over them — add only the `"ghl": { ... }` entry inside your existing `"mcpServers"` object. Save, then fully quit and reopen Claude. (Unsure? Run `npx -y @elitedcs/ghl-mcp@latest cli install --dry-run` to preview exactly what would change, or `--print-only` to get the merged file printed for you.)
+Older installs show it as ghl; that is the same thing.
+
+If it already has other tools in it, do **not** paste over them — add only the `"GHL Command": { ... }` entry inside your existing `"mcpServers"` object. Save, then fully quit and reopen Claude. (Unsure? Run `npx -y @elitedcs/ghl-mcp@latest cli install --dry-run` to preview exactly what would change, or `--print-only` to get the merged file printed for you.)
 
 </details>
 
@@ -448,7 +450,7 @@ Highlights (full guide: [`docs/HEADLESS.md`](docs/HEADLESS.md)):
 | `create_workflow` | Create a new workflow from scratch (starts as draft) |
 | `update_workflow_actions` | Add, edit, or remove actions, triggers, and branches in an existing workflow |
 | `delete_workflow_full` | Permanently delete a workflow |
-| `publish_workflow` | Publish a draft workflow to make it active |
+| `publish_workflow` | Publish a draft workflow to make it active. Runs the `validate_workflow` checks on the live version first and refuses if they find any error |
 | `get_trigger_registry` | Discover GHL's marketplace trigger apps (Zoom, WooCommerce, Shopify, etc.) and their available trigger templates |
 | `validate_workflow` | Pre-flight validation: scans every action and trigger for references to pipelines, stages, custom fields, users, and other workflows; verifies each ID exists. Catches the silent-failure bug where invalid IDs make GHL skip subsequent actions |
 | `build_goal_event` | Build a correctly-shaped goal-event node. Goals sit inline in the action chain — when the goal condition fires (e.g., review_request_clicked), the configured action runs (default: exit the workflow). Returns a `workflow_goal` node ready to wire into your actions array |
@@ -878,12 +880,12 @@ How the deny-list behaves:
 |---|---|---|
 | Only `setup_ghl_mcp` shows up; no other tools | Bootstrap mode — credentials not yet activated | Run `setup_ghl_mcp` with all four required fields, then restart Claude |
 | MCP tools don't appear (CLI) | Server not registered | Run `claude mcp add --scope user -t stdio ghl -- npx -y @elitedcs/ghl-mcp@latest` |
-| MCP tools don't appear (Desktop App) | Config missing or wrong | Check `~/Library/Application Support/Claude/claude_desktop_config.json` has a `ghl` entry under `mcpServers` (see Quick Start above for the exact block) |
+| MCP tools don't appear (Desktop App) | Config missing or wrong | Check `~/Library/Application Support/Claude/claude_desktop_config.json` has a `GHL Command` entry under `mcpServers` (see Quick Start above for the exact block) |
 | MCP tools don't appear (Desktop App) | App not restarted | Quit the Claude app completely (Cmd+Q on Mac) and reopen it |
 | `License key not found` | Wrong email or license_key | Both must match exactly what we have on file. Check spam for the welcome email. |
 | `License key already activated on 3 devices` | Activation limit hit | Email `support@ghlcommand.com` to reset |
 | `locationId is required` | Tool needs a location ID | Set `GHL_LOCATION_ID` in your env, or tell Claude which location to use |
-| `GHL API Error 401` | Invalid or expired key | Generate a new API key in GHL > Settings > Integrations |
+| `GHL API Error 401` | Invalid or expired key | Create a new key in the sub-account at Settings → Private Integrations (under Other settings) → Create New Integration |
 | `GHL API Error 403` | Key from wrong sub-account | Create a new Private Integration **inside the correct sub-account** |
 | `GHL API Error 403` (alt) | Missing permission scope | Edit your Private Integration in GHL and enable the required scope |
 | `GHL API Error 422` | Invalid request data | Check the error message for which field is wrong |
@@ -897,7 +899,7 @@ Built by **[Elite DCs, LLC](https://elitedcs.com)** — a digital marketing and
 
 **Tech stack:** TypeScript, Node.js, esbuild, MCP SDK, Zod, GHL API v2, Firebase Auth
 
-**Version:** 3.88.1
+**Version:** 3.89.0-beta.1
 
 ---