@elitedcs/ghl-mcp 3.84.0 → 3.84.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +35 -0
- package/README.md +1 -1
- package/dist/index.js +929 -228
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,41 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
+
## 3.84.1 — the phone agent answers, the repaint tells the truth, and the build waits to be told
|
|
6
|
+
|
|
7
|
+
**A phone agent you connect now actually answers.** Connecting a number to a voice agent wrote a
|
|
8
|
+
setting GoHighLevel stores but does not route calls by: the tool said the number was connected and
|
|
9
|
+
the readiness check said READY, while the number itself rang out to voicemail. The number is now
|
|
10
|
+
written the way GoHighLevel's own screen writes it, proven by a real call, and "connected" is only
|
|
11
|
+
claimed when the agent reads back that way. An agent still carrying the old setting is named, with
|
|
12
|
+
the two ways to repair it. Disconnecting clears the number for real; it used to leave it behind.
|
|
13
|
+
|
|
14
|
+
**Branding a GoHighLevel design says what changed, in what a visitor sees.** The report used to
|
|
15
|
+
count colour substitutions, which said "a full repaint" on a page where only the button changed.
|
|
16
|
+
It now compares the page GoHighLevel stored before and after, resolved through the design's own
|
|
17
|
+
colour settings, and says plainly when the visible palette barely moved. It also picks the colours
|
|
18
|
+
the page really paints with: the big bands a design is made of, rather than colours that only touch
|
|
19
|
+
a border. Headline and body faces no longer get swapped the wrong way round. Any text that was
|
|
20
|
+
readable and no longer meets the 4.5:1 standard is named, colour by colour, on the page result and
|
|
21
|
+
at the top of the run.
|
|
22
|
+
|
|
23
|
+
**The client document only offers what the build leaves out.** Ticking every feature used to clear
|
|
24
|
+
the record, and the document then offered features the build includes as "available next", priced.
|
|
25
|
+
A feature that was bought and then unticked disappeared from the document altogether. Both are
|
|
26
|
+
fixed, and ticking everything is now kept as a confirmation rather than as no answer at all.
|
|
27
|
+
|
|
28
|
+
**Nothing is built until you confirm what to build.** Saving what a client bought used to create
|
|
29
|
+
the build selection too. It now records the purchase only; the review screen is ticked from it, and
|
|
30
|
+
the build stops and asks until you confirm. Re-running a build from a saved plan follows the
|
|
31
|
+
selection as it stands now, instead of building what you removed.
|
|
32
|
+
|
|
33
|
+
**A plan aimed at something that does not exist is refused before it runs.** Every id a plan
|
|
34
|
+
carries is read back from the account first, as the kind the step says it is, including the ids
|
|
35
|
+
inside workflow steps, triggers, if/else branches and contact fields. A list the account cannot
|
|
36
|
+
page through is never treated as proof that an id is missing. A plan checked against one
|
|
37
|
+
sub-account cannot be approved or run against another. An id this cannot check is refused by name,
|
|
38
|
+
with the node it sits in and what to do about it.
|
|
39
|
+
|
|
5
40
|
## 3.84.0 — the brief reaches past GoHighLevel, Slack arrives, the build follows what the client bought
|
|
6
41
|
|
|
7
42
|
**The morning brief now asks your own Gmail, Google Calendar, Drive and Slack.** It ends with each
|
package/README.md
CHANGED