@elitedcs/ghl-mcp 3.65.2 → 3.65.3

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## 3.65.3 — the guide now covers most of what you are paying for
+
+The library had guides for 20 of the 50 areas the product touches. Six shipped
+guides were listed as covering things they never actually mentioned. That is
+now 38, and the new material was checked against two real accounts before it
+was written, not recalled.
+
+- **Your team, numbers, and files** are covered in account admin: who has access,
+  which phone numbers the account owns, what is in media storage.
+- **Surveys** are covered alongside forms, including why "show me my forms" never
+  returns them and where a client's missing intake answers usually are.
+- **Email campaigns** are covered alongside templates, including how to spot an
+  old sequence still sending against a client's list.
+- **Review links, connected social accounts and bulk campaigns** each got the
+  section their guide had been promising.
+
+**Webhooks do not work and never did.** All five webhook tools call an address
+GoHighLevel does not have. Four different paths, two API versions, two accounts:
+404 every time. They are now marked as not guide material rather than left
+looking available. Whether they get repaired or withdrawn is a separate call.
+
+The billing guide added in 3.65.2 also covers estimates now, so the second
+half-written billing guide has been retired rather than left on the shelf.
+
 ## 3.65.2 — invoicing never worked, and the guide stopped being one long page
 
 - **Fix: creating an invoice failed every single time.** The call sent five

package/dist/index.js

@@ -2854,7 +2854,7 @@ var require_package = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "@elitedcs/ghl-mcp",
-      version: "3.65.2",
+      version: "3.65.3",
       mcpName: "io.github.drjerryrelth/ghl-command",
       description: "GoHighLevel MCP Server for Claude. 238 tools \u2014 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/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: 580f584a6ea0c9bb -->
+<!-- guides-hash: b69654ea29507200 -->
 <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
@@ -245,8 +245,7 @@ body.app.reading #indexview{display:none}
 <div class="catsec" id="cat-pipelines-and-sales"><h2>Pipelines and sales</h2><div class="cards"><a class="card pub" href="#g-documents-and-contracts" data-k="documents contracts proposals signature send sign agreement esign template"><h3>Documents and contracts</h3><p>Proposals and contracts sent for signature and tracked from Claude.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-invoices-and-payments" data-k="invoice bill billing payment paid product price coupon promo code discount transactions orders revenue estimate"><h3>Bill a client and see what you were paid</h3><p>Products, invoices, coupons, and the money reads, without opening the billing screen.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-stand-up-a-pipeline" data-k="pipeline stages create new client setup opportunity sales process deal stages"><h3>Stand up a pipeline</h3><p>Stages, fields, and tags for a new client in one conversation.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~10 minutes</span><span class="open">Open guide &#8594;</span></div></a>
-<a class="card pub" href="#g-track-and-move-opportunities" data-k="opportunities deals move stage track stuck value won lost pipeline board"><h3>Track and move opportunities</h3><p>Move deals between stages, update values, and see what is stuck.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~1 minute</span><span class="open">Open guide &#8594;</span></div></a>
-<button class="card locked" type="button" data-k="invoices estimates payments send record coupons products" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Invoices and estimates. Coming in a product update."><h3>Invoices and estimates</h3><p>Create, send, and track invoices and estimates without opening GHL.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~3 min</span><span class="applabel">Coming in an update</span></div></button></div></div>
+<a class="card pub" href="#g-track-and-move-opportunities" data-k="opportunities deals move stage track stuck value won lost pipeline board"><h3>Track and move opportunities</h3><p>Move deals between stages, update values, and see what is stuck.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~1 minute</span><span class="open">Open guide &#8594;</span></div></a></div></div>
 <div class="catsec" id="cat-client-builds-and-pages"><h2>Client builds and pages</h2><div class="cards"><a class="card pub" href="#g-snapshots-and-reusing-a-build" data-k="snapshot template reuse clone account new client share link import rollout onboarding"><h3>Reuse a build across client accounts</h3><p>Find your snapshots, share one, and know exactly what does not travel with it.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~5 minutes</span><span class="open">Open guide &#8594;</span></div></a>
 <button class="card locked" type="button" data-k="blueprint client account build intake onboarding new complete template" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="The Blueprint: build a client account. Coming in a product update."><h3>The Blueprint: build a client account</h3><p>From intake form to a complete, reviewed account build you approve before it runs.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~1 hour</span><span class="applabel">Coming in an update</span></div></button>
 <button class="card locked" type="button" data-k="page studio compose website landing pages funnel" data-toast="This guide arrives in a product update — your install picks it up automatically." title="Coming in a product update." aria-label="Page Studio: pages and sites. Coming in a product update."><h3>Page Studio: pages and sites</h3><p>Compose landing pages and full sites that render correctly in GHL.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~20 min</span><span class="applabel">Coming in an update</span></div></button>
@@ -317,6 +316,18 @@ Do not change anything. This is a read.</p></div>
 <div class="gsec"><h2>Where people go wrong</h2>
 <div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;Workflow notifications go to nobody.&quot;</td><td>They point at a user who has gone. List the users, then ask Claude to repoint the notification.</td></tr><tr><td>&quot;Texts fail on a new client account.&quot;</td><td>The account has no number, or is not registered for texting yet. The number list shows you in seconds.</td></tr><tr><td>&quot;The export is huge.&quot;</td><td>Ask for the part you care about: &quot;just the workflows and pipelines by name&quot;.</td></tr><tr><td>&quot;The comparison says the other account is empty.&quot;</td><td>Each account's key only works on that account, so the other one could not be read at all. Save its key once and compare again. Claude now says &quot;unavailable&quot; rather than showing zeros, so you can tell the two apart.</td></tr></table></div>
 </div>
+<div class="gsec"><h2>The rest of the account</h2>
+<p class="gpara">One ask covers the things you only look at when something is wrong.</p>
+<div class="prompt"><q>Who has access to this account?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>What phone numbers does this account have?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me the files in media storage.</q><button class="copy" type="button">Copy</button></div>
+<ul>
+<li><b>Users</b> come back with their name, email, phone and role. This is the fastest way to answer &quot;who can see this client's data&quot;, and you need a real user id whenever a workflow has to notify or assign someone.</li>
+<li><b>Phone numbers</b> list with their label, so you can tell which number a client is actually texting from before you wire a workflow to it.</li>
+<li><b>Media</b> is the file library behind your emails and pages. Worth a look when an image stops rendering.</li>
+<li><b>Businesses</b> are GHL's optional grouping layer above contacts. Most accounts have none, and an empty answer here means exactly that, not a failure.</li>
+</ul>
+</div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
 <li>switch-between-client-accounts</li>
@@ -634,6 +645,16 @@ When it saves, list the templates in the account so I can see it landed, and tel
 <div class="gsec"><h2>Where people go wrong</h2>
 <div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The email arrived as one wall of text.&quot;</td><td>Say how you want it structured: short paragraphs, one button. Claude will lay it out.</td></tr><tr><td>&quot;The name did not merge.&quot;</td><td>The merge field name has to match this account's setup. Ask Claude to check the field exists before saving.</td></tr><tr><td>&quot;I have four versions of the same template.&quot;</td><td>Say &quot;update the existing template&quot; instead of describing it again. Repeating the description creates a new one.</td></tr></table></div>
 </div>
+<div class="gsec"><h2>Campaigns, and what is scheduled</h2>
+<p class="gpara">Templates are what an email looks like. Campaigns are the sends built on them.</p>
+<div class="prompt"><q>What email campaigns exist in this account?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me every scheduled email send.</q><button class="copy" type="button">Copy</button></div>
+<ul>
+<li>Campaigns come back with their name, subject and how many sends sit under them, which is the quickest way to spot an old sequence still running against a client's list.</li>
+<li>A template is not a send. Editing one does not change anything already scheduled.</li>
+<li>An empty campaign list on a busy account usually means the sends live in workflows instead. Ask for the workflows.</li>
+</ul>
+</div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
 <li>build-nurture-sequence</li>
@@ -895,6 +916,16 @@ When it saves, read the form back to me question by question, and tell me exactl
 <div class="gsec"><h2>Where people go wrong</h2>
 <div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The answers are not on the contact record.&quot;</td><td>The questions were not wired to fields. Ask Claude to wire them, and it will create the fields it needs.</td></tr><tr><td>&quot;The form saved but looks wrong on the page.&quot;</td><td>The page has its own copy of the form settings. Rebuild the page section with the form after you finish the form, not before.</td></tr><tr><td>&quot;Nobody finished the form.&quot;</td><td>Too many questions. Cut it to four and put the rest in the follow-up conversation.</td></tr><tr><td>&quot;It says my test phone number is invalid.&quot;</td><td>Numbers starting 555 are reserved for fiction and GHL rejects them. Test with a real-format number instead.</td></tr><tr><td>&quot;I submitted a test and the contact does not come up in search.&quot;</td><td>Search runs off an index that lags a few moments behind. The contact record itself is already correct, so open it directly or just ask again shortly.</td></tr></table></div>
 </div>
+<div class="gsec"><h2>Surveys, and the difference from forms</h2>
+<p class="gpara">A form captures somebody in one screen. A survey walks them through questions, often over several pages, and stores its answers separately.</p>
+<div class="prompt"><q>List the surveys in this account.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Show me the last 20 survey responses.</q><button class="copy" type="button">Copy</button></div>
+<ul>
+<li>Ask for surveys explicitly. &quot;Show me my forms&quot; will not include them, and a client asking why their intake answers are missing is usually looking at a survey.</li>
+<li>Both return their answers with the contact attached, so you can go from a response straight to the person.</li>
+<li>Submissions are paged. Ask for a date range or a limit, or you will get the first page and think that is all of them.</li>
+</ul>
+</div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
 <li>page-studio-pages-and-sites</li>
@@ -1331,6 +1362,14 @@ Before you send: confirm the exact contact you matched, show me their phone numb
 <div class="gsec"><h2>Where people go wrong</h2>
 <div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The text says sent but never arrived.&quot;</td><td>The sub-account is not fully registered for texting. Check A2P status in GHL. This is the most common cause by far.</td></tr><tr><td>&quot;It went to the wrong person.&quot;</td><td>Two contacts share a first name. Always give the full name or email and read the match Claude shows you.</td></tr><tr><td>&quot;I meant to send twenty of these.&quot;</td><td>Twenty one-off sends is a sequence in disguise. Build a nurture; it stops on reply and keeps you out of trouble.</td></tr></table></div>
 </div>
+<div class="gsec"><h2>Bulk campaigns</h2>
+<p class="gpara">Individual messages are one thing; a campaign is the older bulk-send layer sitting alongside your workflows.</p>
+<div class="prompt"><q>What campaigns are running in this account?</q><button class="copy" type="button">Copy</button></div>
+<ul>
+<li>Most modern accounts have none, because workflows replaced them. An empty answer is normal, not broken.</li>
+<li>If a client swears they are still emailing people and you cannot find the workflow, check here before you go hunting.</li>
+</ul>
+</div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
 <li>review-your-conversations</li>
@@ -1505,6 +1544,14 @@ Then confirm back to me, one line each, that every post saved as a draft and whi
 <div class="gsec"><h2>Where people go wrong</h2>
 <div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The posts went nowhere.&quot;</td><td>The account connection had expired. Reconnect it in GHL, then the queue drains normally.</td></tr><tr><td>&quot;The captions sound like a robot.&quot;</td><td>Give Claude two real posts from the client and say &quot;write like these&quot;. Voice comes from examples, not adjectives.</td></tr><tr><td>&quot;It posted to the wrong page.&quot;</td><td>Name the exact page or profile in the ask, and check the account list Claude prints first.</td></tr></table></div>
 </div>
+<div class="gsec"><h2>Which accounts are actually connected</h2>
+<p class="gpara">Before scheduling anything, check what the account can post to.</p>
+<div class="prompt"><q>Which social accounts are connected here?</q><button class="copy" type="button">Copy</button></div>
+<ul>
+<li>Connected accounts come back grouped, so you can see at a glance whether the client connected a page, a profile, or nothing at all.</li>
+<li>Scheduling to a platform that was never connected fails quietly at post time, long after you have moved on. Check first on any account you did not connect yourself.</li>
+</ul>
+</div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
 <li>blog-posting</li>
@@ -1790,6 +1837,13 @@ Tell me plainly what happens on my side when somebody clicks it, and what I woul
 <div class="gsec"><h2>Where people go wrong</h2>
 <div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;No reviews came back and I know we have some.&quot;</td><td>Reviews live per sub-account. Confirm which account you are in, then ask again. Reviews also only appear here once the platform they came from is connected under Reputation.</td></tr><tr><td>&quot;It says no reviews, but there are some on our Facebook page.&quot;</td><td>Having a review link for a platform is not the same as having that platform connected. Until it is connected, the reviews stay on Facebook and never reach the account.</td></tr><tr><td>&quot;I want alerts, not to keep asking.&quot;</td><td>Ask for a workflow instead: a review request after every completed appointment, and a notification to you on anything low.</td></tr><tr><td>&quot;The reply Claude wrote sounds defensive.&quot;</td><td>Tell it the tone: short, human, take responsibility, offer to fix it privately. It will rewrite.</td></tr></table></div>
 </div>
+<div class="gsec"><h2>Review links, and where the requests come from</h2>
+<div class="prompt"><q>What is my review link?</q><button class="copy" type="button">Copy</button></div>
+<ul>
+<li>The review link is the URL your request messages point customers at. Read it back before you paste it into a workflow, because a wrong one sends people nowhere and nobody reports it.</li>
+<li>Reviews come back with the rating, the text, the reviewer and the source, so you can answer &quot;what are people actually saying&quot; in one ask rather than reading a dashboard.</li>
+</ul>
+</div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
 <li>weekly-account-report</li>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.65.2",
+  "version": "3.65.3",
   "mcpName": "io.github.drjerryrelth/ghl-command",
   "description": "GoHighLevel MCP Server for Claude. 238 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",