@elitedcs/ghl-mcp 3.72.1 → 3.72.2

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: b9bdfc633583b466 -->
+<!-- guides-hash: a47eca1c8dbf1dd3 -->
 <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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.72.1",
+  "version": "3.72.2",
   "mcpName": "io.github.drjerryrelth/ghl-command",
   "description": "GoHighLevel MCP Server for Claude. 247 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",
@@ -15,6 +15,7 @@
     "templates/trigger-schemas.json",
     "templates/external-funnel/cloudflare-worker.js",
     "templates/external-funnel/README.md",
+    "templates/external-funnel/wrangler.toml.example",
     "README.md",
     "CHANGELOG.md",
     "guide",
@@ -25,6 +26,7 @@
   "scripts": {
     "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",
     "setup": "node setup-wizard.mjs",
+    "catalogue": "node scripts/export-command-os-catalogue.mjs",
     "start": "node dist/index.js",
     "dev": "tsc --watch",
     "test": "vitest run",

package/templates/action-schemas.json

@@ -165,7 +165,7 @@
       "traffic_index": [{ "id": "USER_ID", "indexes": [1] }],
       "total_index": 1
     },
-    "notes": "[UNVERIFIED — captured from GHL's builder bundle 2026-08-27 (client-app-automation-workflows.leadconnectorhq.com assets/index-7CgVurIr.js: the assign_user action class + its registry validator), not yet round-tripped live.] '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 — 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."
   },
   "remove_from_workflow": {
     "example": {

package/templates/external-funnel/README.md

@@ -36,8 +36,11 @@ The executor returns what you plug into the Worker config + form:
 ## Deploy (Cloudflare)
 1. `npm i -g wrangler && wrangler login`
 2. `wrangler secret put GHL_PIT`  ← paste your token (secret; never in code/repo)
-3. Set `[vars]` in `wrangler.toml`: `GHL_LOCATION_ID`, `TRIGGER_TAG`,
-   `ALLOWED_ORIGIN` (your funnel domain — locks CORS), optional `RE_ENROLL`.
+3. `cp wrangler.toml.example wrangler.toml`, then fill in the four values it
+   asks for: `GHL_LOCATION_ID`, `TRIGGER_TAG`, `ALLOWED_ORIGIN` (your funnel
+   domain — locks CORS), and optional `RE_ENROLL`. The example file ships beside
+   this README with each value explained and the right/wrong forms of
+   `ALLOWED_ORIGIN` spelled out.
 4. (Optional) Turnstile: add the widget to your form, `wrangler secret put
    TURNSTILE_SECRET`.
 5. `wrangler deploy` → point your form at the Worker URL.

package/templates/external-funnel/wrangler.toml.example

@@ -0,0 +1,40 @@
+# External-Funnel Lead Bridge — Worker config.
+#
+# Copy this file to `wrangler.toml` (same directory as cloudflare-worker.js),
+# fill in the four values below, then `wrangler deploy`.
+#
+#   cp wrangler.toml.example wrangler.toml
+#
+# The GHL token is NOT in here on purpose. It is a secret:
+#   wrangler secret put GHL_PIT
+# Never put a token in this file — wrangler.toml is committed by most people,
+# and a Private Integration token can write to your whole sub-account.
+
+name = "ghl-lead-bridge"          # your Worker's name; becomes <name>.<subdomain>.workers.dev
+main = "cloudflare-worker.js"
+compatibility_date = "2026-01-01"
+
+[vars]
+# The GHL sub-account this bridge writes into. `apply_build_plan` returns it.
+GHL_LOCATION_ID = "PUT_YOUR_LOCATION_ID_HERE"
+
+# The tag that starts your speed-to-lead workflow. `apply_build_plan` returns it.
+TRIGGER_TAG = "PUT_YOUR_TRIGGER_TAG_HERE"
+
+# Your funnel's exact origin — scheme + host, no trailing slash, no path.
+# This locks CORS. The Worker refuses to start without it and never falls back
+# to "*", so a stranger's page cannot post leads into your account.
+#   right: "https://clinic.example.com"
+#   wrong: "https://clinic.example.com/"  |  "clinic.example.com"  |  "*"
+ALLOWED_ORIGIN = "https://PUT_YOUR_FUNNEL_DOMAIN_HERE"
+
+# Optional. "true" removes and re-adds the trigger tag so a returning lead
+# re-enters the workflow. Leave "false" if a second submission should not
+# restart the sequence.
+RE_ENROLL = "false"
+
+# ── Optional: Turnstile (bot protection on your form) ─────────────────
+# The Worker checks Turnstile ONLY when TURNSTILE_SECRET is set, so this is
+# entirely opt-in. Add the widget to your form, then:
+#   wrangler secret put TURNSTILE_SECRET
+# Nothing to add here — it is a secret, not a var.