@elitedcs/ghl-mcp 3.1.1 → 3.3.0

package/CHANGELOG.md

@@ -1,5 +1,71 @@
 # Changelog
 
+## 3.3.0 — 100% native trigger coverage
+
+**173 tools across 36 modules. Bundle: 255.4 KB.**
+
+All **57 of 57** native GHL workflow trigger types now have their own typed Zod variant in `WorkflowTriggerSchema`. Claude can discriminate every trigger type by name and read documented field paths where the catalogue captured them.
+
+Field-documentation completeness (per trigger, marked in the schema's `.describe()` so the LLM knows):
+
+- **42 fully documented** — every filter field path captured (e.g., `contact_changed` with 12 fields, `opportunity_decay` with 9, `survey_submission`, `birthday_reminder`, etc.)
+- **4 partial** — some fields captured, others not: `custom_date_reminder`, `inbound_trigger`, `facebook_comment_on_post`, `ig_comment_on_post`. Reads still pass; LLM is told docs are partial.
+- **2 fieldless by design** — `inbound_webhook`, `payment_received` (fire on any event)
+- **9 uncaptured** — typed-but-no-docs: `affiliate_created`, `scheduler_trigger`, `user_log_in`, `order_submission`, `conv_ai_trigger`, `conv_ai_autonomous_trigger`, `custom_object_created`, `custom_object_changed`, `facebook_lead_gen`. Most rarely used. Type discrimination still works; field paths to be backfilled when buyers need them.
+
+### Backfills
+- The 4 originally-typed triggers (contact_tag, appointment, customer_reply, pipeline_stage_updated) had incomplete field lists in v3.2.0. Now enriched with all captured fields. `customer_reply` went from "no fields documented" to `workflow.id, message.type, message.body, contact.tags`.
+
+### Coverage delta
+| State | Typed | Reachable-but-untyped | Total |
+|---|---:|---:|---:|
+| Before v3.1.0 | 4 | 0 (reads crashed) | 57 |
+| v3.1.0 | 4 | 53 | 57 |
+| v3.2.0 | 13 | 44 | 57 |
+| **v3.3.0** | **57** | **0** | **57** |
+
+### Future-proof
+Even though every native trigger has a typed variant now, `UnknownTriggerSchema` is still in the union as the last fallback — if GHL ships a new trigger type, reads will pass through cleanly instead of throwing.
+
+### Verified
+- 57 / 57 typed variants matched their own type literal via runtime z.union parse test
+- A synthetic "future_trigger_ghl_invents" type still passes through via the fallback
+- Build: 255.4 KB (up from 248.4 KB; +7 KB for the 44 new variants)
+
+### Files changed
+- `src/trigger-schemas.ts` — all 57 typed variants + 4 doc-completeness statuses (`documented`, `partial`, `fieldless`, `uncaptured`) so the LLM's expectations match each trigger's reality.
+
+## 3.2.0 — Deep trigger typing
+
+**173 tools across 36 modules. Bundle: 248.4 KB.**
+
+v3.1.0 made all 57 native trigger types READ cleanly via a permissive fallback. v3.2.0 deeply types 9 more of the most common ones — `form_submission`, `opportunity_created`, `opportunity_changed`, `opportunity_status_changed`, `payment_received`, `inbound_webhook`, `mailgun_email_event`, `note_add`, `task_added` — bringing typed coverage from **4 / 57 (7%) to 13 / 57 (23%)**.
+
+For Claude that means: when you ask it to read, build, or edit a workflow using one of these triggers, it now knows the discriminated trigger type AND the field paths each one supports (e.g., `opportunity.pipelineId`, `opportunity.monetaryValue`, `form.id`, `mailgun.event`, etc.). Less guessing, fewer rejected payloads.
+
+### Shared trigger-schema module
+- `src/trigger-schemas.ts` (NEW): single source of truth for `WorkflowTriggerSchema`. Both the read path (`workflow-builder-client.ts`) and the write path (`tools/workflow-builder.ts`) now import from this module instead of duplicating definitions.
+- Bundle shrank from 249.7 KB → 248.4 KB thanks to the dedup.
+
+### Field paths documented per trigger
+- Each typed trigger's `field` is `z.string()` with a `.describe()` listing the known field paths (extracted from `templates/trigger-schemas.json`, captured 2026-05-14). Permissive enough that new GHL fields don't crash reads, structured enough that the LLM knows what fields exist.
+
+### Coverage delta
+| State | Typed | Reachable-but-untyped | Total |
+|---|---:|---:|---:|
+| Before v3.1.0 | 4 | 0 (reads crashed) | 57 |
+| v3.1.0 | 4 | 53 | 57 |
+| v3.2.0 | **13** | **44** | 57 |
+
+### Round-trip verified
+- Real `form_submission` workflow from QA Test Clinic v3 parses cleanly through the new typed variant.
+- 8 synthetic typed-trigger samples match their respective variants and are correctly rejected by sibling variants (discrimination works as expected).
+
+### Files changed
+- `src/trigger-schemas.ts` — NEW: 13 typed trigger variants + `UnknownTriggerSchema` fallback in a single module.
+- `src/workflow-builder-client.ts` — removed inline trigger schemas, imports from shared module.
+- `src/tools/workflow-builder.ts` — removed inline trigger schemas, imports from shared module.
+
 ## 3.1.1 — Auto-update visibility
 
 **173 tools across 36 modules. Bundle: 249.7 KB.**

package/README.md

@@ -350,7 +350,7 @@ Re-run setup_ghl_mcp with workflow builder:
 
 **Supported action types:** `sms`, `email`, `add_contact_tag`, `remove_contact_tag`, `update_contact_field`, `wait`, `if_else`, `webhook`, `create_opportunity`, `custom_code`, `add_notes`, `internal_notification`, `task-notification`, `remove_from_workflow`, and more.
 
-**Supported trigger types:** All 57 native GHL trigger types read cleanly (form_submission, payment_received, opportunity_created/changed/status_changed, inbound_webhook, contact_tag, appointment, customer_reply, and 50 more). 4 are deeply typed; the rest pass through a permissive schema so workflows never fail to read regardless of trigger type. Plus 434 marketplace trigger entries across 85 third-party apps — query them via `get_trigger_registry`.
+**Supported trigger types:** **All 57 native GHL trigger types are deeply typed** with their own Zod variant. 42 have full field-path documentation (`opportunity_*`, `form_submission`, `contact_changed`, `survey_submission`, `birthday_reminder`, `mailgun_email_event`, and 36 others). 4 have partial docs, 2 are fieldless by design, 9 have type-only discrimination pending field-path capture. A permissive fallback handles any future trigger types GHL ships, so reads never crash. Plus 434 marketplace trigger entries across 85 third-party apps — query them via `get_trigger_registry`.
 
 ### Pipeline Builder (5 tools) — Internal API