Technology profile
Make
- What it is
- A visual no-code automation platform, formerly known as Integromat, where workflows are called scenarios.
- Type and licence
- Commercial cloud service (SaaS) with a subscription; it cannot be installed on your own server.
- Good for
- Processes with many conditions and branches, processing lists of data, teams that want to see the workflow as a diagram.
- Less suited to
- Strict requirements for hosting on your own infrastructure, or very complex logic better suited to dedicated software.
- Alternatives
- n8n, Zapier, custom-built integrations.
- How we use it
- For automations between cloud apps, with clear rules, error handling and documentation.
Make.com is a no-code automation platform where you connect your company's apps through a visual diagram called a scenario. Each block in the diagram (a module) represents an action in an app, and data flows automatically from one block to the next. The platform was previously known as Integromat and runs exclusively in the cloud.
For a manager, the promise is simple: repetitive tasks, such as copying data from a form into the CRM, sending confirmations or updating a reporting spreadsheet, can be done automatically, without writing an application. Below we explain how Make works, what it does well, how the cost is calculated and where the limits appear.
In short
Make is good for visual automations with many conditions, branches and list processing. It is a cloud service, with a cost tied to the number of steps executed. It works best when the process is clearly defined, the workflows are documented and someone keeps an eye on errors.
What no-code automation means
“No-code” means that instead of writing instructions in a programming language, you choose apps and actions from a list, link them together and fill in fields. The platform handles connecting to the apps, authentication and moving the data.
That does not mean “no technical thinking”. You still need to understand what data you have, what format it is in and what should happen when something goes wrong. The difference is that an organised person with good logic can build and maintain useful workflows without being a programmer.
How Make.com works: scenarios, modules and routes
- The scenario is the complete automation, drawn as a diagram from left to right.
- Modules are the blocks in the scenario: a trigger (for example, “new order in the store”) and the actions that follow (“create the invoice”, “send an email”).
- Routers split the flow into several branches, each with its own actions.
- Filters, placed on the links between modules, let data through only if it meets a condition.
- Iterators and aggregators work with lists: they split an order into its individual products or combine several rows into a single summary.
- Scheduling sets when the scenario runs: at fixed intervals or immediately, when it receives data through a webhook (an automatic call sent by another app).
A conceptual example: for every new order in an online store, the scenario checks the payment method. If the payment was made online, it issues the documents and notifies the warehouse; if it is cash on delivery, it sends the order for a confirmation call. All the logic is visible on a single diagram, which helps a lot when explaining the process to the team.
Beyond modules, Make offers tools for transforming data: functions for text, dates and numbers, as well as internal data stores where you can keep information between runs, for example the last order number processed. Scenarios can be organised into folders, and connections to apps are set up once and reused across several scenarios.
What you can automate with Make
- Capturing leads from forms and ads into the CRM, with assignment to the right salesperson.
- Syncing orders, customers or stock between an online store and other systems.
- Periodic reports built automatically in spreadsheets and sent by email.
- Internal chat notifications for important events: a payment received, an urgent ticket, a negative review.
- Processing files received by email, saving them to an archive and logging them in a spreadsheet.
A simple test for deciding whether a process is worth automating: it repeats often, follows the same rules every time and involves moving data between apps, not human judgement. Processes that change from case to case or depend on conversations with the customer are weaker candidates, at least to begin with.
If an app has no dedicated module in Make, you can still use the HTTP module to call its application programming interface (API) directly. At that point, though, you are entering technical territory, where it helps to have someone who understands API documentation.
AI steps in Make scenarios
At the time of writing, Make lets you integrate language models from popular AI providers, as well as the platform's own AI features. In practice, a scenario can classify a request, extract data from an email, summarise a text or draft a proposed reply. The features change often, so check the official documentation.
Important limit
The AI step can make mistakes or respond differently to the same request. For actions that affect customers or money, add a verification stage: a filter with clear rules or approval by a person before execution. In addition, data sent to the AI model reaches yet another provider, which must be included in your data protection assessment.
Error handling in Make
One of Make's strengths is control over errors. On each module you can attach an error-handling route that decides what happens if the step fails: ignore the error and continue, replace the result with a fallback value, stop the scenario, or keep the incomplete execution so it can be resumed later, once the problem has been fixed.
The execution history shows what data went into and came out of each module, which makes tracking down problems much easier. However, these tools only work if you configure them. A scenario with no error handling and no notifications can fail silently for days.
Practical tip
For every important scenario, set up an error notification to a named person and agree what that person does when they receive it. Also check periodically for scenarios that have not thrown errors but have not run for a long time.
How much does Make.com cost? How usage is calculated
We do not give figures, because plans and prices change; check the official pricing page. What matters is the logic: Make measures usage by the steps executed in scenarios, called operations or credits depending on the plan. Every module that runs consumes usage, and a scenario scheduled to check frequently for new data can consume it even when it finds nothing.
- Count how many runs the scenario has per month and how many modules execute on each run.
- Prefer webhook triggers, where the app allows it, instead of very frequent checks.
- Place filters as early as possible in the scenario, so irrelevant data does not pass through every step.
- Factor in the time to build, test and maintain, which often matters more than the subscription.
Your data in Make: hosting and GDPR
Make is a cloud service, so data passing through scenarios is processed on the provider's infrastructure. A hosting region is usually chosen when the organisation is created; check the available options and choose an EU region where possible. For GDPR, Make usually acts as a data processor, so check the data processing agreement, the list of sub-processors and how long the execution history, which contains the processed data, is kept. This information is valid at the time of writing (October 2026); for your company's specific situation, consult the guidance from ANSPDCP (the Romanian data protection authority) and a specialist. This article is for information only and is not legal advice.
Make's limits and when it isn't the right fit
- It cannot be installed on your own server. If you have strict requirements for data to stay on the company's infrastructure, a solution such as self-hosted n8n or a custom integration is a better fit.
- Large scenarios, with dozens of modules and many routes, become hard to read and change without careful organisation.
- Working with lists, iterators and aggregators takes time to learn; mistakes here can multiply usage unexpectedly.
- Moving scenarios to another platform effectively means rebuilding them.
- For complex business logic with its own user interface, a no-code platform does not replace dedicated software.
Make, n8n or Zapier?
Zapier is usually the easiest to start with for short workflows and has a very broad catalogue of apps. Make offers more visual control for scenarios with branches and data processing. n8n stands out for its self-hosting option and code built into the workflow, at the price of greater technical responsibility. We compare the three platforms in detail in a separate guide.
How we use Make at WEB-AZ
We work with Make for automations between cloud apps, when the process has clear rules and the client's team wants to be able to understand the workflow visually. We start from the real process, build the scenario with error handling and notifications, test it with real data and document it. If Make is not the right choice for your requirements, we tell you openly and suggest the alternative.
Next steps