Automation Glossary
Plain-language definitions of the terms you'll see when documenting Make.com workflows.
- Scenario
- A Make.com automation — a sequence of modules connected to run automatically when triggered.
- Blueprint
- The JSON definition of a scenario, describing every module, connection, and setting.
- Module
- A single step in a scenario (e.g., an HTTP request, a filter, or a Slack message).
- Operation
- A unit of work Make.com counts toward your plan limit; roughly one module execution per run.
- Connection
- A saved authentication to a service (e.g., a Slack or Google account) that modules reuse.
- Router
- A module that splits a flow into multiple routes based on conditional logic.
- Iterator
- A module that loops over each item in an array, processing them one at a time.
- Aggregator
- A module that bundles multiple separate bundles back into a single array.
- Webhook
- A trigger that starts a scenario when an external system sends an HTTP request.
- Filter
- A condition placed on a connection that only lets data through when it matches.
- Error Handler
- Logic (Break, Ignore, Resume) attached to a module to control what happens on failure.
- Data Store
- A simple key-value store inside Make.com for sharing state between scenarios.
Frequently asked questions
What is a Make.com blueprint?
A blueprint is the JSON file that defines a scenario — every module, connection, and setting. Xray Flow reads blueprints to generate documentation.
What is the difference between a scenario and a module?
A scenario is the whole automation; a module is a single step within it.
Last updated: July 2026