A
Aggregator
A flow control module that combines multiple bundles into one. The opposite of an iterator. Common use: collecting line items into a single Slack message.
AI Agent
A scenario type introduced in late 2024 where an LLM decides which tools to call autonomously. Different from regular scenarios where the flow is predetermined.
Apps
Third-party services Make connects to (Gmail, Slack, Notion, etc.). Make has 1,800+ apps natively integrated.
Array Aggregator
A specific aggregator that bundles items into a JSON array. Useful when you need to send multiple records to an API in one request.
B
Blueprint
The exportable JSON representation of a scenario. You can save and share blueprints to recreate scenarios elsewhere.
Bundle
A single unit of data flowing through a scenario. If a trigger returns 10 emails, that's 10 bundles, each processed independently through subsequent modules.
C
Connection
The credentials Make stores to authenticate with an app — typically OAuth tokens or API keys. Reused across all scenarios in your workspace.
Custom App
A user-built integration for an app Make doesn't natively support. Available on Pro and higher plans, requires understanding of REST APIs and OAuth.
D
Data Store
Make's built-in lightweight database. Used for caching API results, deduplicating events, or sharing state between scenarios. Up to 1 million records on paid plans.
Data Transfer
The total size of data moved through scenarios in a billing period. Most plans include unlimited transfer for typical use cases.
E
Error Handler
A fallback path attached to a module that runs when the module fails. Pair with Resume, Rollback, Break, Commit, or Ignore directives.
Execution
One end-to-end run of a scenario. An execution can process many bundles and consume many operations.
F
Filter
A condition between two modules that controls whether bundles continue down the path. Filters cost 1 operation regardless of whether they pass or block.
Function (in expressions)
Built-in operations to transform data inside Make's expression editor — text functions, date functions, math functions, array functions, etc.
I
Integromat
The previous name of Make.com. Rebranded in 2022. All Integromat scenarios were migrated automatically.
Iterator
A flow control module that splits an array into individual bundles for downstream processing. Essential for "for each item, do X" logic.
J
JSON Module
Built-in modules to parse JSON strings into structured data, or convert structured data to JSON. Useful when working with custom APIs.
L
List (vs Search)
Two related action types. List returns all matching records (consumes 1 operation per record returned). Search typically returns only matching records and consumes fewer operations. Prefer Search when possible.
M
Make AI
Make's built-in AI assistant that helps build scenarios from natural language descriptions. Available on Pro and higher plans.
Module
A single step in a scenario. Can be a trigger, action, search, flow control, or transformer. Each module runs once per bundle.
O
Operation
One module run. Make's primary pricing unit. A 5-module scenario processing 10 bundles consumes 50 operations.
P
Polling Trigger
A trigger that checks for new data at regular intervals (e.g., every 15 minutes). Contrast with instant triggers (webhooks).
R
Repeater
A flow control module that runs subsequent modules a fixed number of times. Useful for retry logic or generating multiple variations.
Resume (error directive)
An error handling directive that retries the failed module. Common in error handlers for transient API failures.
Rollback (error directive)
An error handling directive that undoes previous module actions when an error occurs. Used for transactional consistency.
Router
A flow control module that sends bundles down different paths based on filter conditions. Enables branching logic.
S
Scenario
A single automation workflow in Make. Has a trigger and one or more modules. Lives on a visual canvas.
Scheduling
The configuration that determines when a scenario runs — at intervals (every 15 min, hourly, daily) or on demand via webhooks.
Search
An action type that finds specific records matching a query. More operation-efficient than List + Filter for the same goal.
Sleep
A flow control module that pauses scenario execution for a specified duration. Useful for rate-limited APIs.
T
Template
A pre-built scenario shared by Make or the community that you can clone and customize. Different from a Blueprint (which is JSON for import).
Trigger
The event that starts a scenario. Can be polling (checking for new data periodically), webhook (instant on POST), or scheduled (time-based).
V
Variable
A value stored within a scenario for reuse. Different from Data Store (which persists across scenarios). Set Variable and Get Variable modules.
W
Webhook
An instant trigger that activates when an external service POSTs data to a unique URL Make generates. Contrasted with polling triggers.
Workspace
The top-level organizational unit in Make. All your scenarios, connections and team members live in a workspace. Pricing is per-workspace.
Z
Zone
The data center region where your workspace runs (EU or US). Affects latency and data residency for compliance.
Want to learn more?
Now that you've got the vocabulary, dive into our Complete Guide to Make.com for the full picture, or browse our template library to see these concepts in action.