AI Memory Key
in progress
J
Jeff Valin
Unless I am missing something, in order for Chat GPT inside GHL to remember the conversation from one workflow to the next you need to save it at the end of each workflow and the recall and prompt the bot to remember it? The only way to do this is custom fields. As the conversation expands, the data in this field grows. Are there plans to create a an AI Memory Key that stores the conversation between Chat GPT and the contact?
R
Ryan Hartigan
And ability to manage prompts within workflows would be next level too
A
Anthony SIFTR Admin
Hey guys, would really appreciate some support on this idea, its a rather urgent issue for everyone I know: https://ideas.gohighlevel.com/automations/p/new-contacts-followers-almost-usless
P
Prasoon Dadhich
in progress
J
Jarle Lund
Prasoon Dadhich hi! In the the Townhall they mention this do you now when this is scheduled to release ?
P
Prasoon Dadhich
Jarle Lund Hi, GPT 4 upgrade will be launched first and post that we will release the AI Memory Key also. We are working on it and trying to release this ASAP.
P
Prasoon Dadhich
planned
T
The Scaling Team
yes we need this asap!
J
Joshua Hayeslip
We really need this
J
Joshua Hayeslip
Need this ASAP
J
Joe Johnston
Event better than AI memory... a JSON array custom field type! We're currently storing AI memory with custom fields and custom webhook calls to Make.com. We store chat history in sanitized (escaped) JSON in a custom field as single line text since JSON does play well with line returns. A JSON array custom field type would be an absolute game changer and be instantly useful for AI memory and a bunch of other features. Add a couple basic workflow actions to push and pop values on the array. All native MongoDB stuff (I think GHL is running on Mongo?). Repurpose the multi email popup widget for editing array values in the contact view.
By "JSON" array I mean JSON objects inside of the array. On first implementation, we wouldn't need a way to access array object values directly. Maybe that could come later. But adding values to the array should work like the custom webhook were it expects valid JSON as input: strings, numbers, objects, etc. Then any time the JSON array custom value is used, just output it without escaping. In the custom webhook action, we could then simply add the JSON array to the raw body section to pass it along to external API. And ChatGPT already understands arrays, so it's trivial to send the array to the GHL ChatGPT action with just minor prompt tweaking and no modifications to the ChatGPT workflow action. As a bonus, it would be amazing to be able to do things like {{contact.json_array_field_name.first}} and {{contact.json_array_field_name.last}}. Let me know if you need more details on this. I think there's a way to implement it with minimal effort on GHL dev team. Having array support would put GHL lightyears beyond any other CRM platform for so many use cases.
C
Clifford Paulick
Joe Johnston could use Custom Objects once that's released: https://ideas.gohighlevel.com/crm/p/custom-objects
Core Platform
Merged in a post:
Chat GPT Conversation History
T
Tyler Uenaka
Somehow store the conversation history within ChatGPT so the bot can facilitate conversations for you. This is possible using GHL, Zapier, and ChatGPT. However it would be a lot easier to just make it in the workflows! The issue right now is it just doesn't remember the contact, nor the conversation history so the conversations aren't that great.
J
Jacob Moore
GHL would be the ULTIMATE follow up system if it had this. We NEED this.
Load More
→