@elitedcs/ghl-mcp 3.74.0 → 3.76.0

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: 2e657aa65ae89172 -->
+<!-- guides-hash: a372a7f6a8ce5823 -->
 <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
@@ -226,7 +226,7 @@ body.app.reading #indexview{display:none}
   <p class="eyebrow">GHL Command</p>
   <h1>What do you want to get done?</h1>
   <p class="sub">Every guide is a job, in plain English: open one, copy a prompt, paste it to Claude. A job is not a button, so one guide usually puts a dozen of GHL Command's tools to work at once. Every prompt marked "Proven live" was run against a real GoHighLevel account before it shipped.</p>
-  <div class="badges"><span class="badge on">30 guides</span><span class="badge">10 categories</span><span class="badge">Updates with the product</span></div>
+  <div class="badges"><span class="badge on">31 guides</span><span class="badge">10 categories</span><span class="badge">Updates with the product</span></div>
 </div></section>
 <div class="shell">
 <main>
@@ -243,7 +243,8 @@ body.app.reading #indexview{display:none}
 <a class="card pub" href="#g-audit-your-workflows" data-k="audit workflows broken silent failure check review existing validate not sending nothing happens"><h3>Audit your workflows</h3><p>Find silent failures and dead ends in existing workflows before your client does.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~2 minutes</span><span class="open">Open guide &#8594;</span></div></a>
 <a class="card pub" href="#g-branch-on-tags-and-fields" data-k="if else branch condition vip tag field split two paths different message"><h3>Branch on tags and fields</h3><p>If they are a VIP, send this. Otherwise, send that. Built correctly the first time.</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-build-nurture-sequence" data-k="nurture sequence drip texts emails follow up workflow build quiet hours sending window contact hours"><h3>Build a nurture sequence</h3><p>A follow-up machine that texts, emails, waits, and stops the second someone replies.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~15 minutes</span><span class="open">Open guide &#8594;</span></div></a>
-<a class="card pub" href="#g-send-data-to-other-apps" data-k="webhook zapier make integromat slack google sheets api send data integration notify push connect n8n other app"><h3>Send GHL data to another app</h3><p>Push contacts into Slack, Sheets, Zapier, Make or your own software the moment something happens in GHL.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~2 minutes</span><span class="open">Open guide &#8594;</span></div></a></div></div>
+<a class="card pub" href="#g-send-data-to-other-apps" data-k="webhook zapier make integromat slack google sheets api send data integration notify push connect n8n other app"><h3>Send GHL data to another app</h3><p>Push contacts into Slack, Sheets, Zapier, Make or your own software the moment something happens in GHL.</p><div class="meta"><span class="pill full">Full license</span><span class="time">~2 minutes</span><span class="open">Open guide &#8594;</span></div></a>
+<a class="card pub" href="#g-workflows-that-will-not-save" data-k="cannot save will not save invalid uuid action validation failed step id legacy snapshot day days wait unit notification recipient 400 rejected edit workflow parked mid-sequence"><h3>When a workflow runs fine but will not save</h3><p>Understand the error that names steps you never touched, and fix it without dropping anyone mid-sequence.</p><div class="meta"><span class="pill free">Free plan</span><span class="time">~3 minutes</span><span class="open">Open guide &#8594;</span></div></a></div></div>
 <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>
@@ -313,6 +314,8 @@ Do not change anything. This is a read.</p></div>
 <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>Creating and deleting sub-accounts is switched off by default, on purpose. It stays off unless you deliberately turn it on.</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>
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
@@ -837,6 +840,7 @@ Do not change any contact, and do not delete any list that is already there.</p>
 <li>Saved lists are built from conditions, not from a frozen set of names. Tag somebody tomorrow and they appear in the list on their own.</li>
 <li>Saving lists needs version 3.65.0 or later. In every version before it, the list tools reported success and quietly created nothing, so if you tried this before and found nothing in GHL, that is why. Ask Claude &quot;what version are you running&quot; if you are not sure.</li>
 <li>Bulk changes need the full license. The Free plan can find and count the group, but not change it.</li>
+<li><b>A bulk update with nothing in it is refused.</b> It used to report every contact as updated while changing nothing at all.</li>
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
@@ -1008,6 +1012,7 @@ When it saves, read the form back to me question by question, and tell me exactl
 <li>Wire the answers to contact fields. That is what lets you tag, segment, and branch on them later.</li>
 <li>Attach the form to a page in a funnel, or send the form link directly. Both work.</li>
 <li>Submissions can be read on the Free plan. Building and changing forms needs the full license.</li>
+<li><b>Reading submissions with no other instruction works from 31 August.</b> It used to fail unless you happened to name a page size, and the error blamed a number you never gave it.</li>
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
@@ -1074,6 +1079,8 @@ Read them back to me afterwards with their exact names and types, and tell me wh
 <li>Renaming a field is safe. Deleting one is not: anything pointing at it goes quiet. If a field is retired, leave it and stop using it.</li>
 <li>Custom objects are for things that are not people. Most accounts never need one, and that is fine.</li>
 <li>Needs the full license. Reading the field list is free.</li>
+<li><b>Deleting a custom field now asks you to confirm.</b> It takes the stored value on every contact with it, which is not something you can undo, and until 31 August it happened from a single instruction with no check.</li>
+<li><b>Searching, editing and deleting custom object records works from 31 August.</b> All three were aimed at addresses GoHighLevel does not answer on, so none of them did anything.</li>
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
@@ -1131,10 +1138,11 @@ Then tell me which ones I should chase, in order.</p></div>
 <li>GHL hands documents over in modest batches, so on a busy account a full read takes a few passes. Claude will say when it is still fetching.</li>
 <li>A document sent to the wrong contact cannot be unsent. Say the full name or the email in the ask.</li>
 <li>Needs the full license.</li>
+<li><b>A contract built from a template is prepared as a draft.</b> It is only sent when you say to send it. Before 31 August it went out to the customer the moment it was created, which is not something you can take back.</li>
 </ul>
 </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;It sent to the wrong Dana.&quot;</td><td>Two contacts, same first name. Give the email address and Claude confirms the match before sending.</td></tr><tr><td>&quot;The template list is missing one.&quot;</td><td>It exists in a different sub-account. Confirm which account you are in first.</td></tr><tr><td>&quot;The client says the document is blank.&quot;</td><td>The template has no signature or content blocks filled in. That is fixed in the GHL template editor, then resent.</td></tr></table></div>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;It sent to the wrong Dana.&quot;</td><td>Two contacts, same first name. Give the email address and Claude confirms the match before sending.</td></tr><tr><td>&quot;The template list is missing one.&quot;</td><td>It exists in a different sub-account. Confirm which account you are in first.</td></tr><tr><td>&quot;The client says the document is blank.&quot;</td><td>The template has no signature or content blocks filled in. That is fixed in the GHL template editor, then resent.</td></tr><tr><td>&quot;I only wanted to see what it would look like, and the client got it.&quot;</td><td>That was the old behaviour and it changed on 31 August. Creating from a template now leaves the contract as a draft, and sending is a separate instruction.</td></tr></table></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
@@ -1286,10 +1294,16 @@ Do not send it. I will send it myself once I have read it.</p></div>
 <li>Coupons need a code, a type (percentage or fixed) and an amount. Without all three GHL rejects it.</li>
 <li>&quot;What was I paid&quot; is a different question from &quot;what did I invoice&quot;. Ask for transactions or orders for money that actually moved, and for invoices for money you asked for.</li>
 <li>Invoicing needs the full license. The Free plan can read invoices and payments but not raise them.</li>
+<li><b>Estimates and quotes work from 31 August.</b> Before that they failed outright, you could not create one, list them, or delete one. If you tried earlier and gave up, try again.</li>
+<li><b>Invoice dates now follow the sub-account's timezone.</b> An invoice raised late in the evening used to be dated the next day, because the date was worked out in UTC.</li>
+<li><b>Deleting or voiding an invoice now asks you to confirm.</b> Voiding asks you to say VOID rather than DELETE, so the word matches what you are actually doing.</li>
+<li><b>Estimate dates are plain calendar dates.</b> Give them as year-month-day. A full timestamp is refused rather than quietly shifted by a day when it is converted back.</li>
+<li><b>Renaming an invoice and sending one both work from 31 August.</b> Neither did before: an edit was rejected outright, and a send was refused for missing details the tool never supplied. If you gave up on either, try again.</li>
+<li><b>Recording a payment is final.</b> Once an invoice has a payment against it, GoHighLevel will not let it be voided or deleted, by us or by anyone. Take the payment when you mean it.</li>
 </ul>
 </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;Creating an invoice used to just fail.&quot;</td><td>It did, for everyone, until 3.65.2. The call was missing six fields GHL requires and crashed its server rather than telling us. Update and it works.</td></tr><tr><td>&quot;It sent before I was ready.&quot;</td><td>Say &quot;do not send it&quot; in the ask. Sending is the only step here that reaches a customer.</td></tr><tr><td>&quot;The invoice shows the wrong name or no email.&quot;</td><td>Those come from the contact record, not the invoice. Fix the contact first, then raise the invoice.</td></tr><tr><td>&quot;My revenue number looks too low.&quot;</td><td>You are reading invoices, which is money requested. Ask for transactions instead, which is money received.</td></tr><tr><td>&quot;The promo code was rejected.&quot;</td><td>A coupon needs all three of code, type and amount. Percentage discounts take a number like 10, not &quot;10%&quot;.</td></tr></table></div>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;Creating an invoice used to just fail.&quot;</td><td>It did, for everyone, until 3.65.2. The call was missing six fields GHL requires and crashed its server rather than telling us. Update and it works.</td></tr><tr><td>&quot;It sent before I was ready.&quot;</td><td>Say &quot;do not send it&quot; in the ask. Sending is the only step here that reaches a customer.</td></tr><tr><td>&quot;The invoice shows the wrong name or no email.&quot;</td><td>Those come from the contact record, not the invoice. Fix the contact first, then raise the invoice.</td></tr><tr><td>&quot;My revenue number looks too low.&quot;</td><td>You are reading invoices, which is money requested. Ask for transactions instead, which is money received.</td></tr><tr><td>&quot;The promo code was rejected.&quot;</td><td>A coupon needs all three of code, type and amount. Percentage discounts take a number like 10, not &quot;10%&quot;.</td></tr><tr><td>&quot;An invoice is dated tomorrow.&quot;</td><td>Fixed on 31 August. Dates are now taken from the sub-account's own timezone rather than UTC. Invoices raised before then may carry the wrong day; check any that were created late in the evening.</td></tr></table></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
@@ -1447,10 +1461,11 @@ Do not reply to anyone. This is a read.</p></div>
 <li>Timezone comes from the sub-account. On a new client account, confirm it once, because everything downstream inherits it.</li>
 <li>Booking, moving, and cancelling appointments need the full license. Reading them is free.</li>
 <li>Appointment totals are deliberately left out of the weekly account report. Ask for them here instead, where the window is explicit.</li>
+<li><b>Booking and moving now insist on knowing which 2pm you mean.</b> If you say &quot;book Dana at 2pm&quot;, Claude works that out against the sub-account's timezone before it books. Until 31 August a bare time was read as UTC, so a 2pm booking could land at 7am.</li>
 </ul>
 </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;The times look an hour off.&quot;</td><td>The sub-account timezone is set to the wrong city. Fix it in GHL once and every reading is right afterwards.</td></tr><tr><td>&quot;It missed an appointment I know about.&quot;</td><td>It is on a calendar you did not name. Ask &quot;list every calendar in this account&quot; and then ask across all of them.</td></tr><tr><td>&quot;I asked for today and got this week.&quot;</td><td>Say the word today on its own. Claude prints the window it used, so you can spot it immediately.</td></tr></table></div>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The times look an hour off.&quot;</td><td>The sub-account timezone is set to the wrong city. Fix it in GHL once and every reading is right afterwards.</td></tr><tr><td>&quot;It missed an appointment I know about.&quot;</td><td>It is on a calendar you did not name. Ask &quot;list every calendar in this account&quot; and then ask across all of them.</td></tr><tr><td>&quot;I asked for today and got this week.&quot;</td><td>Say the word today on its own. Claude prints the window it used, so you can spot it immediately.</td></tr><tr><td>&quot;It says the slot is not available, but the diary is empty.&quot;</td><td>That was usually the time, not the diary. A time with no timezone on it was read as UTC and landed outside opening hours, and GHL reported it as an availability problem. It is now caught and explained before anything is booked. If you still see this, the slot really is outside the calendar's open hours.</td></tr></table></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
@@ -1561,10 +1576,12 @@ Before you send: confirm the exact contact you matched, show me their phone numb
 <li>One-off messages are for one person. For a sequence to many people, build a nurture instead so replies stop it automatically.</li>
 <li>Compliance stays yours. Business hours, opt-out language, and consent are your responsibility, not the tool's.</li>
 <li>Needs the full license.</li>
+<li><b>Every send now tells you whether it actually went.</b> GHL accepting a message is not the same as delivering it: on an account whose text registration is not approved, messages sit queued for ever and nothing looks wrong. You now get told which of those happened.</li>
+<li><b>&quot;Delivered&quot; is the carrier's word, not proof somebody read it.</b> It is right nearly always, and it is not a receipt. For anything that matters, confirm with the person.</li>
 </ul>
 </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;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 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><tr><td>&quot;We texted them and they say they never got it.&quot;</td><td>Check what the send reported. If it says queued, the account's text registration is almost certainly not approved and the message never left. Before 31 August this looked identical to a successful send.</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>
@@ -1686,6 +1703,8 @@ This is a read. Do not apply anything.</p></div>
 <li>Imported snapshots are somebody else's work and can change out from under you. If a template matters to your business, build your own from an account you control.</li>
 <li>Applying a snapshot is an agency-level action. Reading the list works with your agency key; the rollout itself happens in the GHL agency view.</li>
 <li>Needs the full license.</li>
+<li><b>A cloned automation is checked after it is copied.</b> You are told how many steps and triggers actually landed, and whether anything in the copy still points back at the original.</li>
+<li><b>This mattered:</b> until 31 August a cloned automation could still enrol people into the workflow it was copied from. Clone a nurture sequence for a new client and their leads went into the previous client's automation, while the copy reported itself perfect.</li>
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
@@ -1743,6 +1762,8 @@ Then confirm back to me, one line each, that every post saved as a draft and whi
 <li>Images are not written by this. Attach them in the planner, or ask Claude to build an image separately and add it.</li>
 <li>Publishing straight from the chat is possible, and this guide deliberately does not teach it. A misfired post on a client's real page is not a mistake you can quietly fix.</li>
 <li>Needs the full license.</li>
+<li><b>A scheduled post has to say which hour it means.</b> A time with no timezone on it is read as UTC, so a post set for 9am would go out at 2am, publicly, on the client's own accounts, with nothing to undo. Claude now catches that before anything is scheduled.</li>
+<li><b>Asking for scheduled posts now really gives you only scheduled posts.</b> Until 31 August the filter was advertised and never applied, so a request for one queue came back with published and failed posts mixed in.</li>
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
@@ -1807,10 +1828,11 @@ Do not add any contacts or deals to it yet.</p></div>
 <li>Fewer stages is better. Six is plenty. Ten stages means nobody keeps the board clean.</li>
 <li>Keep the pipeline. When stages change, ask Claude to update the pipeline in place. Deleting and recreating gives every stage a new ID, and every workflow that referenced the old ones goes silently dead.</li>
 <li>Needs the full license.</li>
+<li><b>Editing stages is all-or-nothing, and that is now enforced.</b> Sending only the stage you are renaming used to delete every other stage, and the deals sitting in them were cut loose. Claude now refuses that and tells you which stages were at risk.</li>
 </ul>
 </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;I recreated the pipeline and all my automations stopped.&quot;</td><td>Recreating changes every stage ID. Say &quot;update the existing pipeline&quot; instead, and Claude keeps the IDs alive.</td></tr><tr><td>&quot;A workflow that moves deals does nothing.&quot;</td><td>It is pointing at a stage that no longer exists. Run a workflow audit; this is the single most common find.</td></tr><tr><td>&quot;The stage order came out wrong.&quot;</td><td>Say the stages in order in one line and ask for the read-back. The read-back shows you the true order.</td></tr></table></div>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;I recreated the pipeline and all my automations stopped.&quot;</td><td>Recreating changes every stage ID. Say &quot;update the existing pipeline&quot; instead, and Claude keeps the IDs alive.</td></tr><tr><td>&quot;A workflow that moves deals does nothing.&quot;</td><td>It is pointing at a stage that no longer exists. Run a workflow audit; this is the single most common find.</td></tr><tr><td>&quot;The stage order came out wrong.&quot;</td><td>Say the stages in order in one line and ask for the read-back. The read-back shows you the true order.</td></tr><tr><td>&quot;I renamed one stage and the others disappeared.&quot;</td><td>That was possible until 31 August. The stage list replaces the whole board, so anything left out was deleted. It is now refused unless you explicitly say you mean to remove those stages.</td></tr></table></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
@@ -1924,6 +1946,7 @@ Do not move anything. This is a read.</p></div>
 <li>Won and lost are a different thing from stages. A deal can sit in &quot;Treatment Scheduled&quot; and be marked won. Ask for both when you want the true picture.</li>
 <li>If a deal you expect is missing, it may live on a different pipeline in the same account. Ask &quot;which pipelines exist here&quot; first.</li>
 <li>Needs the full license. The Free plan can read the board but not move deals.</li>
+<li><b>Moving a deal to a stage from another pipeline is refused by GHL</b>, and it names the stages that are valid. Checked on 31 August, this one was already safe.</li>
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
@@ -2113,6 +2136,61 @@ Then give me the three things you would look at first if this were your account.
   <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
   </main></div>
 </section>
+
+<section class="gpage" id="g-workflows-that-will-not-save">
+  <div class="hero"><div class="hero-in">
+    <p class="eyebrow">GHL Command User Guide</p>
+    <h1>When a workflow runs fine but will not save</h1>
+    <p class="sub">Understand the error that names steps you never touched, and fix it without dropping anyone mid-sequence.</p>
+    <div class="badges"><span class="badge on">Free plan</span><span class="badge">~3 minutes</span><span class="badge">Automations</span></div>
+  </div></div>
+  <div class="shell"><main class="gview">
+  <a class="back" href="#top">&#8592; All guides</a>
+  <div class="gsec"><h2>What you'll get</h2>
+<ul>
+<li>Plain English for the error that says <code>Action validation failed</code> and then lists steps you did not touch.</li>
+<li>The reason your workflow runs perfectly and still refuses to save.</li>
+<li>What GHL Command does about it automatically, what it refuses to do, and why refusing is the right answer.</li>
+</ul>
+</div>
+<div class="gsec"><h2>The short version</h2>
+<p class="gpara">Your workflow is not broken. It runs. Contacts move through it and messages go out exactly as they should.</p>
+<p class="gpara">What is broken is your ability to <b>edit</b> it. GoHighLevel tightened what it accepts when a workflow is saved, and older workflows store shapes that no longer pass. Change one step, hit save, and GHL rejects the whole thing and names three other steps as the problem. That is why the error looks unrelated to what you just did.</p>
+<p class="gpara">This affects workflows built from older snapshots and templates. On one real account, 20 of 43 workflows were in this state and the account looked completely healthy from inside GHL.</p>
+</div>
+<div class="gsec"><h2>Say this</h2>
+<div class="prompt"><q>Audit my workflows and tell me which ones cannot be saved.</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Why does this workflow fail with &quot;Action validation failed&quot; when I try to edit it?</q><button class="copy" type="button">Copy</button></div>
+<div class="prompt"><q>Is anyone part-way through this workflow right now?</q><button class="copy" type="button">Copy</button></div>
+</div>
+<div class="gsec"><h2>What the audit tells you now</h2>
+<p class="gpara">Run an audit and you may see warnings that did not exist before. They are <b>warnings, not errors</b>, and the difference matters:</p>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>Warning</th><th>What it means</th><th>What to do</th></tr><tr><td>Step id that GHL now rejects</td><td>The workflow <b>runs fine</b>. You cannot edit it until the ids are renewed.</td><td>See &quot;Renewing the ids&quot; below. Do not rush it.</td></tr><tr><td>Singular wait unit (&quot;day&quot; or &quot;minute&quot;)</td><td>Same: runs fine, blocks saving.</td><td>Nothing. This is corrected automatically the next time the workflow is saved.</td></tr><tr><td>Notification with no recipient</td><td>The opposite problem: it <b>saves fine and runs</b>, and quietly notifies nobody.</td><td>Pick a person to notify, or set it to notify everyone.</td></tr><tr><td>Social step with no connected account</td><td>Also runs and quietly does nothing.</td><td>Connect the account in Settings → Integrations.</td></tr></table></div>
+<p class="gpara">Read those two groups carefully, because the advice is opposite. The first two mean *&quot;it works, you just cannot change it.&quot;* The last two mean *&quot;it looks fine and is doing nothing.&quot;*</p>
+</div>
+<div class="gsec"><h2>Renewing the ids, and the one thing that can go wrong</h2>
+<p class="gpara">Fixing the id problem means giving every step a new identifier. Here is the part nobody tells you:</p>
+<p class="gpara"><b>A contact part-way through a workflow is attached to the step they are waiting on.</b> Somebody sitting at &quot;wait 3 days&quot; is held there by that step's id. Renew the id and that contact is dropped out of the sequence, silently and permanently, with no way to put them back. GoHighLevel has no way to place a contact back at step seven.</p>
+<p class="gpara">So GHL Command will not do it while anyone is waiting. If you ask it to change a step that has someone parked on it, it refuses, tells you how many people are affected, and writes nothing.</p>
+<p class="gpara">That is deliberate. A refused edit costs you a wait. A dropped lead costs you the lead.</p>
+<p class="gpara"><b>What it will still do:</b> every other step in that workflow can be edited, renewed, added or removed. You can repair the whole workflow around the person who is waiting.</p>
+<p class="gpara"><b>What counts as &quot;their step&quot;:</b> the step they are standing on, and any step it depends on. Some steps wait on another step rather than containing it: a goal that waits for a particular email to be opened is holding a reference to that email step. Change the email and the person waiting on the goal is affected, even though you never touched the goal. Those steps are protected too.</p>
+<p class="gpara"><b>When to do it:</b> when nobody is mid-sequence. For a nurture, that is usually after the last person has finished it. For a template or a brand-new account, it is safe immediately, because nobody is in it yet.</p>
+</div>
+<div class="gsec"><h2>Good to know</h2>
+<ul>
+<li>Running the workflow is never affected. If you change nothing, nothing breaks. There is no rush.</li>
+<li>A workflow can show enrolments and still have nobody waiting: those are people who have already finished. Only people mid-sequence matter.</li>
+<li>This works fully on the Free plan. Making the repairs needs the full license.</li>
+<li>If a workflow was built from a snapshot or a template, assume it is affected until the audit says otherwise. That is where these come from.</li>
+</ul>
+</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;The error named three steps I never touched, so I assumed I broke something else.&quot;</td><td>You did not. GoHighLevel rejects the whole workflow at once and reports every step it does not like, including the ones you left alone.</td></tr><tr><td>&quot;The audit said 'ok' before, so I thought the account was clean.&quot;</td><td>Older versions could not see this at all. Re-run the audit: these warnings are new.</td></tr><tr><td>&quot;I renewed the ids on a live nurture and people stopped receiving messages.&quot;</td><td>They were dropped at the step they were waiting on. This is exactly why the product now refuses. Check who is waiting before you repair.</td></tr><tr><td>&quot;It refused to let me rename a step.&quot;</td><td>If someone is parked on that step, even a rename is refused. It is cautious on purpose. Wait until they have moved on.</td></tr><tr><td>&quot;I want to force it through anyway.&quot;</td><td>For an EDIT there is no override, and that is intentional. There is no way to put a dropped contact back, so the product will not offer you a button that loses them.</td></tr><tr><td>&quot;I need to delete the whole workflow and people are in it.&quot;</td><td>Deleting is different: you cannot delete a workflow and keep the people inside it, so this one is your call rather than a refusal. The first attempt tells you how many are part-way through; run it again naming that number and it proceeds. Nothing is deleted until you do.</td></tr></table></div>
+</div>
+  <p class="gfoot">Works in Claude Desktop and Claude Code. Stuck? Email support@ghlcommand.com and a human answers.</p>
+  </main></div>
+</section>
 <footer class="foot"><div class="foot-in">
   <span>GHL Command runs your GoHighLevel account from Claude. This guide library ships with every install, free or paid, and grows with the product.</span>
   <a href="https://ghlcommand.com/skills/">Web version</a><a href="https://ghlcommand.com">ghlcommand.com</a>

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.74.0",
+  "version": "3.76.0",
   "mcpName": "io.github.drjerryrelth/ghl-command",
-  "description": "GoHighLevel MCP Server for Claude. 247 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.",
+  "description": "GoHighLevel MCP Server for Claude. 248 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",
   "bin": {
     "ghl-mcp": "dist/index.js"
@@ -10,7 +10,6 @@
   "files": [
     "dist/index.js",
     "dist/capture-helper.js",
-    "dist/assessment.html",
     "templates/action-schemas.json",
     "templates/clinic-medspa.json",
     "templates/trigger-schemas.json",
@@ -28,6 +27,7 @@
     "build": "esbuild src/index.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/index.js --packages=external && esbuild src/capture-helper.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/capture-helper.js --packages=external && node src/command-os/assessment/build-app.mjs && cp src/command-os/assessment/app.html dist/assessment.html",
     "setup": "node setup-wizard.mjs",
     "catalogue": "node scripts/export-command-os-catalogue.mjs",
+    "manifest:write": "node scripts/write-package-manifest.mjs",
     "start": "node dist/index.js",
     "dev": "tsc --watch",
     "test": "vitest run",
@@ -59,7 +59,7 @@
   },
   "bugs": {
     "url": "https://github.com/drjerryrelth/ghl-command-feedback/issues",
-    "email": "support@cliniclaunchlab.com"
+    "email": "support@ghlcommand.com"
   },
   "publishConfig": {
     "access": "public"

package/skills/blueprint/references/copy-guide.md

@@ -1,6 +1,6 @@
 # Copy Guide — every email and text the Blueprint sends
 
-STATUS: v1, 2026-08-26. Owner: Command OS. Read by the build stage before it writes a single template, and by anyone editing a preset.
+STATUS: v1, 2026-08-26. Read by the build stage before it writes a single template, and by anyone editing a preset.
 
 Why this exists, in the owner's words after inspecting a real build: "If we provide everything generic, our users will not be impressed and will not stay with us long." The workflows are only as good as the words inside them. This guide is the standard every message is written to and rewritten to.
 

package/templates/action-schemas.json

@@ -92,7 +92,7 @@
       "convertToMultipath": false,
       "transitions": []
     },
-    "notes": "startAfter.type: 'minutes', 'hour', or 'days' — NOT consistently singular, and 'day' is rejected with 400 INVALID_FIELD_VALUE on a workflow that has a real action before the wait (live-verified 2026-08-29). ALL 5 fields required (type, startAfter, isHybridAction, hybridActionType, transitions). Derived from working GHL UI-built workflows."
+    "notes": "startAfter.type: 'minutes', 'hour', or 'days' \u2014 NOT consistently singular, and 'day' is rejected with 400 INVALID_FIELD_VALUE on a workflow that has a real action before the wait (live-verified 2026-08-29). ALL 5 fields required (type, startAfter, isHybridAction, hybridActionType, transitions). Derived from working GHL UI-built workflows."
   },
   "internal_notification": {
     "example": {
@@ -106,7 +106,7 @@
         "selectedUser": "USER_ID"
       }
     },
-    "notes": "Nested 'notification' object REQUIRED. selectedUser MUST be a real user ID \u2014 GHL now REJECTS an empty string (live-verified 2026-08-06; the old 'empty = all users' behavior is gone). Use get_users to find IDs. EMAIL CHANNEL (verified live 2026-07-20, PWDJ workflow e91f28da): attributes.type is 'email' (NOT 'notification'), nested key is 'email' (NOT 'notification'), body field is 'html' (NOT 'body'), selectedUser is an ARRAY of user IDs, include attachments:[] and isCloned:false. A 'send_email' discriminator inside a 'notification' object saves but silently never sends.",
+    "notes": "Nested 'notification' object REQUIRED. \u26a0\ufe0f READ THE userType FIRST \u2014 the empty-string rule is SCOPED TO IT, and reading it unscoped makes this entry look like it contradicts intake-to-build/executor.ts. It does not. (a) userType:'user' \u2192 selectedUser MUST be a real user ID; an EMPTY STRING IS REJECTED (live-verified 2026-08-06; the old 'empty = all users' behaviour is gone). Use get_users. (b) userType:'all' \u2192 selectedUser:'' is the CORRECT and live-proven placeholder shape, not a defect; executor.ts:660-688 emits it deliberately when no staff member is resolvable yet, and executor.test.ts:1281-1289 pins it. Never flag (b) as missing a recipient. The ONLY broken combination is userType:'user' with a blank selectedUser. Use get_users to find IDs. EMAIL CHANNEL (verified live 2026-07-20, PWDJ workflow e91f28da): attributes.type is 'email' (NOT 'notification'), nested key is 'email' (NOT 'notification'), body field is 'html' (NOT 'body'), selectedUser is an ARRAY of user IDs, include attachments:[] and isCloned:false. A 'send_email' discriminator inside a 'notification' object saves but silently never sends.",
     "emailChannelExample": {
       "type": "email",
       "email": {
@@ -153,19 +153,30 @@
       "type": "task-notification",
       "__customInputs__": {}
     },
-    "notes": "dueDate is days from now as string. assignedTo is a user ID."
+    "notes": "dueDate is days from now as string. assignedTo is a user ID. \u26a0\ufe0f THE TYPE MUST BE HYPHENATED. The underscore form `task_notification` SAVES, VALIDATES and PUBLISHES and is then SILENTLY SKIPPED AT RUNTIME \u2014 no task is ever created and no error is shown anywhere (live-verified 2026-06-12 on the GHL Command sale alert). If you searched this file for `task_notification` and found nothing, that empty result IS the bug: the key here is `task-notification`."
   },
   "assign_user": {
     "example": {
       "type": "assign_user",
-      "user_list": ["USER_ID"],
+      "user_list": [
+        "USER_ID"
+      ],
       "only_unassigned_contact": false,
       "traffic_split": "equally",
-      "traffic_weightage": { "USER_ID": 1 },
-      "traffic_index": [{ "id": "USER_ID", "indexes": [1] }],
+      "traffic_weightage": {
+        "USER_ID": 1
+      },
+      "traffic_index": [
+        {
+          "id": "USER_ID",
+          "indexes": [
+            1
+          ]
+        }
+      ],
       "total_index": 1
     },
-    "notes": "[PROVEN LIVE 2026-08-27 on the MCP Testing sandbox: a scratch workflow carrying both a single-user and a two-user round-robin assign_user node saved, read back with every attribute intact (user_list, only_unassigned_contact, traffic_split, traffic_weightage, traffic_index, total_index) and both real user ids present, and PUBLISHED — GHL's own builder validator accepted it, which is the check that requires a non-empty user_list and verifies each id against the location's users. Scratch workflow deleted; the account was left byte-identical.] 'Assign to user' — the listed users become the contact owner. Linear actions-category node like add_contact_tag. user_list is REQUIRED and non-empty (GHL's builder validator: 'user_list_required'; every id is checked against the location's users — a dead id silently never assigns). Multiple users = round-robin; the equal-split bookkeeping the builder saves is weightage {id:1 each}, traffic_index [{id, indexes:[1..weight]}] with globally sequential indexes, total_index = sum of weights — single user: weightage {id:1}, index [{id, indexes:[1]}], total 1. only_unassigned_contact false always (re)assigns; true skips contacts that already have an owner. traffic_split 'unevenly' + custom weights and customUserList (custom-value mode) exist in the builder but are NOT built by us. LIVE TEST TO CLOSE: build one workflow with this node on a sandbox (MCP Testing), publish, run a test contact through, read back with get_workflow_full + get_contact — confirm the node persists byte-for-byte and the contact's assignedTo/owner becomes USER_ID; then remove this UNVERIFIED label."
+    "notes": "[PROVEN LIVE 2026-08-27 on the MCP Testing sandbox: a scratch workflow carrying both a single-user and a two-user round-robin assign_user node saved, read back with every attribute intact (user_list, only_unassigned_contact, traffic_split, traffic_weightage, traffic_index, total_index) and both real user ids present, and PUBLISHED \u2014 GHL's own builder validator accepted it, which is the check that requires a non-empty user_list and verifies each id against the location's users. Scratch workflow deleted; the account was left byte-identical.] 'Assign to user' \u2014 the listed users become the contact owner. Linear actions-category node like add_contact_tag. user_list is REQUIRED and non-empty (GHL's builder validator: 'user_list_required'; every id is checked against the location's users \u2014 a dead id silently never assigns). Multiple users = round-robin; the equal-split bookkeeping the builder saves is weightage {id:1 each}, traffic_index [{id, indexes:[1..weight]}] with globally sequential indexes, total_index = sum of weights \u2014 single user: weightage {id:1}, index [{id, indexes:[1]}], total 1. only_unassigned_contact false always (re)assigns; true skips contacts that already have an owner. traffic_split 'unevenly' + custom weights and customUserList (custom-value mode) exist in the builder but are NOT built by us. LIVE TEST TO CLOSE: build one workflow with this node on a sandbox (MCP Testing), publish, run a test contact through, read back with get_workflow_full + get_contact \u2014 confirm the node persists byte-for-byte and the contact's assignedTo/owner becomes USER_ID; then remove this UNVERIFIED label."
   },
   "remove_from_workflow": {
     "example": {
@@ -426,5 +437,17 @@
     "nurture_sequence": "Use linear workflow with stopOnResponse:true. Create separate 'exit workflows' triggered by tags (appointment-booked, do-not-contact) that use remove_from_workflow to pull contacts out. Do NOT use inline if/else gates at every step \u2014 this creates too many actions and can freeze GHL.",
     "exit_workflow": "Small 3-4 step workflow: remove_from_workflow \u2192 note \u2192 tag \u2192 notify. Triggered by a tag being added to the contact.",
     "max_actions": "Keep workflows under 40 actions. GHL's UI renderer struggles with larger workflows. Split into multiple connected workflows if needed."
+  },
+  "add_to_workflow": {
+    "example": {
+      "type": "add_to_workflow",
+      "name": "Add to: <Target Workflow Name>",
+      "attributes": {
+        "input_trigger_params": false,
+        "type": "add_to_workflow",
+        "workflow_id": "TARGET_WORKFLOW_ID"
+      }
+    },
+    "notes": "COPIED FROM A LIVE PUBLISHED NODE on a real account (read-only, 2026-09-01) \u2014 not derived from docs. \u26a0\ufe0f THIS IS NOT THE SAME SHAPE AS remove_from_workflow, which is the adjacent action and the easy mistake: remove needs BOTH `workflowId` (camelCase string) AND `workflow_id` (ARRAY). add needs NEITHER \u2014 `workflow_id` is snake_case and a SINGULAR STRING, there is no `workflowId` and no `workflowName`. `input_trigger_params: false` is present in the working node; purpose unknown, carry it. \u26a0\ufe0f KNOWN DIVERGENCE, UNRESOLVED: src/intake-to-build/executor.ts:806 emits the REMOVE shape under the ADD type (camelCase workflowId + workflowName + workflow_id as an ARRAY, no input_trigger_params). Whether GHL accepts and FIRES that variant is [UNVERIFIED] \u2014 a shape that saves and validates is not evidence it runs (cf. task_notification, wait unit \"day\", internal_notification \"inapp\"). Prove it on a sandbox before trusting either form."
   }
-}
+}