Types of Make.com Modules Explained Step by Step

When you first open make.com and start building scenarios, the wide range of module types can feel confusing. This guide shows you exactly how each module type works and how to choose the right one for your automation.

All information in this how-to article is based on the official documentation at this Make module types page, distilled into a practical, step-driven format.

Understanding Module Roles in Make.com Scenarios

Modules are the building blocks of every scenario you create in make.com. Each module performs a specific task, such as retrieving data, transforming it, or sending it to another service.

At a high level, modules can:

• Trigger a scenario when a specific event happens
• Retrieve data from a service or app
• Create, update, or delete data
• Transform or route data inside the scenario

To design reliable workflows in make.com you must understand the capabilities and limitations of each type of module.

How to Use Trigger Modules in Make.com

Trigger modules start the execution of a scenario. They monitor an app, service, or internal event, and when a condition is met, the scenario runs.

Types of Trigger Modules in Make.com

There are several ways a trigger can behave in make.com:

• Instant triggers – Start the scenario immediately when an event occurs (for example, a new record is created).
• Polling triggers – Check a service at regular intervals and start the scenario when new data appears.
• Webhook-based triggers – Receive data from an external system via HTTP requests.

Steps to Configure a Trigger Module

1. Add a new scenario in make.com and click the plus icon to insert your first module.
2. Select the app or service you want to watch (for example, a CRM or form tool).
3. Choose a trigger event such as “Watch records” or “New submission.”
4. Authorize the connection if requested and specify filters such as folder, list, or status.
5. Set the scheduling options (instant, at intervals, or manual) and save.

Every scenario in make.com must have one trigger module as its starting point.

Working with Search Modules in Make.com

Search modules look up data that already exists in an app or database and return matching records into your scenario.

When to Use Search Modules

Use a search module when you need to:

• Find records by ID, email, name, or other fields
• Check if a contact or order already exists
• Retrieve related data before updating or creating records

How to Configure a Search Module in Make.com

1. Add a module after your trigger or after another processing step.
2. Select the same app (or a different one) that contains the data you want to search.
3. Choose a search action such as “Search records” or “Get item.”
4. Map input fields from previous modules (for example, email from the trigger output).
5. Specify filters or query expressions if available, then test the module.

Search modules in make.com often combine with routers and filters so you can branch behavior depending on whether data is found.

Retrieve (Get) Modules in Make.com

Retrieve or “Get” modules load a specific record, usually by a unique identifier such as an ID.

Typical Uses for Retrieve Modules

Retrieve modules are ideal when:

• You already know the record ID from a previous step
• You need full record details, not just a search result summary
• You want to refresh data before making changes

Configuring Retrieve Modules

1. Add a new module in your make.com scenario after a step that outputs an ID.
2. Select the app and a “Get” or “Retrieve” action.
3. Map the ID field from the output of a previous module.
4. Run once to verify that the retrieved data looks correct.

Because they are precise, retrieve modules reduce ambiguity when working with large databases in make.com.

Create, Update, and Delete Modules in Make.com

These modules are responsible for writing changes back to your apps and services.

Create Modules

Create modules make new records such as contacts, deals, tasks, or tickets.

To use them in make.com:

1. Insert a create module after any logic or search steps.
2. Choose the app and the “Create” type action.
3. Map required fields like name, email, or title from earlier modules.
4. Optionally map optional fields for richer records.
5. Test and confirm that new items are created as expected.

Update Modules

Update modules change existing records, often using an ID obtained from a search or retrieve module.

1. Add an update module after a step that outputs the record ID.
2. Select which fields you want to update in your make.com scenario.
3. Map new values from earlier modules or from calculated functions.
4. Run a test to ensure only the intended records are modified.

Delete Modules

Delete modules remove records or items entirely.

Use them carefully in make.com by:

• Making sure the ID or key you pass is correct
• Testing in a safe environment or with sample data first
• Optionally backing up key data before deletion

Iterator and Aggregator Modules in Make.com

Iterator and aggregator modules help you work with collections of items, such as multiple rows, emails, or orders.

Iterator Modules

Iterator modules take a bundle containing a list and split it into multiple bundles, one for each item.

To implement an iterator in make.com:

1. Place it directly after a module that outputs an array or list.
2. Select the array field you want to iterate over.
3. Build the following modules to process each item individually.

Aggregator Modules

Aggregator modules perform the opposite function. They collect multiple bundles and merge them into a single bundle, often creating arrays.

Configure an aggregator by:

1. Adding it after a sequence that produces many bundles.
2. Defining which fields should be grouped into arrays.
3. Using the aggregated output in emails, reports, or summaries.

Router and Flow Control Modules in Make.com

Router and flow control modules determine how data moves through your scenario and which paths it follows.

Router Modules

A router creates branches so each bundle can follow different paths based on conditions.

In make.com you can:

• Add a router module where you want to split the flow.
• Create one or more branches from the router.
• Apply filters on each branch to route bundles selectively.

Other Flow Control Modules

Common flow control options include:

• Filters to allow or block bundles based on conditions
• Tools such as sleep, set variable, or error handling modules
• Aggregators and iterators to reshape how data moves between steps

Proper flow control is essential for building robust and maintainable automations in make.com.

How to Plan Scenarios with the Right Make.com Modules

Before you start dragging modules into your canvas, invest a few minutes to plan the scenario structure.

Planning Checklist

• Identify the event that should start the scenario and choose the trigger module.
• Decide where you need to search or retrieve existing data.
• Specify which objects must be created, updated, or deleted.
• Determine if you will process multiple items and need iterators or aggregators.
• Map decision points where routers and filters will be required.

Following this checklist will help you select the correct module types in make.com from the start.

Next Steps for Learning Make.com Modules

To deepen your understanding, compare this guide with the official overview at Make.com module types documentation and practice by building small test scenarios.

If you need expert help designing complex workflows, you can also consult automation specialists at Consultevo, who work extensively with make.com and related tools.

By mastering each module type, you will be able to design accurate, efficient automations in make.com with confidence.

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