WorksheetsQuiz Recap - Lesson 2
Total questions: 10
Worksheet time: 5mins
In the context of automation tools, what is the main difference between Make.com and Zapier for complex multi‑step workflows?
Make.com only supports single‑step workflows, Zapier supports multi‑step
Make.com supports visual branching with routers and advanced logic, Zapier is more linear and limited in branching
Zapier supports more complex data transformations, Make.com only sends simple notifications
Zapier can only connect two apps at a time, Make.com can connect unlimited apps
Why is Make.com’s operations‑based pricing often more economical than Zapier’s task‑based model for complex automations?
Operations in Make.com are always free, tasks in Zapier are always paid
Make.com charges only per month, Zapier charges per user
Complex workflows use many actions; Make.com prices operations more cheaply at scale than Zapier prices tasks
Make.com sets a strict cap on scenario length, Zapier has no caps
In Make.com, what is a module and how does it relate to a scenario?
A module is a complete automation; a scenario is one step inside it
A module is a single step (trigger, action, search, or tool) and a scenario is the chain of modules that forms the workflow
A module is only used for error handling; a scenario is for normal actions
A module is just a visual icon; it has no functional role in a scenario
What is the difference between Tools modules and Apps modules in Make.com?
Tools modules require API keys; Apps modules never need authentication
Tools modules transform or manipulate data without external connections; Apps modules interact with external services via connections
Tools modules are only for triggers; Apps modules are only for actions
Tools modules are only available on paid plans; Apps modules are free
How does an instant trigger differ from a polling trigger in Make.com?
Instant triggers run only once per day; polling triggers run every second
Instant triggers start the scenario as soon as the event happens, while polling triggers check for new data at intervals and may introduce a delay
Polling triggers are cheaper because they only consume operations when new data arrives
Polling triggers are only available for Google apps, instant triggers only for Slack
In Make.com, what is a bundle?
A collection of modules grouped into a scenario
A unit of pricing that counts how many operations you have left
A container holding related data items that a module processes and passes along as input or output
A special error‑handling object created when a module fails
Why is the rule of thumb “only the trigger generates the first bundles; other modules just transform existing bundles” important?
Because only the trigger consumes operations; other modules are free
Because it clarifies that data enters the scenario once, and downstream modules reuse and transform those data, which affects both data flow understanding and how many operations are counted
Because it means you can add unlimited triggers in one scenario
Because downstream modules cannot access data from the trigger
On which dimensions is n8n typically preferred over Make.com, despite Make’s usability advantages?
When no integrations are needed and only local files are used
When teams want self‑hosting, deeper control over infrastructure, and are comfortable with a more technical, developer‑oriented tool
When non‑technical users need the simplest possible interface and templates
When you must avoid any open‑source components for compliance reasons
Which combination best describes key reasons for choosing Make.com over its competitors?
Requires coding skills, cheapest on the market, no visual builder
Visual builder for complex logic, operations‑based pricing that scales well, rich data‑manipulation modules and strong integrations with tools like Google, Notion, and Slack
Only single‑step automations, but with unlimited free usage
Focuses only on database storage, not on connecting SaaS apps
In the lead‑notification practical case (Google Sheets → Gmail → Slack), which statement is most accurate?
The trigger should be Slack; Google Sheets and Gmail are only used for notifications
The trigger is a Google Sheets “Watch Rows” module, Google Sheets is the data source, and Gmail/Slack act as notification channels that can be extended with additional actions (e.g. writing to a CRM)
The trigger is Gmail; Google Sheets is only updated manually
Slack acts as both trigger and data source; Google Sheets is not part of the scenario
