Updated Aug 4, 2026

Session Memory Operations

Use this action when you want to store a value and reuse it in later CEL expressions during the current workflow or assistant execution context.

Best for

• Saving a value from one step for later conditions
• Keeping a simple flag, counter, or lookup result available to later steps
• Cleaning up temporary values when they are no longer needed

Main fields

Field	What it does
Operation	Chooses set, get, delete, or merge
Key	Names the value you want to store (not used with merge)
Value	The value to store, used with set and merge

Merge evaluates Value to an object and stores each of its key-value pairs at once, so it does not take a Key.

What later steps can use

This action does not create a separate step output. Instead, the stored value can be referenced directly in later CEL expressions by the key name you chose.

Example:

• Save customerTier
• Use customerTier in a later condition or message

Tips

• Use simple key names like customerTier, latestSummary, or shouldEscalate.
• In most cases, Set and Delete are the operations you will use most often.
• You do not need a separate Get step, because later expressions can reference the stored key directly.
• Use debugging to confirm the stored value is available where you expect it.