# Set Memory

Store text data that persists across workflow executions. Perfect for maintaining conversation context, user preferences, or any state between runs. Data is stored with timestamps and can be appended or overwritten. Memories are automatically deleted after 7 days of inactivity (no read or write). **Important: Only works in webhook-triggered and cron-triggered workflows** (not manual/test runs).

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## When to use this node

Store text data that persists across workflow executions. Perfect for maintaining conversation context, user preferences, or any state between runs. Data is stored with timestamps and can be appended or overwritten. Memories are automatically deleted after 7 days of inactivity (no read or write). **Important: Only works in webhook-triggered and cron-triggered workflows** (not manual/test runs).

Add **Set Memory** to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.

## Configure the fields

| Field | What to enter |
| --- | --- |
| **Memory Name** | Unique name for this memory (e.g., 'conversation_context', 'user_preferences'). Allowed: letters, numbers, underscore, hyphen. Max 50 chars. |
| **Action** | How to handle existing data: 'overwrite' (replace all) or 'append' (add to top with timestamp)<br>Choices: `append`, `overwrite`.<br>Example/default shown in the editor: `append`. |
| **Data** | Text data to store. Can be any string content (conversation log, JSON, user info, etc.) |
| **Add Date/Time Prefix** | If 'true' (default), adds a date/time at the beginning of each entry. If 'false', only the data is stored.<br>Choices: `true`, `false`.<br>Example/default shown in the editor: `true`. |

## Use the result

Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.

| Output | Meaning / label |
| --- | --- |
| `success` | Success (true/false) |
| `message` | Result Message |

## Connect the next step

Connect the continuation shown on the canvas. Some nodes calculate their branches from the configured options. Read each branch label in the editor and connect the paths your workflow needs.

## Test it in a workflow

1. Configure this node with a small, recognizable test input or a test resource.
2. Check the variables from preceding steps and the connection selected in the inspector.
3. Save the workflow. For event-driven flows, generate the actual event; use **Run** only for a Manual workflow.
4. Open **Workflow Activity** and check the outcome before enabling wider use.

## If something goes wrong

- Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
- Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
- Follow the [troubleshooting guide](/help/troubleshooting/) for a symptom-by-symptom checklist.

## Related guides

- [Work with variables](/workflows/variables/)
- [Understand branches and error handling](/workflows/branches/)
- [Browse all nodes](/reference/nodes/)
- [Get Memory](/nodes/memory-get/)


## Catalog coverage

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.