Glossary
Short definitions for the words a recipe uses the first time. One or two sentences each.
Webhook
A notice an app sends to Make or n8n when something happens, such as a payment. It often carries only an id, and the flow then asks the app for the rest.
API
The door an app opens so another app can read or write data without you clicking around the screen. Your everyday username and password are not enough.
Token or API key
A long secret the app gives you so the flow can act as you. Do not paste it into a chat or a shared sheet. Recipes call this a token, a key, or an API key.
HTTP
The way two apps talk over the internet. In Make it is the HTTP module. In n8n it is the HTTP Request node. Recipes use it when there is no ready-made app.
JSON
The shape the data usually arrives in: names and values. If a value is missing, leave it empty. Do not invent it.
Module or node
One block in the flow. Make calls it a module. n8n calls it a node. One block watches, another writes a row, another sends a message.
Trigger
The block that starts the flow: a time of day, a new email, or an incoming notice. Without it, the flow never hears that something happened.
Scenario or workflow
The whole flow, from the first block to the last. Make calls it a scenario. n8n calls it a workflow.
WhatsApp template
Text Meta has to approve before your business can open a chat. It is not a message you type on the spot, and it does not send from the phone app.
OAuth
The allow-access screen where you sign in with Google or another account. The password stays with that account. The usual button is Sign in with Google.
Credentials
The saved permission the flow uses to enter an app: a Google connection, a bot token, or an API key.
Credits or operations
What Make counts when a module does something. Make now calls them credits. Most actions use 1, and the free plan includes 1,000 a month. When they run out, scenarios pause.