@elitedcs/ghl-mcp 3.29.0 → 3.30.0

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## 3.30.0 — Workflow trigger stays active after edit/publish (Bug 7)
+
+Editing a trigger on a published workflow via `update_workflow_actions` silently
+disabled it (`active` flipped to `false`), and there was no MCP path to turn it
+back on. Any contract/tag/form trigger you edited stopped firing.
+
+**Root cause.** The internal trigger-write helper hardcoded `status: "draft"` on
+every trigger POST/PUT. GHL derives a trigger's stored `active` flag from that
+write-time `status`. Verified live against the sandbox:
+
+- `status:"published"` → `active:true`
+- `status:"draft"` → `active:false` (and so do `"active"`, `"live"`, and
+  omitting `status` entirely)
+
+So every trigger edit re-drafted the trigger, and nothing flipped it back —
+`publish_workflow` didn't either, because it sent no triggers at all.
+
+**Fix.** Trigger writes now mirror the workflow's own published/draft state:
+
+- `update_workflow_actions` on a published workflow writes its triggers as
+  `published`, so editing a trigger condition keeps it live.
+- `publish_workflow` now re-syncs the workflow's triggers, so a draft →
+  published transition (including the documented create → add-trigger →
+  publish flow) activates them.
+
+Action-chain linking and the workflow-setting preservation from 3.29.0 are
+unchanged.
+
 ## 3.29.0 — Documents & Contracts API fix + workflow/contact bug fixes
 
 Five confirmed bugs fixed, verified live against the GHL API.

package/dist/index.js

@@ -31,7 +31,7 @@ var require_package = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "@elitedcs/ghl-mcp",
-      version: "3.29.0",
+      version: "3.30.0",
       mcpName: "io.github.drjerryrelth/ghl-command",
       description: "GoHighLevel MCP Server for Claude. 212 tools \u2014 full CRM, automation, marketing control, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
       main: "dist/index.js",
@@ -1636,8 +1636,9 @@ ${errorBody}`
    */
   async updateWorkflow(workflowId, updates) {
     const current = await this.getWorkflow(workflowId);
+    const effectiveStatus = updates.status ?? current.status;
     if (updates.triggers !== void 0) {
-      await this.syncTriggers(workflowId, current.triggers || [], updates.triggers);
+      await this.syncTriggers(workflowId, current.triggers || [], updates.triggers, effectiveStatus);
     }
     const currentActions = current.workflowData?.templates || [];
     const newActions = updates.actions ?? currentActions;
@@ -1649,7 +1650,7 @@ ${errorBody}`
     const body = {
       name: updates.name ?? current.name,
       isRestoreRequest: true,
-      status: updates.status ?? current.status,
+      status: effectiveStatus,
       version: current.version,
       dataVersion: current.dataVersion ?? 1,
       timezone: current.timezone ?? "account",
@@ -1682,16 +1683,30 @@ ${errorBody}`
     return this.request("DELETE", `/${this.locationId}/${workflowId}`);
   }
   /**
-   * Publish a draft workflow
+   * Publish a draft workflow.
+   *
+   * Publishing must also re-activate the workflow's triggers. GHL stores a
+   * trigger's `active` flag based on the write-time `status`, so triggers
+   * created/edited while the workflow was a draft are written as "draft"
+   * (active:false). Re-syncing them here under the now-"published" status
+   * flips them live — otherwise a freshly published workflow's triggers never
+   * fire (and the create → update_workflow_actions → publish_workflow flow
+   * would leave new triggers inactive).
    */
   async publishWorkflow(workflowId) {
-    return this.updateWorkflow(workflowId, { status: "published" });
+    const current = await this.getWorkflow(workflowId);
+    return this.updateWorkflow(workflowId, {
+      status: "published",
+      triggers: current.triggers ?? []
+    });
   }
   /**
    * Create a workflow trigger. GHL generates the Firestore id and returns it.
+   * `workflowStatus` is the owning workflow's published/draft state; it
+   * determines whether the new trigger is written live or as a draft.
    */
-  async createTrigger(workflowId, trigger) {
-    const payload = this.buildTriggerPayload(workflowId, trigger);
+  async createTrigger(workflowId, trigger, workflowStatus) {
+    const payload = this.buildTriggerPayload(workflowId, trigger, workflowStatus);
     const raw = await this.request("POST", `/${this.locationId}/trigger`, payload);
     if (isRecord(raw) && typeof raw.id === "string") {
       return raw.id;
@@ -1699,10 +1714,11 @@ ${errorBody}`
     throw new Error(`Trigger creation did not return an id. Response: ${JSON.stringify(raw)}`);
   }
   /**
-   * Update an existing workflow trigger.
+   * Update an existing workflow trigger. `workflowStatus` is the owning
+   * workflow's published/draft state (see buildTriggerPayload).
    */
-  async updateTrigger(workflowId, trigger) {
-    const payload = this.buildTriggerPayload(workflowId, trigger);
+  async updateTrigger(workflowId, trigger, workflowStatus) {
+    const payload = this.buildTriggerPayload(workflowId, trigger, workflowStatus);
     return this.request("PUT", `/${this.locationId}/trigger/${trigger.id}`, payload);
   }
   /**
@@ -1716,7 +1732,7 @@ ${errorBody}`
    * Triggers without an id are created; triggers present in current but
    * missing from desired are deleted; triggers in both are updated in place.
    */
-  async syncTriggers(workflowId, current, desired) {
+  async syncTriggers(workflowId, current, desired, workflowStatus) {
     const currentById = /* @__PURE__ */ new Map();
     for (const t of current) {
       if (typeof t.id === "string") currentById.set(t.id, t);
@@ -1732,9 +1748,9 @@ ${errorBody}`
     }
     for (const trigger of desired) {
       if (hasTriggerId(trigger) && currentById.has(trigger.id)) {
-        await this.updateTrigger(workflowId, trigger);
+        await this.updateTrigger(workflowId, trigger, workflowStatus);
       } else {
-        await this.createTrigger(workflowId, trigger);
+        await this.createTrigger(workflowId, trigger, workflowStatus);
       }
     }
   }
@@ -1742,7 +1758,8 @@ ${errorBody}`
    * Shape a trigger for the POST/PUT trigger endpoints, matching what the
    * GHL UI sends. Missing fields are filled from the client's context.
    */
-  buildTriggerPayload(workflowId, trigger) {
+  buildTriggerPayload(workflowId, trigger, workflowStatus) {
+    const isPublished = workflowStatus === "published";
     return {
       ...trigger,
       workflowId,
@@ -1752,8 +1769,8 @@ ${errorBody}`
       belongs_to: "workflow",
       actions: trigger.actions ?? [{ workflow_id: workflowId, type: "add_to_workflow" }],
       schedule_config: trigger.schedule_config ?? {},
-      active: trigger.active ?? true,
-      status: "draft"
+      active: isPublished,
+      status: isPublished ? "published" : "draft"
     };
   }
   /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.29.0",
+  "version": "3.30.0",
   "mcpName": "io.github.drjerryrelth/ghl-command",
   "description": "GoHighLevel MCP Server for Claude. 212 tools — full CRM, automation, marketing control, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
   "main": "dist/index.js",