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

package/guide/guide.html

@@ -4,7 +4,7 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>GHL Command — User Guide</title>
-<!-- guides-hash: 15d2093538a1928d -->
+<!-- guides-hash: f5a3b2744fb86bef -->
 <style>
 /* Deliberately light in every environment, including a dark-mode OS. This is a
    reference document people read at length, print, and save to PDF, and a page
@@ -320,7 +320,7 @@ Do not change anything. This is a read.</p></div>
 <li>The comparison is the useful one. Line a new client's account up against your template account and the setup list writes itself.</li>
 <li>User roles matter for workflow notifications. A notification pointed at somebody who has left the business fails silently, and this is where you spot them.</li>
 <li>Snapshots are how you carry a whole account setup to a new client. Claude can list what you have and create a share link for one.</li>
-<li>Chat creation is off until you enable “Let GHL Command create sub-accounts from chat” in Your agency. This switch does not enable deletion. GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key. Creation also needs an agency key with permission to create locations. Deletion requires separate confirmation and GoHighLevel authorization; its current plan gate has not been verified. Removing a saved key only disconnects an account.</li>
+<li>Chat creation is off until you enable “Let GHL Command create sub-accounts from chat” in Your agency. This switch does not enable deletion. GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key. To create it: in GoHighLevel's agency view, click Sub-Accounts in the left menu, then Create Sub-Account. Fill in the business details and save. Creation also needs an agency key with permission to create locations. Deletion requires separate confirmation and GoHighLevel authorization; its current plan gate has not been verified. Removing a saved key only disconnects an account.</li>
 <li>Needs the full license. Reading users and numbers is free.</li>
 <li><b>Destructive actions ask before they act.</b> Twelve of them did not until 31 August, including deleting a custom field, which erases that field on every contact, and deleting or voiding an invoice.</li>
 <li><b>Changing a sub-account's business details is refused if Claude cannot read the account first.</b> Those are the details your text-message registration is filed against, and a check that could not run is not a check that passed. Timezone and other settings are unaffected.</li>
@@ -571,7 +571,7 @@ Before you build: confirm the [Consult] calendar exists and scope the trigger to
 <li>Claude confirms the calendar and ties the trigger to it.</li>
 <li>It uses appointment-relative waits, so the reminders track the booking rather than the enrolment.</li>
 <li>It writes the messages with the real booking fields in them and shows you first.</li>
-<li>It builds as a draft; you publish it.</li>
+<li>It builds as a draft; you publish it. Claude runs the pre-flight check on that exact version first, and publishing is refused until it comes back with no errors.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Good to know</h2>
@@ -697,7 +697,7 @@ Build nothing until I say approved.</p></div>
 <li>If a workflow step moves a deal to a new stage, the plan makes it find the deal first. That pairing is checked before the build runs, because a stage move on its own saves cleanly and then does nothing at all.</li>
 <li>The manual list is short but real: connecting a payment provider, phone and A2P registration, connecting social accounts, and domain settings. Those need a human with account access, and no tool can honestly do them for you.</li>
 <li><b>If you are told there are no submissions, the answers are not lost.</b> GoHighLevel does not report submissions for forms created outside its own editor, which is every intake form this installs, so the tool that reads submissions will say there are none even after your client has filled it in. The answers are on the contact tagged <code>blueprint-intake</code>. Say &quot;read the intake from the contact&quot; and Claude will pull it from there with the ordinary contact tools and carry on into the plan.</li>
-<li>Blueprint builds assets inside a registered sub-account. GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key. Confirm that account before building. On an account that has been built before, it refuses to quietly compose a second, different plan. That refusal is deliberate: it is what stops you ending up with duplicate pipelines and duplicate workflows.</li>
+<li>Blueprint builds assets inside a registered sub-account. GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key. To create it: in GoHighLevel's agency view, click Sub-Accounts in the left menu, then Create Sub-Account. Fill in the business details and save. Confirm that account before building. On an account that has been built before, it refuses to quietly compose a second, different plan. That refusal is deliberate: it is what stops you ending up with duplicate pipelines and duplicate workflows.</li>
 <li>The build plan is worth keeping. It is the document you walk your client through on the kickoff call.</li>
 <li>Budget an hour end to end, most of it your review time. The building itself is minutes.</li>
 <li>Needs the full license.</li>
@@ -1169,7 +1169,7 @@ Before you build: look up the real calendar, the real workflows you are removing
 <li>Claude looks up every workflow you are removing them from by name, in the account, and tells you if one does not exist.</li>
 <li>It pairs the stage move with a find step, so the move has something to act on.</li>
 <li>It shows you the plan and the confirmation messages before building.</li>
-<li>It builds as a draft; you publish it.</li>
+<li>It builds as a draft; you publish it. Claude runs the pre-flight check on that exact version first, and publishing is refused until it comes back with no errors.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Good to know</h2>
@@ -1344,8 +1344,44 @@ Before you build: look up the real calendar, the real workflows you are removing
 <p class="gpara">Remove the saved connection or take back the provider's permission.</p>
 <p class="gpara">Disconnect Google Drive in your Claude's connector settings.</p>
 </div>
+<div class="gsec"><h2>Zoom · not yet checked</h2>
+<p class="gpara">A Server-to-Server OAuth app is a small private app you make in your own Zoom account; its Account ID, Client ID and Client Secret let this machine read your cloud recordings without your Zoom password.</p>
+<p class="gpara">not yet checked</p>
+<h3>What it gives you</h3>
+<p class="gpara">Adds the meetings you recorded to the Zoom cloud in the last 7 days to your brief: how long each ran, whether a transcript or audio and video was saved, and a link to open it. A meeting recorded yesterday is flagged so you review it and send follow-ups.</p>
+<h3>What you need</h3>
+<p class="gpara">Have these ready before you connect.</p>
+<ul>
+<li>A Zoom account where you are the owner or an admin, with cloud recording turned on. Zoom's paid plans include it.</li>
+<li>Permission to build apps on marketplace.zoom.us. An account owner or admin normally has it.</li>
+<li>About ten minutes to make the app and copy three values: the Account ID, the Client ID and the Client Secret.</li>
+</ul>
+<h3>How to connect</h3>
+<p class="gpara">Follow these steps to give this machine access.</p>
+<h4>8 steps</h4>
+<p class="gpara">These steps have not been checked on a real screen yet.</p>
+<ol class="steps">
+<li>Open marketplace.zoom.us and sign in with your Zoom account.</li>
+<li>Choose Develop at the top right, then Build App.</li>
+<li>Pick Server-to-Server OAuth App and choose Create. Give it a name you will recognise, such as Morning brief reader.</li>
+<li>On App Credentials, copy the Account ID, the Client ID and the Client Secret. Keep them somewhere private until you paste them here.</li>
+<li>Fill in the Information page with your name and email; Zoom asks for them before it lets the app run.</li>
+<li>Open Scopes and choose Add Scopes. Add the user read scope, which Zoom may list as View a user (user:read:user:admin), and the cloud recording read scope, which Zoom may list as View all user recordings (cloud&#95;recording:read:list&#95;user&#95;recordings:admin). Add nothing else.</li>
+<li>Open Activation and choose Activate your app.</li>
+<li>On the Zoom card on the Connections screen, paste the Account ID, the Client ID and the Client Secret, and choose Connect.</li>
+</ol>
+<h3>What to say</h3>
+<p class="gpara">In a Claude chat you can say one of these to connect or use it.</p>
+<ul>
+<li>“Connect my Zoom.”</li>
+<li>“Disconnect my Zoom.”</li>
+</ul>
+<h3>How to take access back</h3>
+<p class="gpara">Remove the saved connection or take back the provider's permission.</p>
+<p class="gpara">Choose Disconnect on this system's Connections card to remove the app's credentials from this machine. To take access back everywhere, open marketplace.zoom.us, then Manage, open the app and deactivate or delete it.</p>
+</div>
 <div class="gsec"><h2>Not built yet</h2>
-<p class="gpara">Not built yet: Zoom, Plaud.</p>
+<p class="gpara">Not built yet: Plaud.</p>
 </div>
   <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
   </main></div>
@@ -1654,9 +1690,9 @@ Show me the first ten rows in the chat so I can sanity check them before you wri
   <a class="back" href="#top">&#8592; All guides</a>
   <div class="gsec"><h2>Before you start: what you need</h2>
 <ul>
-<li><b>A GoHighLevel plan that includes API access.</b> That is GoHighLevel Unlimited ($297 a month) or Agency Pro ($497). The $97 Starter plan has no API, so nothing can connect to it, GHL Command included. Check under Settings, then Billing, in GoHighLevel before you install.</li>
+<li><b>A GoHighLevel plan that includes API access.</b> That is GoHighLevel Unlimited ($297 a month) or Agency Pro ($497). The $97 Starter plan has no API, so nothing can connect to it, GHL Command included. Check under Settings, then Billing, in GoHighLevel before you install. On Unlimited ($297), GoHighLevel does not let GHL Command create sub-accounts or add staff users. Both are Agency Pro only, so on $297 you do those two jobs in GoHighLevel yourself.</li>
 <li><b>Claude on this computer.</b> GHL Command runs inside the Claude Desktop app or inside Claude Code in a terminal. It cannot run in a claude.ai tab in your browser. Not sure which you have? The Members Hub page Which Claude do I use? settles it in two minutes, and with it every later question about restarts.</li>
-<li><b>A Private Integration token</b> from the sub-account you want to work in, and that sub-account's location ID (the part of its GoHighLevel web address after /location/). Claude asks for both during setup, not the installer. GoHighLevel shows the token under Settings, then Private Integrations.</li>
+<li><b>A Private Integration token</b> from the sub-account you want to work in, and that sub-account's location ID. Claude asks for both during setup, not the installer. Inside the sub-account, create the token under Settings, then Private Integrations (under Other settings), then Create New Integration. The location ID is under Settings, then Business Profile, at the top of the General Information card, with a copy button. It is also the part of the sub-account's web address after /location/.</li>
 </ul>
 </div>
 <div class="gsec"><h2>What you'll get</h2>
@@ -1668,9 +1704,10 @@ Show me the first ten rows in the chat so I can sanity check them before you wri
 </div>
 <div class="gsec"><h2>The two steps</h2>
 <ol class="steps">
-<li><b>Paste one command, once.</b> Open a terminal. On a Mac press Cmd+Space, type Terminal and press Return. On Windows press the Windows key, type cmd and press Enter. Paste <code>npx -y @elitedcs/ghl-mcp@latest cli install</code> and press Enter. That one command writes GHL Command into the Claude Desktop app's settings for you, so there is no JSON to hand-edit and anything else already in there is left alone. Your account and your license are connected in the next breath, inside Claude, not in the terminal. <b>Using Claude Code instead?</b> Paste this line instead of the installer: <code>claude mcp add --scope user -t stdio ghl -- npx -y @elitedcs/ghl-mcp@latest</code>. Then quit Claude fully and open it again (Desktop app: Cmd+Q on a Mac, not just closing the window; on Windows close it from the system tray too. Claude Code: start a new session). The new tools only load on a fresh start. Now say to Claude: &quot;Set up GHL Command with my license key.&quot; Claude asks for your email, your license key and that sub-account's Private Integration token and location ID, then answers: &quot;Step 1 of 2 done.&quot;</li>
+<li><b>Paste one command, once.</b> Open a terminal. On a Mac press Cmd+Space, type Terminal and press Return. On Windows press the Windows key, type cmd and press Enter. Paste <code>npx -y @elitedcs/ghl-mcp@latest cli install</code> and press Enter. That one command writes &quot;GHL Command&quot; into the Claude Desktop app's settings for you, so there is no JSON to hand-edit and anything else already in there is left alone. Your account and your license are connected in the next breath, inside Claude, not in the terminal. <b>Building client accounts from the cockpit?</b> The installer writes GHL Command into the Claude Desktop app only, and the cockpit runs every client-build stage through Claude Code. So also paste <code>npx -y @elitedcs/ghl-mcp@latest cli install --claude-code</code> once. It adds GHL Command to Claude Code and changes nothing else. The cockpit's Check readiness then confirms it. <b>Using Claude Code instead?</b> Paste this line instead of the installer: <code>claude mcp add --scope user -t stdio ghl -- npx -y @elitedcs/ghl-mcp@latest</code>. Then quit Claude fully and open it again (Desktop app: Cmd+Q on a Mac, not just closing the window; on Windows close it from the system tray too. Claude Code: start a new session). The new tools only load on a fresh start. Now say to Claude: &quot;Set up GHL Command with my license key.&quot; Claude asks for your email, your license key and that sub-account's Private Integration token and location ID, then answers: &quot;Step 1 of 2 done.&quot;</li>
 <li><b>One 60-second browser login.</b> Say to Claude: &quot;Unlock the Workflow Builder.&quot; A Chrome window opens and you log into GoHighLevel like you always do. This is how GHL itself trusts the workflow tools. One last step: quit Claude fully and open it once more so the workflow tools load. That is two restarts in all, thirty seconds each, and the install is finished.</li>
 </ol>
+<p class="gpara">Older installs show it as ghl; that is the same thing.</p>
 </div>
 <div class="gsec"><h2>Say this</h2>
 <div class="prompt"><q>Set up GHL Command with my license key.</q><button class="copy" type="button">Copy</button></div>
@@ -1810,7 +1847,7 @@ Before you build: confirm the account has a phone number that can send texts, an
 <li>Claude checks the account can actually send a text before it builds anything that sends one.</li>
 <li>It writes both messages for the caller you described and shows you them first.</li>
 <li>It builds the workflow as a draft and hands you the link to read it in GoHighLevel.</li>
-<li>You publish it.</li>
+<li>You publish it. Claude runs the pre-flight check on that exact version first, and publishing is refused until it comes back with no errors.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Good to know</h2>
@@ -1947,7 +1984,7 @@ Before you build: confirm the [Consult] calendar exists in this account and scop
 <li>Claude confirms the calendar exists and ties the trigger to it, rather than to every appointment in the account.</li>
 <li>It writes the messages and shows you them before building.</li>
 <li>It builds as a draft and hands you the link.</li>
-<li>You publish it, and from then on the empty chair has a process attached to it.</li>
+<li>You publish it, and from then on the empty chair has a process attached to it. Claude runs the pre-flight check on that exact version first, and publishing is refused until it comes back with no errors.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Good to know</h2>
@@ -2500,7 +2537,7 @@ Before you build: look up the real form, the real pipeline and stage, and the re
 <li>Claude looks up the real form, pipeline, stage and user in the account. Not names you typed, actual records.</li>
 <li>It writes the messages for the audience you described and shows you every one of them before anything is built.</li>
 <li>It builds the workflow as a draft, checks each piece exists after it creates it, and hands you the link.</li>
-<li>You read the messages, then publish it yourself.</li>
+<li>You read the messages, then publish it yourself. Claude runs the pre-flight check on that exact version first, and publishing is refused until it comes back with no errors.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Good to know</h2>
@@ -2989,7 +3026,7 @@ Do not add anyone to the workflow yet. Build it, show me the messages, and stop.
 <li>Claude builds the segment first and tells you the count, so you approve a number before you approve a campaign.</li>
 <li>It writes all five messages and shows you every one.</li>
 <li>It builds the workflow as a draft. Nobody is enrolled.</li>
-<li>You read it, publish it, then add the tag to the segment in batches.</li>
+<li>You read it, publish it, then add the tag to the segment in batches. Claude runs the pre-flight check on that exact version before it publishes, and publishing is refused until it comes back with no errors.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Good to know</h2>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.88.1",
+  "version": "3.89.0-beta.1",
   "mcpName": "io.github.drjerryrelth/ghl-command",
   "description": "GoHighLevel MCP Server for Claude. 250 tools — full CRM, automation, marketing control, account-wide workflow audit, live funnel-capture verification, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
   "main": "dist/index.js",

package/skills/blueprint/presets/clinic.preset.json

@@ -1764,7 +1764,7 @@
         "owner": "OPERATOR-UI",
         "title": "Add the people who get lead alerts and call tasks",
         "trigger": "the brief listed no staff",
-        "instruction": "In the sub-account go to Settings > My Staff and add at least one user (yourself is fine): name, email, role. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
+        "instruction": "In the sub-account go to Settings → My Staff (called Users in newer accounts) → + Add User and add at least one person (yourself is fine): enter their name and the same email address listed in the intake. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
         "produces": null,
         "successCheck": "At least one user exists and no workflow step still shows \"user pending\"",
         "blocks": [
@@ -1880,7 +1880,7 @@
         "owner": "TEAM",
         "title": "Read every template once for your compliance rules",
         "trigger": "always, before publishing",
-        "instruction": "Open Marketing > Emails > Templates and Conversations > Snippets. The copy never names a condition, diagnosis, treatment or medication; confirm your edits keep it that way and match the compliance notes you gave at intake (HIPAA, state advertising rules, insurance language). Ten minutes now saves a complaint later.",
+        "instruction": "Open Marketing > Emails > Templates and Conversations > Snippets. The copy never names a condition, diagnosis, treatment or medication; confirm your edits keep it that way and match the compliance notes you gave at intake (privacy, state advertising rules, insurance language). Ten minutes now saves a complaint later.",
         "produces": null,
         "successCheck": "Every template read by a responsible person; no clinical detail in any text or email",
         "blocks": [

package/skills/blueprint/presets/coach.preset.json

@@ -1766,7 +1766,7 @@
         "owner": "OPERATOR-UI",
         "title": "Add the people who get lead alerts and call tasks",
         "trigger": "the brief listed no staff",
-        "instruction": "In the sub-account go to Settings > My Staff and add at least one user (yourself is fine): name, email, role. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
+        "instruction": "In the sub-account go to Settings → My Staff (called Users in newer accounts) → + Add User and add at least one person (yourself is fine): enter their name and the same email address listed in the intake. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
         "produces": null,
         "successCheck": "At least one user exists and no workflow step still shows \"user pending\"",
         "blocks": [

package/skills/blueprint/presets/ecommerce.preset.json

@@ -1263,7 +1263,7 @@
         "owner": "OPERATOR-UI",
         "title": "Add the people who get lead alerts and call tasks",
         "trigger": "the brief listed no staff",
-        "instruction": "In the sub-account go to Settings > My Staff and add at least one user (yourself is fine): name, email, role. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
+        "instruction": "In the sub-account go to Settings → My Staff (called Users in newer accounts) → + Add User and add at least one person (yourself is fine): enter their name and the same email address listed in the intake. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
         "produces": null,
         "successCheck": "At least one user exists and no workflow step still shows \"user pending\"",
         "blocks": [

package/skills/blueprint/presets/generic-client.preset.json

@@ -1789,7 +1789,7 @@
         "owner": "OPERATOR-UI",
         "title": "Add the people who get lead alerts and call tasks",
         "trigger": "the brief listed no staff",
-        "instruction": "In the sub-account go to Settings > My Staff and add at least one user (yourself is fine): name, email, role. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
+        "instruction": "In the sub-account go to Settings → My Staff (called Users in newer accounts) → + Add User and add at least one person (yourself is fine): enter their name and the same email address listed in the intake. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
         "produces": null,
         "successCheck": "At least one user exists and no workflow step still shows \"user pending\"",
         "blocks": [

package/skills/blueprint/presets/local-service.preset.json

@@ -1776,7 +1776,7 @@
         "owner": "OPERATOR-UI",
         "title": "Add the people who get lead alerts and call tasks",
         "trigger": "the brief listed no staff",
-        "instruction": "In the sub-account go to Settings > My Staff and add at least one user (yourself is fine): name, email, role. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
+        "instruction": "In the sub-account go to Settings → My Staff (called Users in newer accounts) → + Add User and add at least one person (yourself is fine): enter their name and the same email address listed in the intake. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
         "produces": null,
         "successCheck": "At least one user exists and no workflow step still shows \"user pending\"",
         "blocks": [

package/skills/blueprint/presets/med-spa.preset.json

@@ -1753,7 +1753,7 @@
         "owner": "OPERATOR-UI",
         "title": "Add the people who get lead alerts and call tasks",
         "trigger": "the brief listed no staff",
-        "instruction": "In the sub-account go to Settings > My Staff and add at least one user (yourself is fine): name, email, role. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
+        "instruction": "In the sub-account go to Settings → My Staff (called Users in newer accounts) → + Add User and add at least one person (yourself is fine): enter their name and the same email address listed in the intake. Every \"alert a real person\" and \"call task\" step in the workflows is already built and waiting; the moment a user exists, open each workflow and pick them in the Notify and Task steps (or re-run the build with useSavedPlan:true so the pending steps are re-pointed).",
         "produces": null,
         "successCheck": "At least one user exists and no workflow step still shows \"user pending\"",
         "blocks": [