Automation Glossary: Zaps vs Scenarios vs Workflows (Triggers, Actions, Nodes)

Why the terms are confusing

Zapier, Make and n8n do the same basic job, but each one invented its own vocabulary. A "Zap", a "scenario" and a "workflow" are the same thing. "Tasks", "credits" and "executions" are all billing units, but they measure different things, which is why prices are hard to compare.

Use this glossary as a translation table. We reuse it in every migration guide on this site.

The core translation table

Concept	Zapier	Make	n8n
One automation	Zap	Scenario	Workflow
One step	Step (trigger or action)	Module	Node
What starts it	Trigger	Trigger module (first module)	Trigger node
One record moving through	(implicit)	Bundle	Item
Billing unit	Task = one successful action	Credit = one module run	Execution = one full workflow run
Branching	Paths	Router	IF / Switch
Condition to continue	Filter	Filter (on a route)	Filter / IF
Loop over a list	Looping by Zapier	Iterator	Loop Over Items (or automatic per-item)
Combine a list	Formatter / Digest	Aggregator	Aggregate / Merge
Wait	Delay	Sleep	Wait
Scheduled start	Schedule by Zapier	Scheduling settings	Schedule Trigger
Receive data from any app	Webhooks by Zapier	Custom webhook	Webhook
Call any API	Webhooks / API Request	HTTP module	HTTP Request
Custom code	Code by Zapier	(limited; custom functions on Enterprise)	Code node (JavaScript or Python)
Saved app login	Connection	Connection	Credential
Data storage	Tables / Storage	Data store	Data tables or an external DB
Error handling	Autoreplay, error notifications	Error handler routes	Error Trigger workflow, retry on fail

Trigger terms

• Trigger: the event that starts an automation.
• Polling trigger: the tool checks an app on a schedule ("anything new since last time?"). Cheap and universal, but delayed by the polling interval.
• Instant trigger / webhook: the app pushes data the moment something happens. Faster, but the app must support it.
• Schedule trigger: starts at a fixed time, for example every Monday at 9:00.

Action terms

• Action: a step that does something, such as create, update, send or delete.
• Search action: finds an existing record (for example, "find contact by email") so you can update instead of duplicating.
• Upsert: create the record if it does not exist, update it if it does.

Data terms

• Field mapping: telling a step which data from earlier steps goes into which field.
• Expression: a formula inside a field. In n8n, {{ $json.email }}; in Make, {{1.email}}.
• JSON: the text format almost all automation tools use to pass data. Learn to read it and every tool gets easier.
• Array: a list of things, such as order line items. Arrays are why iterators and loops exist.

Billing terms explained with one example

Imagine a workflow: trigger, then 4 steps, running 1,000 times a month.

Tool	What it counts	Monthly usage
Zapier	Each successful action	4,000 tasks
Make	Each module run, including the trigger	About 5,000 credits
n8n Cloud	Each full run	1,000 executions
n8n self-hosted	Nothing	Unlimited

This is why the same automation can cost $0, $10 or $100+ depending on the tool. See real pricing compared for full numbers.

Next steps

• Moving between tools? Use the Zapier and Make to n8n mapping cheat sheet.
• Starting fresh? Read what is n8n.