# Memory



Workflow memory is a feature that allows you to store data as a variable that can be accessed at any point within a workflow, or within other workflows. **Workflow memory will persist even after a workflow has run, unlike typical data that lives within the life of a workflow run.**

### Setting Memory

To set workflow memory, you can create an action at any point using the app “Set Memory”

![](https://mindcloud.imgix.net/docs/document360/cc324f6106d8-image-82_1778245945364.octet-stream "image(82).png")

Within the config of the action, you can add any number of key-value pairs, setting the value based on any other action within the workflow.

![](https://mindcloud.imgix.net/docs/document360/65e1996a6e24-image-83_1778245957893.octet-stream "image(83).png")

- **Value:** This can be set from any other action, system, webhook parameters, or any other value accessible from within the workflow builder
- **Saves On:** This determines at which point the memory is saved, on `success` , `failure` , or `always`
- **Expires After:** This determines how long the value will retain in memory
- **Scope:** Here you can determine the scope of the memory, either workflow-specific or global (within a given Company)

Once configured, memory will be saved once the workflow step is run.

### Accessing Memory

Workflow Memory can be accessed through the “Workflow Memory” button at the top for reference, and within any workflow step for use in the workflow itself.

![](https://mindcloud.imgix.net/docs/document360/57ca30e06504-image-84_1778245957895.octet-stream "image(84).png")

Within a mapper or any other workflow step, the key-value pairs will always be accessible

![](https://mindcloud.imgix.net/docs/document360/74faba3b0e3b-image-85_1778245957896.octet-stream "image(85).png")