@elitedcs/ghl-mcp 3.62.0 → 3.62.1

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## 3.62.1 — update_pipeline works again (Bug 8)
+
+- **Fix: `update_pipeline` no longer 422s.** GHL's pipeline PUT rejects unknown
+  body properties, and the request body was seeded with `locationId` — so every
+  update died with "property locationId should not exist" before the stages were
+  read. locationId now rides as a query parameter (the same pattern
+  `delete_pipeline` already used). Live-proven on the sandbox with the case that
+  matters: existing stage IDs survive the update (rename + reorder + append in
+  one call), so open opportunities are never orphaned. New regression proof:
+  `scripts/pipeline-update-proof.mjs`.
+- Trigger reference: `custom_date_reminder` real UI-generated shape captured
+  (conditions + custom_date_reminder_config; before-days variant — after-days
+  still unverified).
+- Action reference: the workflow Email action has NO "to" field — it always
+  mails the enrolled contact; third parties are copied via `cc` (merge fields
+  supported). Documented so nobody builds a "send to a third party" node that
+  silently mails the contact.
+
+
 ## 3.62.0 — The user guide ships inside the product
 
 - **New tool `get_user_guide`** (free tier included): opens the full GHL Command

package/dist/index.js

@@ -2854,7 +2854,7 @@ var require_package = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "@elitedcs/ghl-mcp",
-      version: "3.62.0",
+      version: "3.62.1",
       mcpName: "io.github.drjerryrelth/ghl-command",
       description: "GoHighLevel MCP Server for Claude. 235 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.",
       main: "dist/index.js",
@@ -12486,7 +12486,7 @@ ${text2}`);
     },
     async ({ pipelineId }) => {
       try {
-        const result = await pipelineRequest("GET", `/${pipelineId}?locationId=${client.locationId}`);
+        const result = await pipelineRequest("GET", `/${encodeURIComponent(pipelineId)}?locationId=${client.locationId}`);
         return {
           content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
         };
@@ -12556,12 +12556,12 @@ ${text2}`);
     },
     async ({ pipelineId, name, stages, showInFunnel, showInPieChart }) => {
       try {
-        const body = { locationId: client.locationId };
+        const body = {};
         if (name !== void 0) body.name = name;
         if (stages !== void 0) body.stages = stages;
         if (showInFunnel !== void 0) body.showInFunnel = showInFunnel;
         if (showInPieChart !== void 0) body.showInPieChart = showInPieChart;
-        const result = await pipelineRequest("PUT", `/${pipelineId}`, body);
+        const result = await pipelineRequest("PUT", `/${encodeURIComponent(pipelineId)}?locationId=${client.locationId}`, body);
         return {
           content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
         };
@@ -12580,7 +12580,7 @@ ${text2}`);
     },
     async ({ pipelineId }) => {
       try {
-        const result = await pipelineRequest("DELETE", `/${pipelineId}?locationId=${client.locationId}`);
+        const result = await pipelineRequest("DELETE", `/${encodeURIComponent(pipelineId)}?locationId=${client.locationId}`);
         return {
           content: [{ type: "text", text: JSON.stringify(result, null, 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: 95cbfe7f949954d7 -->
+<!-- guides-hash: d9c9fd6db916ddcf -->
 <style>
 :root{
   --bg:#F2F4F6; --surface:#FFFFFF; --ink:#1C2833; --muted:#5B6B78; --line:#DDE3E8;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.62.0",
+  "version": "3.62.1",
   "mcpName": "io.github.drjerryrelth/ghl-command",
   "description": "GoHighLevel MCP Server for Claude. 235 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",

package/templates/action-schemas.json

@@ -17,21 +17,22 @@
     "Keep workflows under 40 actions to avoid GHL UI renderer freezes",
     "Use separate exit workflows instead of inline if/else branching for nurture sequences"
   ],
-
   "add_contact_tag": {
     "example": {
-      "tags": ["tag-name-here"]
+      "tags": [
+        "tag-name-here"
+      ]
     },
     "notes": "Use 'tags' ARRAY, NOT 'tagName' string. Tag must exist in the location."
   },
-
   "remove_contact_tag": {
     "example": {
-      "tags": ["tag-to-remove"]
+      "tags": [
+        "tag-to-remove"
+      ]
     },
     "notes": "Same format as add_contact_tag but action type is 'remove_contact_tag'."
   },
-
   "sms": {
     "example": {
       "body": "Hi {{contact.first_name}}, your message here.",
@@ -39,7 +40,6 @@
     },
     "notes": "Body supports GHL merge fields. 'attachments' is REQUIRED even if empty array."
   },
-
   "email": {
     "example": {
       "subject": "Your Subject Line",
@@ -48,15 +48,19 @@
         "hasTrackingLinks": false,
         "hasUtmTracking": false,
         "hasTags": false
-      }
+      },
+      "cc": "{{contact.sales_rep_email}}"
     },
-    "notes": "Use 'html' NOT 'body'. Content MUST be HTML with <p> tags. Subject supports merge fields. trackingOptions is REQUIRED."
+    "notes": "Use 'html' NOT 'body'. Content MUST be HTML with <p> tags. Subject supports merge fields. trackingOptions is REQUIRED. RECIPIENT: there is NO 'to' field — the email action ALWAYS sends to the enrolled contact (UI reads 'Send an email to the contact'). To copy a third party use attributes.cc (plain string, accepts merge fields e.g. {{contact.sales_rep_email}}); 'bcc' presumably mirrors it but is NOT live-verified. Never build a 'send to a third party' node expecting a To field — it silently mails the contact instead. (cc shape live-captured 2026-08-08, CLL.)"
   },
-
   "wait": {
     "example_1hour": {
       "type": "time",
-      "startAfter": { "type": "hour", "value": 1, "when": "after" },
+      "startAfter": {
+        "type": "hour",
+        "value": 1,
+        "when": "after"
+      },
       "name": "Wait",
       "isHybridAction": true,
       "hybridActionType": "wait",
@@ -65,7 +69,11 @@
     },
     "example_30min": {
       "type": "time",
-      "startAfter": { "type": "minutes", "value": 30, "when": "after" },
+      "startAfter": {
+        "type": "minutes",
+        "value": 30,
+        "when": "after"
+      },
       "name": "Wait",
       "isHybridAction": true,
       "hybridActionType": "wait",
@@ -74,7 +82,11 @@
     },
     "example_3days": {
       "type": "time",
-      "startAfter": { "type": "day", "value": 3, "when": "after" },
+      "startAfter": {
+        "type": "day",
+        "value": 3,
+        "when": "after"
+      },
       "name": "Wait",
       "isHybridAction": true,
       "hybridActionType": "wait",
@@ -83,7 +95,6 @@
     },
     "notes": "startAfter.type: 'minutes', 'hour', or 'day'. ALL 5 fields required (type, startAfter, isHybridAction, hybridActionType, transitions). Derived from working GHL UI-built workflows."
   },
-
   "internal_notification": {
     "example": {
       "type": "notification",
@@ -98,7 +109,6 @@
     },
     "notes": "Nested 'notification' object REQUIRED. selectedUser empty string for all users, or specific user ID."
   },
-
   "update_contact_field": {
     "example": {
       "type": "update_contact_field",
@@ -115,7 +125,6 @@
     },
     "notes": "'field' is the custom field ID, not the name. Use get_custom_fields to find IDs."
   },
-
   "add_notes": {
     "example": {
       "html": "<p style=\"padding-left: 0px!important;\">Note content here.</p>",
@@ -123,7 +132,6 @@
     },
     "notes": "Content MUST be HTML."
   },
-
   "task-notification": {
     "example": {
       "assignedTo": "USER_ID",
@@ -135,17 +143,17 @@
     },
     "notes": "dueDate is days from now as string. assignedTo is a user ID."
   },
-
   "remove_from_workflow": {
     "example": {
       "workflowId": "TARGET_WORKFLOW_ID",
       "workflowName": "Target Workflow Name",
       "type": "remove_from_workflow",
-      "workflow_id": ["TARGET_WORKFLOW_ID"]
+      "workflow_id": [
+        "TARGET_WORKFLOW_ID"
+      ]
     },
     "notes": "Requires BOTH workflowId (string) AND workflow_id (ARRAY with same ID). Also needs type: 'remove_from_workflow' inside attributes. Derived from GHL UI."
   },
-
   "internal_update_opportunity": {
     "example": {
       "__customInputFields__": [
@@ -167,14 +175,16 @@
     },
     "notes": "CREATABLE from scratch (re-enabled v3.41.0). The discriminator workflowsActionType:'INTERNAL' MUST sit at the NODE level, never nested in attributes — a nested copy makes GHL reject the node as 'action has a corrupted type' and silently fail the whole save. update_workflow_actions normalizes this for you (hoists workflowsActionType to the node level, scaffolds allowBackward + __customInputs__, gives each __customInputFields__ entry an __customInputs__). The shape below (workflowsActionType at the node level alongside type/name/attributes) is correct for both creating and round-tripping. Use pipeline and stage IDs (not names) — get_pipelines / list_pipelines_full to find them FIRST. CRITICAL: if the pipelineId or pipelineStageId don't exist in the target sub-account, GHL silently fails this action AND can kill subsequent actions. A synthesized node needs BOTH a pipelineId and a pipelineStageId entry; a node round-tripped via get_workflow_full keeps its id and passes through unchanged."
   },
-
   "_if_else_branching": {
     "notes": "if_else is a node type discriminator only. Do not send a single flat if_else action.",
     "condition_node": {
       "type": "if_else",
       "cat": "conditions",
       "nodeType": "condition-node",
-      "next": ["YES_BRANCH_ID", "NO_BRANCH_ID"],
+      "next": [
+        "YES_BRANCH_ID",
+        "NO_BRANCH_ID"
+      ],
       "attributes": {
         "currentRecipeType": "HAS_TAG",
         "operator": "and",
@@ -182,26 +192,34 @@
         "conditionName": "HAS_TAG",
         "version": 2,
         "noneBranchName": "None",
-        "branches": [{
-          "id": "YES_BRANCH_ID",
-          "name": "Branch name",
-          "segments": [{
-            "__segmentId": "SEGMENT_UUID",
-            "operator": "and",
-            "conditions": [{
-              "conditionType": "contact_detail",
-              "conditionSubType": "tags",
-              "conditionOperator": "index-of-true",
-              "conditionValue": ["tag-to-check"],
-              "__conditionId": "CONDITION_UUID",
-              "__customFieldType__": "standard",
-              "nestedDropdownTypes": [],
-              "allowIsOperatorTypes": [],
-              "ifElseNodeId": "CONDITION_NODE_ID",
-              "isWait": false
-            }]
-          }]
-        }]
+        "branches": [
+          {
+            "id": "YES_BRANCH_ID",
+            "name": "Branch name",
+            "segments": [
+              {
+                "__segmentId": "SEGMENT_UUID",
+                "operator": "and",
+                "conditions": [
+                  {
+                    "conditionType": "contact_detail",
+                    "conditionSubType": "tags",
+                    "conditionOperator": "index-of-true",
+                    "conditionValue": [
+                      "tag-to-check"
+                    ],
+                    "__conditionId": "CONDITION_UUID",
+                    "__customFieldType__": "standard",
+                    "nestedDropdownTypes": [],
+                    "allowIsOperatorTypes": [],
+                    "ifElseNodeId": "CONDITION_NODE_ID",
+                    "isWait": false
+                  }
+                ]
+              }
+            ]
+          }
+        ]
       }
     },
     "branch_yes": {
@@ -209,7 +227,9 @@
       "parent": "CONDITION_NODE_ID",
       "cat": "conditions",
       "nodeType": "branch-yes",
-      "sibling": ["NO_BRANCH_ID"],
+      "sibling": [
+        "NO_BRANCH_ID"
+      ],
       "next": "FIRST_YES_CHILD_ID",
       "attributes": {
         "if": false,
@@ -223,7 +243,9 @@
       "parent": "CONDITION_NODE_ID",
       "cat": "conditions",
       "nodeType": "branch-no",
-      "sibling": ["YES_BRANCH_ID"],
+      "sibling": [
+        "YES_BRANCH_ID"
+      ],
       "next": "FIRST_NO_CHILD_ID",
       "attributes": {
         "else": true,
@@ -246,7 +268,6 @@
     },
     "branch_notes": "Branch nodes need BOTH parentKey AND parent (same value). Sibling arrays cross-reference the other branch. Condition node next points to [YES, NO]. Branch node next is a string to the first child when non-empty. CAUTION: Complex branching (>2 if/else in one workflow) can freeze GHL's UI renderer. Use separate exit workflows for nurture sequences instead."
   },
-
   "workflow_goal": {
     "example": {
       "id": "<UUID>",
@@ -260,7 +281,13 @@
             "conditions": [
               {
                 "goal_condition": "review_request_clicked",
-                "extras": { "reviewTypes": ["sms", "email"], "reviewLinkId": "" },
+                "extras": {
+                  "reviewTypes": [
+                    "sms",
+                    "email"
+                  ],
+                  "reviewLinkId": ""
+                },
                 "id": "<UUID>"
               }
             ]
@@ -273,7 +300,6 @@
     "notes": "Goal-event nodes sit inline in the action chain — when the goal condition fires during workflow execution, the configured action runs (default: 'exit' terminates the workflow path). The previous action's `next` should point to the goal node's id; the goal node itself does NOT have a `next` field. Use build_goal_event to construct the node — it handles UUID generation and the nested op/segments/conditions shape. Verified goal_condition value: 'review_request_clicked' (with extras { reviewTypes: ['sms', 'email'], reviewLinkId: '' }). Other goal_condition strings from GHL's UI pass through verbatim; the full catalogue of goal conditions has not been captured yet.",
     "build_helper": "build_goal_event(goal_condition, extras?, action='exit', target_node_id?, name='Goal', op='or', inner_op='or')"
   },
-
   "_trigger_patterns": {
     "real_shape": {
       "id": "<UUID>",
@@ -351,7 +377,6 @@
     },
     "notes": "Workflow GET requests must include ?includeTriggers=true or triggers silently disappear. Each trigger type has type-specific condition fields."
   },
-
   "_workflow_design_patterns": {
     "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 — this creates too many actions and can freeze GHL.",
     "exit_workflow": "Small 3-4 step workflow: remove_from_workflow → note → tag → notify. Triggered by a tag being added to the contact.",

package/templates/trigger-schemas.json

@@ -364,9 +364,45 @@
       "labsKey": null,
       "filterClass": "CustomDateReminderFilter",
       "conditions": [
-        {},
-        {}
-      ]
+        {
+          "operator": "custom-field-eq",
+          "field": "contact.customFields",
+          "value": "<customFieldId>",
+          "title": "Contact date field",
+          "type": "select",
+          "id": "custom-field"
+        },
+        {
+          "operator": "time-diff-now-lte",
+          "field": "customDateField.dateValue",
+          "value": 21,
+          "title": "Before no. of days",
+          "type": "number",
+          "id": "before-days-in-number"
+        },
+        {
+          "operator": "index-of-true",
+          "field": "contact.tags",
+          "value": "<tag>",
+          "title": "Has tag",
+          "type": "select",
+          "id": "has-tag"
+        }
+      ],
+      "extraTriggerFields": {
+        "match_year": false,
+        "custom_date_reminder_config": {
+          "recordType": "contact",
+          "customDateFieldId": "<customFieldId>",
+          "customDateFieldType": "DATE",
+          "matchYear": false,
+          "offsetDays": 21,
+          "runHour": "8",
+          "timezone": "",
+          "last_run": ""
+        }
+      },
+      "captureNote": "UI-generated shape captured 2026-08-08 from CLL WF 1a066847 (before-days variant, offsetDays 21, has-tag condition). 'After no. of days' NOT captured — likely a sibling operator to time-diff-now-lte; confirm in the UI before using. The custom_date_reminder_config object rides on the trigger alongside conditions."
     },
     {
       "value": "note_add",
@@ -2275,7 +2311,7 @@
       "appId": "68515cf6affc523761f4e74f",
       "companyName": "All The Apps",
       "triggerName": "Participant Joined Meeting ",
-      "description": "This trigger activates whenever a participant joins a Zoom meeting. It captures details such as the participant\u2019s name, email, join time, and meeting ID. Use this to track attendance, send personalized welcome messages, or update CRM records.  Example: Jane Smith (jane@example.com) joins a scheduled client onboarding meeting at 10:05 AM. This trigger can automatically log attendance, send a welcome email, and notify the meeting host.",
+      "description": "This trigger activates whenever a participant joins a Zoom meeting. It captures details such as the participant’s name, email, join time, and meeting ID. Use this to track attendance, send personalized welcome messages, or update CRM records.  Example: Jane Smith (jane@example.com) joins a scheduled client onboarding meeting at 10:05 AM. This trigger can automatically log attendance, send a welcome email, and notify the meeting host.",
       "templateId": "01JYKHM97F40D0K4CB5WSNKKQ7",
       "_id": "685bef320b94dc339a0fde1d",
       "customVars": [
@@ -2565,7 +2601,7 @@
       "appId": "68515dac857ac4ac43be90e1",
       "companyName": "All The Apps",
       "triggerName": "Update Customer",
-      "description": "To update an existing customer\u2019s information in your WooCommerce store, provide the customer ID along with the new details such as name, email, or billing address. For example, if \"John Smith\" changes his shipping address, you can quickly update his profile to keep records accurate and orders delivered correctly.",
+      "description": "To update an existing customer’s information in your WooCommerce store, provide the customer ID along with the new details such as name, email, or billing address. For example, if \"John Smith\" changes his shipping address, you can quickly update his profile to keep records accurate and orders delivered correctly.",
       "templateId": "01JYECNX7H7723PDEFYT6AGN05",
       "_id": "68594bdc4c1de9cca419c148",
       "customVars": [
@@ -2767,7 +2803,7 @@
       "appId": "68515dac857ac4ac43be90e1",
       "companyName": "All The Apps",
       "triggerName": "Update Order",
-      "description": "To modify an existing order in your WooCommerce store, select the order ID and update details such as status, shipping address, or product quantities. For example, changing the status of order ID \u201c1254\u201d from \u201cPending Payment\u201d to \u201cCompleted\u201d instantly updates the record in your store for accurate order tracking.",
+      "description": "To modify an existing order in your WooCommerce store, select the order ID and update details such as status, shipping address, or product quantities. For example, changing the status of order ID “1254” from “Pending Payment” to “Completed” instantly updates the record in your store for accurate order tracking.",
       "templateId": "01JYE9HTSJCHCXG75YMMGV7EAD",
       "_id": "685948434c1de9cca41965da",
       "customVars": [
@@ -2873,7 +2909,7 @@
       "appId": "68515dac857ac4ac43be90e1",
       "companyName": "All The Apps",
       "triggerName": "Create Order",
-      "description": "To create a new order in your WooCommerce store, enter the customer details, products, quantity, and payment information. For example, adding a customer name \u201cJohn Smith\u201d with two T-shirts and setting the status to \u201cProcessing\u201d will generate a new order instantly for him in your store.",
+      "description": "To create a new order in your WooCommerce store, enter the customer details, products, quantity, and payment information. For example, adding a customer name “John Smith” with two T-shirts and setting the status to “Processing” will generate a new order instantly for him in your store.",
       "templateId": "01JYE7Z4FCZXA9MB8F45TWWW8C",
       "_id": "68593a474c1de9cca4180de2",
       "customVars": [
@@ -3372,7 +3408,7 @@
       "appId": "685167a7c9d8a7f4d68e7fef",
       "companyName": "All The Apps",
       "triggerName": "Job in Progress",
-      "description": "Detects when a job\u2019s status changes to \u201cin progress\u201d in HouseCall Pro. This trigger is commonly used to automate notifications, update team workflows, and ensure efficient job tracking and management.",
+      "description": "Detects when a job’s status changes to “in progress” in HouseCall Pro. This trigger is commonly used to automate notifications, update team workflows, and ensure efficient job tracking and management.",
       "templateId": "01JYGQZ99RTCPQ7EB3ABAKHWW0",
       "_id": "685a81554c1de9cca4377988",
       "customVars": [
@@ -12537,7 +12573,7 @@
       "appId": "68518a78bd28100e82cefd93",
       "companyName": "All The Apps",
       "triggerName": "Payment Failed",
-      "description": "The Payment Failed trigger notifies your workflow whenever a customer\u2019s payment attempt is unsuccessful. Use this action to automate follow-ups, alert your team, or update customer records, ensuring timely handling of failed transactions and minimizing revenue disruption.",
+      "description": "The Payment Failed trigger notifies your workflow whenever a customer’s payment attempt is unsuccessful. Use this action to automate follow-ups, alert your team, or update customer records, ensuring timely handling of failed transactions and minimizing revenue disruption.",
       "templateId": "01JZ2P20PDF52A3TEY05RF4KGN",
       "_id": "6863af426bc372da326fe362",
       "customVars": [
@@ -14269,7 +14305,7 @@
       "appId": "685169967cd7af5925d3ce94",
       "companyName": "All The Apps",
       "triggerName": "Update Appointment",
-      "description": "The \"Update Appointment\" action allows you to modify the details of an existing appointment. Whether it\u2019s changing the appointment date, time, location, or client information, this action provides an easy way to keep your appointments up to date, ensuring that all details are accurate and reflect the latest changes.",
+      "description": "The \"Update Appointment\" action allows you to modify the details of an existing appointment. Whether it’s changing the appointment date, time, location, or client information, this action provides an easy way to keep your appointments up to date, ensuring that all details are accurate and reflect the latest changes.",
       "templateId": "01JZ8GN2BQNC9VXD2N25VNTQJ0",
       "_id": "6866afa66bc372da32b45755",
       "customVars": [
@@ -14416,7 +14452,7 @@
       "appId": "68515d1d0c620fa98f1b3f21",
       "companyName": "All The Apps",
       "triggerName": "Order Updated",
-      "description": "The Order Updated trigger activates workflows whenever an existing order\u2019s details are modified in Printful. Use it to sync records, notify customers, or update your fulfillment system automatically.",
+      "description": "The Order Updated trigger activates workflows whenever an existing order’s details are modified in Printful. Use it to sync records, notify customers, or update your fulfillment system automatically.",
       "templateId": "01K09BS29YGAXQG11EYQVFG90X",
       "_id": "687780806bc372da32f70c73",
       "customVars": [
@@ -18213,7 +18249,7 @@
       "appId": "68516b385c7d2960ea655e16",
       "companyName": "All The Apps",
       "triggerName": "User Update",
-      "description": "Triggers when an existing user\u2019s details are updated in a system connected to Mux.",
+      "description": "Triggers when an existing user’s details are updated in a system connected to Mux.",
       "templateId": "01JYHB3S1Q3RPM31ZYZHV1JKYC",
       "_id": "685ace864c1de9cca4402387",
       "customVars": [
@@ -18284,7 +18320,7 @@
       "appId": "68516b385c7d2960ea655e16",
       "companyName": "All The Apps",
       "triggerName": "Contact Updated",
-      "description": "Triggers when a contact\u2019s information is updated in a system integrated with Mux.",
+      "description": "Triggers when a contact’s information is updated in a system integrated with Mux.",
       "templateId": "01JYHAJT6C98F7WM8BD1T9KJNZ",
       "_id": "685acd154c1de9cca43fd2d5",
       "customVars": [
@@ -19124,7 +19160,7 @@
       "appId": "68515efc671ccb236e1c9eaf",
       "companyName": "All The Apps",
       "triggerName": "Contact Updated",
-      "description": "Triggers when an existing contact\u2019s details are modified.",
+      "description": "Triggers when an existing contact’s details are modified.",
       "templateId": "01JZAFMPB549V5RE04YW7SBBVJ",
       "_id": "6867ad776bc372da32c7a53f",
       "customVars": [
@@ -19337,7 +19373,7 @@
       "appId": "68516bcb5c7d29ba8465b33f",
       "companyName": "All The Apps",
       "triggerName": "Delete Contact",
-      "description": "This trigger activates whenever a contact is deleted in Job Nimbus. It captures details such as the contact\u2019s name, associated jobs, and removal timestamp. Use this to update CRM records, notify relevant team members, or trigger automated cleanup processes.  Example: A client, Sarah Johnson, is removed from Job Nimbus after project completion. This trigger can automatically delete her record from the CRM, revoke access to client portals, and archive related documents.",
+      "description": "This trigger activates whenever a contact is deleted in Job Nimbus. It captures details such as the contact’s name, associated jobs, and removal timestamp. Use this to update CRM records, notify relevant team members, or trigger automated cleanup processes.  Example: A client, Sarah Johnson, is removed from Job Nimbus after project completion. This trigger can automatically delete her record from the CRM, revoke access to client portals, and archive related documents.",
       "templateId": "01JYKA91T80M62042MJNF3PPQ2",
       "_id": "686413566bc372da327a16d3",
       "customVars": [
@@ -19956,7 +19992,7 @@
       "appId": "68516bcb5c7d29ba8465b33f",
       "companyName": "All The Apps",
       "triggerName": "Create Contact",
-      "description": "This trigger activates whenever a new contact is created in Job Nimbus. It captures details such as the contact\u2019s name, email, phone number, and associated project. Use this to sync customer data, trigger onboarding workflows, or send automated welcome emails.  Example: A new client, Sarah Johnson, is added to Job Nimbus for a roofing project. This trigger can automatically create a record in the CRM, send a welcome email, and assign a sales rep for follow-up.",
+      "description": "This trigger activates whenever a new contact is created in Job Nimbus. It captures details such as the contact’s name, email, phone number, and associated project. Use this to sync customer data, trigger onboarding workflows, or send automated welcome emails.  Example: A new client, Sarah Johnson, is added to Job Nimbus for a roofing project. This trigger can automatically create a record in the CRM, send a welcome email, and assign a sales rep for follow-up.",
       "templateId": "01JYK73TRTX3FV0E0SQSJ3YVR1",
       "_id": "685be4e90b94dc339a0f12e3",
       "customVars": [
@@ -22828,7 +22864,7 @@
       "appId": "6851899eaf8a69e109eef528",
       "companyName": "All The Apps ",
       "triggerName": "Contact Updated",
-      "description": "This trigger activates when an existing contact record is updated in the system. It monitors changes to contact information\u2014such as name, email, phone number, or other fields\u2014and triggers workflows based on those updates.",
+      "description": "This trigger activates when an existing contact record is updated in the system. It monitors changes to contact information—such as name, email, phone number, or other fields—and triggers workflows based on those updates.",
       "templateId": "01JZ36ZY47H44QWYTHYVHXNJK0",
       "_id": "6863f4076bc372da32759fbf",
       "customVars": [
@@ -22960,7 +22996,7 @@
       "appId": "6851899eaf8a69e109eef528",
       "companyName": "All The Apps ",
       "triggerName": "Appointment Created",
-      "description": "The Appointment Created trigger fires whenever a new appointment is scheduled in Keap. This event is triggered when a user books an appointment with you, whether it\u2019s through your booking page or directly in the system.",
+      "description": "The Appointment Created trigger fires whenever a new appointment is scheduled in Keap. This event is triggered when a user books an appointment with you, whether it’s through your booking page or directly in the system.",
       "templateId": "01JZ36GYJ74KF4FGT4JXDP5CVS",
       "_id": "6863f2676bc372da3274fe67",
       "customVars": [
@@ -24915,7 +24951,7 @@
       "appId": "6851840b671ccb3d9b32c891",
       "companyName": "All The Apps",
       "triggerName": "Party Updated",
-      "description": "Triggers when a party\u2019s information is updated in Capsule.",
+      "description": "Triggers when a party’s information is updated in Capsule.",
       "templateId": "01JZ3BAMKDTGNP1PBFCX80PPHF",
       "_id": "686406566bc372da3277fe64",
       "customVars": [
@@ -26180,7 +26216,7 @@
       "appId": "6904ec431ab8a75aacaacd68",
       "companyName": "Plugins",
       "triggerName": "Outbound Message Manual",
-      "description": "The Outbound Message Manual in the Outbound Message Action Automation for Workflows  offers guidance on effective messaging that bridges human interactions with real-time automation. It detects manually sent outbound messages and subsequently initiates\u00a0workflows.",
+      "description": "The Outbound Message Manual in the Outbound Message Action Automation for Workflows  offers guidance on effective messaging that bridges human interactions with real-time automation. It detects manually sent outbound messages and subsequently initiates workflows.",
       "templateId": "01K8XP92K7FGDM5XRS2ZW4R3SK",
       "_id": "6904f7ceeebd2db657607da7",
       "customVars": [
@@ -28368,7 +28404,7 @@
       "appId": "685150fd671ccb5cf312368a",
       "companyName": "All The Apps",
       "triggerName": "Customer Updated ",
-      "description": "This trigger activates when an existing customer\u2019s details are updated in Stripe, allowing you to automate actions like syncing changes to your CRM or notifying relevant teams.",
+      "description": "This trigger activates when an existing customer’s details are updated in Stripe, allowing you to automate actions like syncing changes to your CRM or notifying relevant teams.",
       "templateId": "01JY3ZCSZGY3S3VQJGHJ76DERK",
       "_id": "6853f6454c1de9cca4bb4319",
       "customVars": [
@@ -29636,7 +29672,7 @@
       "appId": "65c3ca4663331e6b1c8f98ae",
       "companyName": "Hiro.fm",
       "triggerName": "New Listener via Other Platform",
-      "description": "Triggers when a new listener is created.\u00a0",
+      "description": "Triggers when a new listener is created. ",
       "templateId": "01JX0P2MTTCQN3NFCB8PXV2S3Q",
       "_id": "68541d214c1de9cca4beb7de",
       "customVars": [
@@ -37851,4 +37887,4 @@
       ]
     }
   ]
-}
+}