How to Use Data Stores in Make.com

Data stores in make.com let you save and manage structured data directly inside your scenarios without relying on external databases. This guide walks you step by step through creating data stores, defining their structure, and using modules to add, search, update, and delete records.

What Are Data Stores in Make.com?

A data store is a lightweight, built-in database for your automations. Instead of calling an external system, you can store values directly inside make.com and reuse them across scenarios.

Each data store contains records with fields you define. Typical uses include:

Reference tables (lists of IDs, statuses, or mappings)
Caches of external data for faster scenarios
Lookups for routing logic in flows
Temporary storage for values between runs

Data stores are managed from the main navigation and are available to all scenarios within the same organization.

How to Create a Data Store in Make.com

Before using a data store in a scenario, you must create it and define its structure.

Step 1: Open the Data Stores Section in Make.com

In the left main menu, select Data Stores.
Click Add or the appropriate button to create a new data store.

Step 2: Configure the Data Store

When creating a new data store, you configure its basic settings:

Name: A clear, descriptive name that reflects how it will be used in make.com scenarios.
Description: Optional notes for your team about what the data store contains.

After saving, you move on to defining the structure of records.

Defining the Structure of a Data Store

The structure determines what fields each record in the data store will have. This is similar to defining columns in a spreadsheet or fields in a database table.

Primary Key in Make.com Data Stores

Every data store has a primary key field. This field must be unique for each record and is used for fast lookups and updates.

The primary key is required.
Each record must have a unique value in this field.
You normally choose an ID, code, or another unique identifier.

Adding Fields to the Structure

In addition to the primary key, you can add custom fields to store information relevant to your automations in make.com.

For each field, configure:

Name: The field name used in modules and mappings.
Type: Data type such as text, number, boolean, or other supported types.
Required: Whether the field must always have a value.
Default value (if available): Value used when no data is provided.

You can edit the structure later, but changing or removing fields can affect existing scenarios that rely on those fields.

Managing Records in a Make.com Data Store

Once the structure is ready, you can start adding and managing records using built-in modules or by editing records directly in the interface.

Adding Records Manually

Open the relevant data store from the Data Stores section.
Click to add a new record.
Fill in the primary key and other fields according to your structure.
Save the record.

This is useful for small reference lists or quick corrections.

Adding Records from a Scenario in Make.com

To add records automatically during a scenario run:

Open or create a scenario.
Add the Data store > Add a record module (or the equivalent add module).
Select the target data store.
Map values from previous modules to the fields, including the primary key.
Save and run the scenario.

Each execution creates a new record in the chosen data store.

Searching Records in a Make.com Scenario

To read data from a store, use a search or get module, depending on your need:

Search records: Retrieve multiple records by criteria.
Get a record: Retrieve a single record by primary key.

Add the appropriate data store module to your scenario.
Select the data store you defined earlier in make.com.
Set search criteria or map the primary key.
Map the output fields to other modules in the scenario.

Updating Existing Records

To update data already stored in a data store:

Use a module such as Update a record.
Select the relevant data store.
Provide the primary key value of the record to update.
Map the fields you want to change.
Run the scenario to apply updates.

Only the mapped fields are updated; other fields remain unchanged.

Deleting Records from a Make.com Data Store

If you need to remove data:

Add the Delete a record module (or equivalent) to your scenario.
Select the data store.
Map the primary key of the record you want to delete.
Run the scenario to remove the record.

Use this carefully, as deleted records cannot be restored from within make.com.

Best Practices for Using Data Stores in Make.com

To keep your automations stable and efficient, follow these practices when working with data stores.

Design the Structure Carefully

Plan the primary key so it is always unique and stable.
Avoid unnecessary fields to keep the structure simple.
Use clear, descriptive field names so your team can understand mappings easily.

Control Access Across Scenarios

Data stores are shared across scenarios within an organization. When multiple scenarios write to the same data store in make.com:

Document how each scenario uses the store.
Avoid conflicting logic, such as two scenarios updating the same field differently.
Test changes in a separate or cloned data store if possible.

Maintain and Clean Up Data

Periodically remove outdated records.
Check for unused data stores and archive or delete them.
Keep a simple log (for example, another data store) of major data changes if needed.

Where to Learn More About Make.com Data Stores

For full reference details and any updates to features or limits, always consult the official documentation. You can read more in the original guide on data stores here: Make data stores documentation.

If you need help designing complex automations, mapping data structures, or optimizing scenarios across your organization, you can also explore expert automation and integration services at Consultevo.

By defining a clear structure, using the available modules consistently, and following the practices in this guide, you can use data stores in make.com to build faster, more reliable automations without external databases.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help