How to use data stores for persistent memory on Make

intermediate 8 min read Updated 2026-04-20

Quick Answer

Data stores in Make allow you to store and retrieve data persistently across scenario runs, acting as a database for your automations. You can create data stores, add/search/update records using dedicated modules, and use them to maintain state between executions.

Full Make Review

Prerequisites

Active Make account with paid subscription
Basic understanding of Make scenarios
Familiarity with JSON data structures
Knowledge of Make modules and connections

Step-by-Step Instructions

Create a New Data Store

Navigate to Data structures in your Make dashboard sidebar, then click Data stores. Click the Add button to create a new data store. Enter a descriptive name for your data store and define the data structure by adding fields with their respective data types (text, number, date, etc.). Each data store automatically includes a key field as the primary identifier.

Plan your data structure carefully as modifying it later can affect existing records.

Add Data Store Modules to Your Scenario

In your scenario editor, click the + button to add a new module. Search for Data store and select the appropriate operation: Add a record, Search records, Get a record, Update a record, or Delete a record. Choose your previously created data store from the dropdown menu.

Use descriptive module names to keep track of different data store operations in complex scenarios.

Configure Add a Record Module

Select your data store and provide a unique Key value for the record. Fill in the data fields you defined earlier with either static values or dynamic data from previous modules using the mapping panel. The key must be unique - if you use an existing key, it will update that record instead of creating a new one.

Use timestamp or UUID functions to generate unique keys automatically.

Set Up Search Records Module

Configure the search parameters by setting Limit (maximum number of records to return) and optionally add Filter conditions. In the filter section, specify the field name, operator (equals, contains, greater than, etc.), and the value to search for. You can add multiple filter conditions using AND/OR logic.

Start with a low limit during testing to avoid processing too many records.

Configure Update Record Module

Select your data store and specify the Key of the record you want to update. Map the new values to the fields you want to modify. Leave fields empty if you don't want to change them. The module will only update the specified fields while preserving others.

Always verify the key exists before updating, or use 'Add a record' which handles both creation and updates.

Implement Data Retrieval Logic

Use the Get a record module when you need to retrieve a specific record by its key. Configure error handling using the Advanced settings to specify what happens if the record doesn't exist. You can choose to continue the scenario, stop execution, or create a fallback route.

Combine Get a record with Router modules to handle different scenarios based on whether data exists.

Test and Monitor Data Store Operations

Run your scenario in test mode and monitor the data store operations in the execution history. Check the Data stores section in your dashboard to verify that records are being created, updated, or deleted correctly. Use the Browse records feature to manually inspect your data store contents.

Enable logging for data store modules to track operations and debug issues more effectively.

Common Issues & Troubleshooting

Records not being created or updated

Verify that all required fields are mapped correctly and that the data store connection is properly configured. Check if the key field contains valid, non-empty values and ensure your subscription includes data store operations.

Search operations returning no results

Double-check your filter conditions and ensure field names match exactly (case-sensitive). Verify that the data you're searching for actually exists in the data store using the Browse records feature in the dashboard.

Data store operations consuming too many operations

Optimize your search queries by using more specific filters and lower limits. Consider using Get a record instead of Search records when you know the exact key. Implement caching logic to avoid redundant data store calls.

Key conflicts when adding records

Implement unique key generation using functions like now combined with random numbers, or use UUIDs. Check for existing records before adding new ones, or use the update operation which handles both creation and modification.

Prices mentioned in this guide are pulled from current plan data and may change. Always verify on the official Make website before purchasing.

Visit Make View Make Pricing