Tools
Memory
Add, retrieve, and delete key-value memory that persists across workflow runs
The Memory block stores and retrieves conversational entries under a conversation ID, persisting them across separate workflow executions. It is a low-level building block for injecting artificial memory into a conversation.
Do not use this block unless explicitly required. For natural conversation memory, use an Agent block's built-in memory modes instead — this block exists for cases that need direct, explicit control over what is stored.
Configuration
- Operation —
Add Memory,Get All Memories,Get Memory, orDelete Memory. - Conversation ID — identifies which memory thread to operate on (for example
user-123). Required for every operation. - Role —
User,Assistant, orSystem. Only shown, and required, forAdd Memory. - Content — the message content to store. Only shown, and required, for
Add Memory.
Inputs and outputs
| Field | Type | Description |
|---|---|---|
operation (input) | string | Operation to perform. |
id (input) | string | Conversation ID. |
role (input) | string | Agent role, for Add Memory. |
content (input) | string | Memory content, for Add Memory. |
memories (output) | json | Memory data returned by Get Memory / Get All Memories. |
id (output) | string | The conversation ID the operation ran against. |
Example
Add a memory entry for user-123 with role user after each turn of a custom chat loop, then use Get All Memories at the start of the next run to rebuild context the Agent block would not otherwise have.