What is a module in Make?
Quick answer
A module in Make is one step in a scenario, shown as a round icon on the canvas. Each module does one thing with one app or tool: watch for new data (a trigger), search for records, create or update something (an action), or reshape data (a tool such as a router or aggregator). Modules pass bundles of data to the next one along the line.
Last updated
Take the free module →Module 9 of the free AI for Medical & Dental Office Admin course, about 12 minutes. No account needed.
Updated · By Robert Breen
Why it matters for a small business
Thinking in modules makes any automation easier to plan. Write the job as "when this happens, find that, then do this", and each part becomes a module. It is also how you troubleshoot: after a run, every module shows a bubble with what came in and what went out, so you can see exactly where something went wrong.
Each module that runs uses part of your plan's usage, counted as operations and billed in credits, so fewer, well-chosen modules make a cheaper and simpler scenario. Every module that talks to an app also needs a saved connection to that app.
Where you'll use it: in the Make scenario builder, the big plus adds the first module, which is always the trigger. The small plus on the right of a module adds the next one. Clicking a module opens its settings panel, and clicking a field opens the mapping panel with data from earlier modules.
In a real lesson: Your First Make.com Scenario: Google Forms to Google Sheets
In the free Your First Make Scenario lesson, Brookside Dental builds a scenario with two modules. The first is Google Forms Watch Responses, the trigger. You create a connection, paste the Form ID and leave the limit at two.
The second is Google Sheets Add a Row, added with the small plus. You pick the New patient requests sheet and map the form's full name, email and reason into the columns as purple tags. After Run once, both modules show a bubble with a 1 in it, and the one on Google Sheets shows the row it added.
Try this lesson free or read the step-by-step guide.
Common confusions
Module vs scenario
A scenario is the whole automation. A module is one step inside it.
Make module vs n8n node
Same idea, different name. n8n calls each step a node and draws it as a box instead of a circle.
Tips
- Rename modules to say what they do, so a long scenario stays readable.
- Saving a module's settings does not save the scenario; click the save icon in the toolbar too.
- Click a module's bubble after a test to see its input and output.
Related terms
More n8n and automation terms
Where you use it: free lessons
- Your First Make.com Scenario: Google Forms to Google Sheets (Make, 12 min)
- Filters and Routers in Make.com: Send Urgent Requests One Way, Routine Ones Another (Make, 12 min)
- Add AI to Make.com: ChatGPT Writes a Personal Reply, Gmail Sends It (Make, 18 min)
Frequently asked questions
- What module types does Make have?
- The main ones are triggers, searches and actions for apps, plus flow control and tool modules such as routers, iterators and aggregators.
- Can one module connect to several apps?
- No. Each app module works with one app through one connection. Use the HTTP module for an app Make has no module for.