@elitedcs/ghl-mcp 3.45.0 → 3.47.0

package/CHANGELOG.md

@@ -1,5 +1,67 @@
 # Changelog
 
+## 3.47.0 — Blueprint Cap-0: cross-workflow exit chaining + native trigger builders
+
+Two foundational executor fixes so `apply_build_plan` builds workflows that actually
+chain together AND actually fire — the prerequisites for a non-hollow account build.
+
+- **Fixed: a cross-workflow `remove_from_workflow` / `add_to_workflow` halted the build.**
+  When one workflow's exit action targeted another workflow in the SAME plan, execute
+  halted, reporting the (already-built) target as unresolved — so the canonical "pull the
+  lead out of nurture when they book / reply" pattern (workflows that enrol each other)
+  could not fully execute. The executor now resolves EVERY workflow's identity in a first
+  pass (never-clobber bind existing, else create an empty DRAFT) before expanding any
+  actions, so forward, backward, AND mutual cross-workflow references all resolve. Safety
+  rails intact and hardened: never-clobber (existing workflows are never modified),
+  empty-orphan detection (now halts rather than blind-binds when an existing workflow's
+  action count is unreadable), verify-after, and rollback of every unsaved shell on a halt
+  — with any orphan id that could not be deleted SURFACED in the halt message (never
+  swallowed) and dropped from the returned id map.
+- **New: native trigger builders for the trigger types real accounts actually use.**
+  Previously only `contact_tag` triggers were auto-built; every other workflow shipped
+  trigger-less (inactive) — the #1 reason builds were hollow. Blueprint now builds
+  `form_submission`, `appointment` (status-conditioned, e.g. confirmed / no-show),
+  `customer_reply`, `pipeline_stage_updated`, `inbound_webhook`, and `payment_received`
+  triggers natively. Each saved shape was CAPTURED from a real, live, UI-built trigger in a
+  reference account (not guessed) so the synthesized trigger reads back identical and fires.
+  Refs in trigger conditions (form / pipeline / stage) resolve to real GHL ids at build
+  time. A trigger type Blueprint doesn't yet build natively — or one missing the field it
+  needs (e.g. an `appointment` trigger with no status) — is still surfaced as a manual step.
+- Plan validation now rejects two workflows that share a name (the executor binds workflows
+  by name, so duplicates would collapse onto one shell).
+
+## 3.46.0 — `verify_funnel`: prove a funnel actually captures leads (+ external-funnel wiring bundle)
+
+The live-runtime companion to `audit_workflows`. `audit_workflows` finds dead workflow
+steps (static); **`verify_funnel`** proves a public funnel actually **captures** a lead AND
+the machine **acts** on it — because the UI is never proof. (Motivated by two real failures
+from the field: a funnel whose thank-you page showed while every lead silently evaporated,
+and a handler that wrote guessed field keys so values were dropped on save.)
+
+- **New tool `verify_funnel`.** Submits a clearly-marked sentinel lead to the live funnel
+  URL, then reads GHL back to verify what REALLY happened:
+  - **Backend truth** — the contact is actually created (`search_contacts`), with submit→appear latency.
+  - **Field-value fidelity** — each expected field PERSISTED with the exact submitted value
+    (a wrong field id makes upsert succeed while silently dropping the value).
+  - **Trigger tag landed**, else the speed-to-lead workflow can't fire.
+  - **SMS/A2P pre-check** — flags an account with no SMS-capable number (any SMS step would silently fail).
+  - **Workflow status** — flags a DRAFT workflow (never fires on real leads).
+  - **Outreach fired** — an outbound message was actually logged (proves enrollment + send, not a green log).
+  - **Consent recorded** when messaging fires (TCPA/CAN-SPAM).
+  - **Duplicate-contact dedup** + **concurrent double-submit race** (lag-stable polling, no false-pass).
+  - **Routing/opportunity/attribution** (optional) and **multi-surface** (extra URLs).
+  - Booking can't be faked server-side → surfaced as a manual "book one real appointment" step.
+  - Safety: creates a real (clearly-marked `blueprint-qa`) contact and may fire real automation;
+    cleans the sentinel(s) up afterward by default (cleanup runs even on error), with a verdict
+    that turns any failed assertion into an overall FAIL (no silent skips).
+- **`apply_build_plan` execute now returns an `externalWiring` bundle.** For each
+  `target:"external"` funnel: the location id, the **verified GHL custom-field ids** the
+  external form must send (never name-guessed keys), the booking URL, and the contact-tag
+  trigger to add — with an `unresolved` list for anything not yet built. This is what you
+  template into the self-hosted lead bridge (`templates/external-funnel/`).
+- External-funnel README hardened: the contactless-inbound-webhook rationale (why the bridge
+  uses `/contacts/upsert`, not a raw trigger) + a "verify after deploy" QA checklist.
+
 ## 3.35.0 — `create_social_post` is now draft-first (closes the silent "everything published at once" trap)
 
 **Behavior change.** `create_social_post` no longer defers go-live to GoHighLevel's

package/README.md

@@ -1,6 +1,6 @@
 # GHL Command — GoHighLevel MCP Server
 
-**Full GoHighLevel API access for Claude.** 219 tools across 43 modules — manage contacts, conversations, pipelines, calendars, funnels, workflows, invoices, custom objects, webhooks, and more. **Includes full workflow builder, funnel/page editor, form builder, pipeline builder, bulk operations, account export, and workflow cloning** — capabilities no other GHL tool offers. **Multi-tenant:** one install can run the workflow builder across multiple clients' GHL accounts.
+**Full GoHighLevel API access for Claude.** 220 tools across 43 modules — manage contacts, conversations, pipelines, calendars, funnels, workflows, invoices, custom objects, webhooks, and more. **Includes full workflow builder, funnel/page editor, form builder, pipeline builder, bulk operations, account export, and workflow cloning** — capabilities no other GHL tool offers. **Multi-tenant:** one install can run the workflow builder across multiple clients' GHL accounts.
 
 **Distributed via npm as [`@elitedcs/ghl-mcp`](https://www.npmjs.com/package/@elitedcs/ghl-mcp).** Buyers install with one config block — no git, no Node.js setup, no terminal commands. Updates flow automatically (`npx @latest` re-resolves on every Claude restart).
 
@@ -116,7 +116,7 @@ Run setup_ghl_mcp to activate GHL Command:
   ghl_location_id: YOUR_LOCATION_ID
 ```
 
-Approve the tool call. Server validates your license, verifies your GHL credentials, writes them to a per-user config file. **Quit Claude one more time and reopen** — the full core toolset is now unlocked (219 tools total with the optional Workflow Builder Firebase add-on).
+Approve the tool call. Server validates your license, verifies your GHL credentials, writes them to a per-user config file. **Quit Claude one more time and reopen** — the full core toolset is now unlocked (220 tools total with the optional Workflow Builder Firebase add-on).
 
 ### 4. Try it
 
@@ -734,7 +734,7 @@ Source repo is private. Contributors need an invitation from `drjerryrelth`. The
 
 ### Reducing context / token usage
 
-Every registered MCP tool's schema is shipped to the model on every message. With 219 tools that's a meaningful per-message context cost even in chats that never touch GHL. If you only use a slice of GHL Command, restrict the tool surface with `GHL_ENABLED_MODULES` and/or `GHL_ENABLED_TOOLS`:
+Every registered MCP tool's schema is shipped to the model on every message. With 220 tools that's a meaningful per-message context cost even in chats that never touch GHL. If you only use a slice of GHL Command, restrict the tool surface with `GHL_ENABLED_MODULES` and/or `GHL_ENABLED_TOOLS`:
 
 ```jsonc
 // Claude Desktop config — enable whole modules