Automation with Make: what it is and how it is used for SMEs

Make (formerly Integromat until 2022) is a no-code platform that allows you to connect applications and automate workflows visually, without writing code. Basically: define a sequence of steps — "when an email with attachment arrives, download the file, rename it and save it to Google Drive" — and Make automatically executes it every time the trigger occurs.

For one Italian SMEs is one of the most practical tools to start with the automation of business processes: it has a low learning curve, a generous free plan and a visual interface that makes flows understandable even to those who are not technical.

In this guide we see how Make works, how to build an automation, when it is convenient compared to other platforms and how to avoid typical errors.

What Make is and how it works

Make is a platform of no-code integration and automation. The central concept is scenario: a visual sequence of modules that activates on a trigger and then performs cascade actions.

Each scenario consists of:

• Trigger: the event that starts the stream (a new email, a completed form, a timetable, an incoming webhook).
• Modules: the actions to be performed (look for a record on a CRM, send a message on Slack, create a file on Drive, call an API).
• Filters and Routers: conditions that branch the flow in different paths depending on the data.
• Iterators and aggregators: to process arrays of items (e.g. all rows of an Excel sheet) one by one or in bulk.

Make's canvas is visual: the modules are connected by lines, like a flow diagram. This makes workflows readable even to those who haven't built them, which is useful when the team grows or someone is absent.

How to Build a Workflow Make: Step by Step

1. Create a scenario. Log in to make.com, click "Create a new scenario" and the blank canvas opens.
2. Add the trigger. Click the central circle and choose the app where the workflow starts (e.g. Gmail → "Watch Emails"). Configure OAuth credentials and initial filters (sender, subject and label).
3. Add the next modules. Click on the "+" after the trigger to add the first action. Each module asks you what data output from the previous module to use: Make shows a visual "data mapping" in which you select the fields.
4. Add filters or routers if needed. If the flow must behave differently based on the content, enter a filter (condition) or a router (multiple branch) between two modules.
5. Run a test. Click "Run once": Make shows the execution step by step, with the processed data in each module. Identify immediately where it breaks.
6. Activate and schedule. Once tested, activate the scenario and set the polling frequency (every 15 minutes, every hour) or let it react to a webhook in real time.

Data mapping: the key concept

In Make each module exposes its data as "variables" that the next module can use. If the trigger retrieves an email, you will have available {{1.subject}}, {{1.from.email}}, {{1.body.text}} and so on. Understand this and understand Make: 90% of configuration problems arise from not mapping the right field.

Make for SMEs: practical examples

Example 1 consulenza Consulting firm: new clients from form to CRM

A tax consulting firm in Milan uses a Typeform form on the site to collect initial requests. Before, someone would copy the data by hand into the CRM (HubSpot) and send the confirmation email. With Make:

1. Trigger: New Typeform response.
2. Create or update contact on HubSpot with form data.
3. Send a personalized email to the potential customer (Gmail).
4. Adds a line on Google Sheets used for weekly tracking.

Time saved: about 5-10 minutes in contact. With 30-40 contacts per month, it's hours.

Example 2 — E-commerce: new order → warehouse update and notification

An e-commerce of handmade products on WooCommerce receives orders from different channels. Make:

1. Trigger: new WooCommerce order.
2. Decrement the stock on a Google Sheets sheet used as a plain stock.
3. If the stock falls below the threshold, send an alert on Slack to the purchasing manager.
4. Create a draft shipment on Sendcloud.

Result: fewer over-sale errors, less forward-back on WhatsApp to report low stocks.

Example 3 — Garage: service reminders

A workshop with 400 active customers wanted to send reminders by cutting without having to call one by one. Make reads a Google Sheet with date cutting and phone number, and for each line with cutting in the next 15 days sends an SMS (via Twilio or an Italian SMS gateway). The scenery runs every day at noon.

This type of automation for customer follow-up has a direct impact on the rate of return.

If your team is already using Azure, you should also include the preview of Logic Apps Automation and its free shares. The evaluation must separate execution plan, grant, connectors and region: the conditions are not interchangeable with those of Make.

Make vs Zapier vs n8n: which one to choose

For an in-depth comparison between the three platforms see Make vs Zapier vs n8n. For those who rate only the first two, automation with Zapier shows the strengths of the alternative.

Integrations most used in Italian SMEs

Make has native connectors for most of the tools used by Italian SMEs:

• Email and Communication: Gmail, Outlook, Slack, Microsoft Teams, WhatsApp Business (via official API).
• Google Workspace: Sheets, Drive, Docs, Calendar, Forms.
• CRM and Sales: HubSpot, Salesforce, Pipedrive, Monday.com, Airtable.
• E-commerce: Shopify, WooCommerce, Prestashop.
• Italian Billing: Fatture in Cloud (native connector), other management software via HTTP/API.
• AI: OpenAI/ChatGPT, Anthropic Claude, Google AI — to add intelligent processing to streams.

For managers who do not have a native connector, Make has a generic HTTP module: if the software exposes a REST API, you can call it directly. It is the way many niche Italian ERPs integrate.

Make and AI: Hybrid Flows

One of the most useful developments is combining Make with AI modules. For example: an agency receives email enquiries → Make extracts the email text → passes it to an OpenAI module with specific instructions (classify the request, extract key data and suggest a response) → the result is entered into the CRM or sent to the salesperson on Slack.

This type of hybrid workflow is more sophisticated than simple trigger-action automation: it combines AI Automation with data orchestration. It does not require a full AI agent, but adds intelligence to the steps that need it.

When to use Make and when to avoid it

Platform monitoring can use the new Event Subscriptions by Make, in beta with conditions related to the plan. A deactivated subscription does not append events; a temporarily unreachable endpoint follows documented retry instead. The receiver must handle delivery, duplicates and recovery.

Mistakes to Avoid

• Automating immediately without mapping the process first. If you do not know exactly what goes in, what comes out and who is responsible for checking, the automated workflow reproduces the chaos. First paper and pen, then Make.
• Not handling errors. Make has an error handling system (alternative routes in case of failure) that most users ignore. A form that silently fails can corrupt data for weeks before anyone notices.
• Forgetting personal data. Passing customer emails, phone numbers or accounting data through dozens of apps without a signed DPA is a GDPR violation. Art. 28 imposes the contract with each external data controller. Consult a legal expert before putting flows into production with PII.
• Not monitoring operation usage. Make counts each action as "operation". A stream that iterates over 500 lines uses 500 operations per execution. Without monitoring the plan runs out and workflows freeze.
• Abandoning workflows without documentation. In six months you won't remember why that filter was set like this. Use form names and Make notes to document non-obvious choices.

How to apply it in the company

1. Identify the most manual and repetitive process. Hand-transcribe data from email to CRM? Create reports by copying data from multiple sources? That task is the number one candidate.
2. Check that the apps involved have a Make integration. Go to make.com/en/integrations and search for your apps. If they are missing, check if they have REST or webhook APIs.
3. Build the minimum workflow. Start with the most common case, not the exception. 20% of cases covering 80% of volumes are version 1.0 to be tested.
4. Head with real but not critical data. Use a test account or parallel pipeline. Do not put an untested workflow into production on real data.
5. Measure before and after. Hours spent per week, errors recorded, response time to customer. Without measure there is no ROI, just impression.
6. Keep and monitor. Set Make error notifications to receive an alert on email or Slack when a stream fails. Assign a person responsible for maintenance.

To understand what other processes lend themselves to automation in your company, the guide what to automate in an SME is a good place to start. If you are interested Document Automation or the Automatic CRM Management, Make is often the glue that joins the pieces.

Conclusion

Automation with Make It does not require developers or high budgets: it requires clear processes and the willingness to invest a few hours in the initial configuration. For an Italian SME working with Gmail, Google Sheets, a CRM and a management system, Make is often the most accessible tool to stop doing manual copy-paste and start running streams on your own.

The limit is not technology: it is having a process stable enough to automate. If steps change every week, the workflow will break every week. If the process is solid, an automation Make can recover hours every month with a few euros of license.

If you want to go from testing with ChatGPT to an AI system integrated into business processes, Giallo Studio custom designed agents and automations.