How to Map Data in Make.com Scenarios

Mapping data in make.com is a core skill for building powerful, reliable automations. This how-to guide walks you step by step through using the mapping panel, understanding the data tree, and correctly passing information between modules in your scenarios.

Understanding Data Mapping in Make.com

In any make.com scenario, data mapping is the process of connecting the output from one module to the input fields of another. Instead of manually typing values everywhere, you drag and drop items from the data tree into the fields you want to populate.

Mapping lets you:

Re-use data captured earlier in the scenario.
Avoid repetitive manual input.
Keep information consistent across connected apps.
Build dynamic workflows that adjust to incoming data.

You perform mapping inside the module configuration window, where you see both editable fields and the data tree.

Opening the Mapping Panel in Make.com

To start mapping in make.com, you first open the scenario and module where you want to use data from previous steps.

Open your scenario in the make.com editor.
Click the module you want to configure.
In the configuration dialog, locate the field you want to populate with mapped data.
Ensure the field is set to Map mode where applicable, so it can accept mapped items.

Once you are in the configuration dialog, the data tree appears on the right side and shows all available bundles and items you can map.

The Data Tree in Make.com

The data tree is the central tool for mapping in make.com. It lists all data outputs provided by the modules that run before the currently selected module.

Key characteristics of the data tree:

Items are grouped by module and by bundle.
Each item in the data tree has a label that corresponds to an output field from a previous module.
You can expand or collapse sections to navigate complex structures.
Only data produced earlier in the scenario is available for mapping.

If a module has not run yet, or if its output is conditional, some data may not appear until you execute or re-execute the scenario.

Basic Data Mapping Steps in Make.com

Use the following basic procedure to map data from one module to another in make.com:

Select the target field
Click into the field in the module configuration where you want to insert data.
Locate the source item in the data tree
On the right, expand the module whose output you want to use and find the specific field.
Drag and drop the item
Drag the chosen item from the data tree and drop it into the target field. The field will show a colored token representing the mapped data.
Combine mapped items and text (optional)
You can mix mapped values with static text. For example, you might create a message like: “Order ID: [Order ID token]”.
Save and test
Click OK or Save to confirm, then run the scenario to verify that the mapped data behaves as expected.

Using Different Value Types in Make.com Mapping

When mapping fields in make.com, you often work with different value types. Recognizing these helps you map correctly and avoid errors.

Text Values in Make.com Mapping

You can map text outputs, such as names, descriptions, or notes, into text fields. Typical uses include:

Mapping a contact name from a CRM module into an email greeting.
Combining multiple text fields into a single message.
Adding prefixes or suffixes to mapped text values.

Numeric Values in Make.com Mapping

Numeric values, such as amounts, counts, or identifiers, can be mapped into numeric fields and used in calculations. For example:

Passing an order total into an invoicing module.
Mapping a quantity to update inventory records.
Using numbers in formulas with functions available in the data mapping editor.

Dates and Times in Make.com Mapping

Date and time outputs are common in scheduling and logging. In make.com you can:

Map a timestamp from a trigger to a calendar event.
Use date functions to format or modify mapped date values.
Pass date information to external services that require a specific format.

Array and Collection Data in Make.com

Some modules return arrays or collections. In make.com, these structures appear as expandable sections in the data tree. When mapping them:

Identify whether the module returns multiple items (bundles).
Use iterator or aggregator modules when you need to work with each item individually or combine them.
Map fields from within each collection item to build lists or complex records.

Editing and Removing Mapped Items in Make.com

After mapping data in make.com, you might need to change or remove mappings.

Edit a mapped value: Click inside the field and adjust the mixture of tokens and static text.
Remove a token: Place your cursor after the token and use backspace or delete to remove it.
Replace data source: Drag a different item from the data tree into the same field.

Always re-run the scenario after editing mappings to confirm the new configuration behaves as intended.

Best Practices for Data Mapping in Make.com

Following simple best practices makes your make.com scenarios easier to maintain and troubleshoot.

Name modules clearly so their outputs are easy to identify in the data tree.
Test frequently after changing mappings to catch issues early.
Use comments and notes in your scenario to explain complex mapping logic.
Validate data types before mapping, especially when passing numbers, dates, or arrays.
Re-run modules to refresh the data tree when you change prior configuration.

Troubleshooting Mapping Issues in Make.com

If a mapped field in make.com does not behave as expected, check the following:

Is the source module running successfully?
If the module fails, no data is passed forward.
Is the correct bundle in use?
In multi-bundle scenarios, make sure you map from the intended execution path.
Are data types compatible?
For example, a text field may accept mapped numbers, but some target apps require strictly formatted values.
Has the scenario been re-run?
The data tree updates based on the latest run. Execute the scenario again if you changed upstream modules.

When needed, check the run history to inspect how data moves between modules and which values are actually mapped at each step.

Learn More About Make.com Mapping

To dive deeper into data mapping in make.com and review the original documentation, see the official guide at this make.com help page.

If you need expert assistance designing complex automations and mapping strategies, you can work with specialists at Consultevo, a consulting partner focused on automation and integration solutions.

By understanding how to use the data tree, how to map different value types, and how to troubleshoot common issues, you can build robust make.com scenarios that move data accurately between all your connected applications.

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