nœuds / builtin / ai / aidependencies / chatmemories
Persistent Chat Memory (replaced)
Replaced by Chat Memory. Workflows that use Persistent Chat Memory keep working and are upgraded on save.
Ce contenu n’est pas encore disponible dans votre langue.
Gave an agent a conversation history saved under a key.
What it does
Section titled “What it does”Workflows that already use Persistent Chat Memory keep working, with the same key and history. The node now runs as a Chat Memory with Storage: Key, your conversation key, and Key scope: Shared: old keys were shared by every workflow, and they stay that way. When you open the workflow, the node shows that it was upgraded; saving the workflow turns it into a Chat Memory node.
Conversations saved under a key used to be invisible in the app. They now appear on the Memory page under Workflows, marked Recovered.
When to use it
Section titled “When to use it”Don’t add it to new workflows. Use Chat Memory with Storage: Key, and prefer Key scope: This workflow unless several workflows really need to share the conversation.
Inputs and settings
Section titled “Inputs and settings”| Réglage | Type | Ce que cela fait |
|---|---|---|
| Conversation Key (obligatoire) | Text | A stable, user-chosen identifier used to persist this memory across runs. |
Conversation Key becomes Chat Memory’s Key. Summarise older messages stays off, as before; turn it on in Chat Memory if you want it.
Outputs
Section titled “Outputs”This node has no output port. It plugs into a slot on another node instead of passing items along.
- Memory slot of Chat Trigger, Tools Agent, RAG Agent
Dependencies and credentials
Section titled “Dependencies and credentials”None. This node needs no connection and has no slots for other nodes.
Example workflow
Section titled “Example workflow”- Open a workflow that uses Persistent Chat Memory with the key
support-bot. - Save it. The node becomes a Chat Memory with Storage: Key, Key
support-botand Key scope: Shared. - Run it as before: the agent continues the same conversation.
Common issues
Section titled “Common issues”- “Conversation Key is required”. The key is empty. Fill in Key on the Chat Memory.
- Two workflows share a conversation. They use the same key with Shared scope, as the old node did. Switch one to This workflow if they should be separate.
Related nodes
Section titled “Related nodes”- Chat Memory: the node that replaces it.
- Chat Trigger: a chat window that uses a memory.