Triggers, Modules, and Connections
Understanding modules
Every module is either a trigger (starts the scenario), a search/action (does something in an app), or an aggregator/iterator (reshapes data). Knowing which type you're placing helps you build logical, readable scenarios.
Connections store your credentials
The first time you add a module for an app, Make asks you to authenticate (OAuth or API key) and saves this as a reusable "connection" — you won't need to re-authenticate for every new scenario using the same app.
Mapping data between modules
Click into any field of a downstream module to see available data "bubbles" from upstream modules — drag the exact field you need rather than typing values manually, avoiding typos and broken mappings.
Key Takeaways
- Modules are triggers, actions/searches, or data reshapers — know which is which.
- Connections store credentials once and reuse them across scenarios.
- Drag data bubbles between modules rather than typing values manually.
- Understanding module types helps you debug and build cleaner scenarios.
Map a data field between modules
In an existing scenario, click into a downstream field and drag a data bubble from an upstream module instead of typing a static value.