# What is a module in Make?

> A module in Make is one step in a scenario, drawn as a circle: a trigger, an action, a search or a tool. How modules connect and pass data along.

Source: https://learn.ynteractive.com/content/glossary/make-module · Updated 2026-10-20 · Free from Stepthrough (https://learn.ynteractive.com)

[n8n and automation](https://learn.ynteractive.com/content/glossary#topic-n8n-and-automation) · [AI glossary](https://learn.ynteractive.com/content/glossary)

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 October 20, 2026

[Take the free module →](https://learn.ynteractive.com/courses/ai-for-medical-dental-admin/9)Module 9 of the free [AI for Medical & Dental Office Admin](https://learn.ynteractive.com/courses/ai-for-medical-dental-admin) course, about 12 minutes. No account needed.

Updated October 20, 2026 · By [Robert Breen](https://learn.ynteractive.com/content/about)

## 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](https://learn.ynteractive.com/content/glossary/make-operation) and billed in [credits](https://learn.ynteractive.com/content/glossary/make-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](https://learn.ynteractive.com/content/make-com-google-forms-to-google-sheets), 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](https://learn.ynteractive.com/modules/make-first-scenario) or [read the step-by-step guide](https://learn.ynteractive.com/content/make-com-google-forms-to-google-sheets).

## Common confusions

### Module vs scenario

A [scenario](https://learn.ynteractive.com/content/glossary/make-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](https://learn.ynteractive.com/content/glossary/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

[Scenario (Make)](https://learn.ynteractive.com/content/glossary/make-scenario) · [Bundle (Make)](https://learn.ynteractive.com/content/glossary/make-bundle) · [Operation (Make)](https://learn.ynteractive.com/content/glossary/make-operation) · [Trigger](https://learn.ynteractive.com/content/glossary/trigger) · [Action](https://learn.ynteractive.com/content/glossary/action) · [Node](https://learn.ynteractive.com/content/glossary/node)

## More n8n and automation terms

[Multi-step Zap](https://learn.ynteractive.com/content/glossary/multi-step-zap) · [n8n](https://learn.ynteractive.com/content/glossary/n8n) · [n8n Cloud](https://learn.ynteractive.com/content/glossary/n8n-cloud) · [n8n data store node (Data table)](https://learn.ynteractive.com/content/glossary/data-store-node)

## Where you use it: free lessons

- [Your First Make.com Scenario: Google Forms to Google Sheets](https://learn.ynteractive.com/content/make-com-google-forms-to-google-sheets) (Make, 12 min)
- [Filters and Routers in Make.com: Send Urgent Requests One Way, Routine Ones Another](https://learn.ynteractive.com/content/make-com-router-and-filters) (Make, 12 min)
- [Add AI to Make.com: ChatGPT Writes a Personal Reply, Gmail Sends It](https://learn.ynteractive.com/content/make-com-chatgpt-gmail-personalized-reply) (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.

[All AI glossary terms, A to Z](https://learn.ynteractive.com/content/glossary) · [Free prompt templates](https://learn.ynteractive.com/content/prompts)
