How to Add and Configure Another Module in Make.com

In this guide, you will learn step by step how to add another module in a make.com scenario, configure its fields, map data, and optimize how your automation runs from start to finish.

The instructions below are based on the official documentation and walk you through a realistic example using a task manager app, a spreadsheet, and an email service. You can follow the same logic for any other apps and services supported by the platform.

Before You Add a New Module in Make.com

Before inserting another module, make sure you have these basics in place:

• A working scenario with at least one module already configured.
• Valid connections to the apps or services you plan to use.
• Access to any supporting resources (for example, a spreadsheet or a database table).

In the reference example, a task manager module provides the data that is sent to a spreadsheet and then used to trigger an email to the task owner.

Step 1: Insert Another Module in Make.com

The first step is to insert a new module into your scenario flow. This module will receive data from a previous module and pass structured data on to the next one.

1. Open your scenario and locate the module that already produces the data you need (for example, a task-based module that outputs task details).

2. Click the small plus icon that appears on the right side of that module.

3. In the app selector, choose the service you want to use. In the sample scenario, a spreadsheet app is selected to store task information.

4. Select the specific action you need, such as “Add a row” or a similar create/insert operation.

Once selected, the new module will appear in the scenario sequence directly after the previous one.

Step 2: Configure the New Module in Make.com

After adding the module, you must configure its basic settings and choose the correct resource it will work with.

1. Click the new module icon to open its configuration dialog.

2. Choose or create a connection to the target service if you have not already connected it.

3. Select the concrete resource, such as a specific spreadsheet file or table.

4. If available, pick the sheet, table, or list inside that resource where new data should be stored.

When the configuration dialog loads successfully, you should see a list of fields available for mapping, based on the structure of the selected resource.

Step 3: Map Fields Between Modules in Make.com

Field mapping defines how data from one module flows into the next. This is where you tell the scenario exactly what information goes where.

1. Review the list of input fields in the new module, such as “Title”, “Status”, “Description”, “Due date”, and similar fields.

2. Click into a field where you want to map data from a previous module.

3. Use the panel that appears (often on the right) to select an output item from the earlier module, such as Title or Status from the task module.

4. Repeat this process for each field you want to populate. For example, map the task title to the spreadsheet title column, and the task status to the status column.

You can leave non-required fields empty, or you can combine text and variables, such as writing a custom description that includes mapped values from earlier modules.

Example: Using Make.com to Store Task Data

To illustrate the mapping process, imagine that new tasks are created in a task manager and then recorded in a spreadsheet for reporting.

• Task title from the task module is mapped to the Title column in the spreadsheet.
• Task status is mapped to a Status column.
• Task owner email is mapped to a column that will later be used by an email module.

With these fields in place, every time a task is processed, a new row appears in the spreadsheet containing all the important details.

Step 4: Add a Third Module in Make.com (Optional)

Many scenarios extend beyond two modules. For instance, you might want to send an email notification after logging data in a spreadsheet.

1. Click the plus icon to the right of the spreadsheet module.

2. Select an email or notification service from the app list.

3. Choose an appropriate action, such as “Send an email.”

4. Configure the module to use mapped data from the spreadsheet module or directly from the initial module, depending on what information you need.

You can map fields like recipient address, subject line, and message body using the data stored in previous steps.

Configuring Email Fields in Make.com

When setting up an email module, focus on three main areas:

• To: Map the recipient email address, such as the task owner field from the task module.
• Subject: Combine static text and mapped values, for example “New task created: [Task Title]”.
• Message body: Add formatted text and insert multiple mapped fields, such as task description, status, and links.

This structure ensures that every message is personalized and automatically updated with data from your workflow.

Step 5: Run and Test Your Make.com Scenario

After everything is configured, it is important to test the entire flow from start to finish.

1. Turn on or run your scenario once manually from the scenario editor.

2. Trigger the initial event, such as creating or updating a task in your task manager.

3. Watch the scenario execution progress. Each module should show a number indicating how many operations have been processed.

4. Open your spreadsheet to confirm that a new row has been added with the correct title, status, and any other mapped data.

5. Check your email inbox (or the inbox of the configured recipient) to verify that the notification was sent and that the content matches your mappings.

If any field is empty or incorrect, return to the corresponding module configuration, review the field mapping, and adjust as needed.

Managing Filters and Execution Order in Make.com

As your scenario grows more complex, you may need filters or additional conditions between modules.

• Insert filters between modules to limit which records pass through based on status, dates, or custom values.
• Reorder or branch your scenario so that different types of data follow different paths.
• Test each path separately to confirm that modules are executed only when the conditions are met.

Careful design of filters and conditions will keep your automation efficient and prevent unnecessary operations.

Additional Resources for Make.com Users

To go deeper into scenario design, module settings, and advanced options such as iterators and aggregators, you can consult the original help article that this walkthrough is based on: official step-by-step instructions.

For broader automation strategy, AI integration, and workflow optimization around make.com implementations, explore expert resources at Consultevo, where you can learn how to design scalable automation architectures.

Summary: Building Modular Scenarios in Make.com

By following these steps, you now know how to:

• Add another module to an existing scenario.
• Configure connections and resources.
• Map data from earlier modules into new fields.
• Extend the workflow with email or other actions.
• Test and refine execution so every module behaves as expected.

Once you are comfortable adding and configuring modules in make.com, you can design powerful, multi-step automations that save time, reduce manual work, and keep your data synchronized across all your tools.

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