Tauseef FayyazA to Z
Glossary
Every concept in this sheet, plus the smaller terms it uses. Select a concept to open its card.
A
- Action
- A step that does something after the trigger: create a CRM contact, send a message, add a row, call an API.
- API key
- A long secret string that identifies the caller to an API, usually sent in a header.
C
- Connections and the HTTP app
- Connections store access to apps through OAuth or keys.
- Credits
- The billing unit on Make.
D
- Data mapping
- Choosing which output of an earlier step fills each input of a later step, often with a small transformation such as trimming, lowercasing or a fallback value.
- Data store
- A small built-in table in Make with a key per record and a data structure you define, which scenarios can add to, search, update and delete from.
H
- HTTP request
- A call to an API with a method (GET reads, POST creates, PUT or PATCH updates, DELETE removes), a URL, headers and often a JSON body.
I
- Iterators and aggregators
- An iterator splits one bundle holding an array into many bundles; an aggregator collects many bundles back into one, such as an array, a text block or a CSV.
J
- JSON
- The text format apps use to exchange data: objects in curly braces with named fields, arrays in square brackets, and values that are strings, numbers, booleans or null.
M
- Mapping and functions
- Mapped values appear as pills such as
1.email(module 1, field email). - Modules and bundles
- Each module outputs bundles, one per record, and the next module runs once for every bundle it receives.
O
- OAuth 2.0
- A flow where the account owner approves limited permissions, called scopes, and the tool receives a token that can be refreshed or revoked without sharing a password.
R
- Rate limit
- A cap on how many requests an API accepts in a time window, such as 100 per minute.
- REST API
- An API that exposes data as resources at URLs, such as /contacts/123, and uses HTTP methods to act on them.
- Routers and filters
- A router splits a scenario into routes; a filter on each route lets through only bundles that meet its conditions.
S
- Scenario
- A Make workflow: a chain of modules on a canvas, started by a trigger module, a webhook or a schedule.
T
- Trigger
- The event that starts a workflow: a form submitted, an email received, a record created or a schedule reached.
W
- Webhook
- An HTTP request an app sends to your URL when an event happens, carrying the event data as JSON.