How Automating with Make Eliminates Manual Data Transfer
Every day, businesses repeat the same operations: moving orders from an online store to CRM, updating stock levels in 1C, sending invoices to clients. On average, these tasks consume 2–4 hours daily. As volumes grow, N+1 database queries only worsen the situation. Manual entry errors can lead to losses of up to 5% of revenue. We configure Make (formerly Integromat) scenarios that handle all the routine, freeing employees' time and reducing operational costs.
On one project, we automated synchronization between Shopify, Freshdesk, and Telegram. Previously, a manager manually copied orders from Shopify to Freshdesk and sent notifications in Telegram. After implementing Make, the processing time per order dropped from 180 seconds to 2–3 seconds — 60–90 times faster. Error rate fell to zero.
Which Business Processes Can You Automate with Make?
Make fits any task that involves data transfer between services: CRM, email, messengers, databases, and APIs. Unlike Zapier, Make supports branching (Router), iterators (Iterator), and aggregators (Aggregator). This allows processing arrays of thousands of records with individual conditions. For example, when syncing a product catalog with marketplaces: one scenario can break down an array, check prices, update stock, and compile a report — all without human intervention. Make also offers more flexible pricing: up to 1,000 operations per month on the free plan — 10 times more than Zapier (only 100). The HTTP module lets you integrate any service's API, even legacy systems.
How Do the HTTP Module, Iterators, and Aggregators Work?
The HTTP module sends requests to any REST API. Example POST request configuration:
{ "url": "https://api.example.com/orders", "method": "POST", "headers": [ { "name": "Authorization", "value": "Bearer {{1.api_token}}" }, { "name": "Content-Type", "value": "application/json" } ], "body": { "orderId": "{{1.id}}", "customer": { "email": "{{1.customer.email}}", "name": "{{1.customer.first_name}} {{1.customer.last_name}}" }, "amount": "{{1.total_price}}", "currency": "RUB" } } An Iterator splits an array into individual bundles — each element goes through a chain of modules. An Aggregator collects results into a single response. This is essential for handling shopping carts or product lists. Example processing an items array from an order:
[Webhook: new order with items[]] │ [Iterator: split items[] into bundles] │ (one by one items[i]) [Lookup: find product in DB by SKU] │ [HTTP: decrease stock quantity] │ [Aggregator: collect results] │ [Email: final report] Step-by-step scenario setup with a webhook and iterator:
- Create a new scenario in Make and select the Webhook trigger.
- Copy the webhook URL and configure the external service to send POST requests.
- Add an Iterator module, pointing to the array from the request body.
- Inside the iterator, configure an HTTP request to your API for each array element.
- Add an Aggregator module to bundle results, choosing source data and structure.
- Set up a notification module (e.g., Email) to send the final report.
How to Handle Errors in Make Scenarios?
Make provides an Error Handler Module — a special branch executed on failure. According to Make documentation, the Error Handler supports four strategies:
- Ignore — skip the error, continue processing next bundles.
- Break — stop the current bundle, move to next.
- Retry — retry the module up to 5 times with configurable delay.
- Rollback — undo changes in supporting modules.
This variety gives 4 times more flexibility compared to Zapier, which only offers Retry. We always configure error notifications to Telegram or Slack so you know about issues instantly. This reduces downtime and minimizes financial losses.
Automation Setup Process and Timelines
| Stage | Duration |
|---|---|
| Audit and design | 1–2 days |
| Implementation and testing | 2–4 days |
| Documentation and training | 1 day |
Pricing is tailored to scenario complexity. A simple scenario with 3–5 modules and one condition takes 1–2 days; a scenario with iterator and aggregator takes 3–5 days; a turnkey solution with training and documentation takes up to 7 days.
Comparison: Make vs. Zapier
| Feature | Make (Integromat) | Zapier |
|---|---|---|
| Operations per month (free) | 1,000 | 100 |
| Active scenarios (free) | 2 | 5 |
| Module types | HTTP, iterator, aggregator, router | Linear actions only |
| Branching | Router | No |
| Error handling | 4 strategies | Retry only |
What Is Included in the Work
- Scenario documentation: description of each module, logic, and variables.
- Access configuration: connecting to service APIs, creating webhooks.
- Testing: verification with test data, edge case handling.
- Employee training: demonstration of scenario operation, instructions for adding new data.
- Warranty support: 2 weeks after launch to fix any issues.
Contact us to assess automation for your process. Get a consultation — we'll analyze your routine and propose a scenario that saves hours of your team's time. Order setup now — the investment pays off through reduced manual labor.