nodes / builtin / ai / aidependencies / chatmemories
Local Memory (replaced)
Replaced by Chat Memory. Workflows that use Local Memory keep working and are upgraded on save.
Gave an agent a saved conversation history, picked from your conversations.
What it does
Section titled “What it does”Workflows that already use Local Memory keep working, with the same conversation and history. The node now runs as a Chat Memory with Storage: Conversation and the conversation you had picked. When you open the workflow, the node shows that it was upgraded from Local Memory; saving the workflow turns it into a Chat Memory node.
When to use it
Section titled “When to use it”Don’t add it to new workflows. Use Chat Memory.
Inputs and settings
Section titled “Inputs and settings”| Setting | Type | What it does |
|---|---|---|
| Memory (required) | Memory picker | The memory to use to make the request. |
Memory becomes Chat Memory’s Conversation. 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 Local Memory, for example a Chat Trigger with a Tools Agent.
- Save it. The node becomes a Chat Memory with Storage: Conversation and the same conversation.
- Chat as before: the history is still there.
Common issues
Section titled “Common issues”- I can’t find Local Memory in the node list. It was replaced. Add Chat Memory instead.
- Where is the conversation? On the Memory page, under Workflows.
Related nodes
Section titled “Related nodes”- Chat Memory: the node that replaces it.
- Chat Trigger: a chat window that uses a memory.