Lyron

Make.com · Visual workflows · EU

Make.com: visual automation with European roots.

Make.com (formerly Integromat) is a visual automation platform distinguished by its intuitive drag-and-drop interface and powerful data manipulation capabilities. As a European company based in Prague, it offers data protection advantages and is ideal for data-intensive workflows and complex transformations. As a Make.com agency, Lyron supports you from consulting and implementation through to ongoing operations.

  1. European provider, EU data centers
  2. Over 3,000 app integrations
  3. Powerful data transformation
  4. Transparent operations usage
Team working on several laptops at a shared table – a symbol for connected apps and workflows

When Make.com is the right choice

  1. Visual workflow planning

    Make.com displays workflows as visual diagrams that make data flow understandable at a glance. Branches, loops, and parallel paths are intuitively recognizable – ideal for complex processes that require more than simple trigger-action chains.

    Example: A workflow that simultaneously sends data to CRM, email tool, and accounting, with each path containing its own transformation logic.

  2. Powerful data transformation

    Built-in functions for JSON operations, arrays, text manipulation, and mathematical calculations directly in the workflow. No external scripting needed – complex data structures can be prepared directly in the interface.

    Example: Filter and aggregate API responses with nested arrays, transforming them into a different format for the target system.

  3. European provider & GDPR

    Make.com is headquartered in Prague and offers data centers in Europe. For companies with strict data protection requirements, this is an advantage over US-based alternatives like Zapier.

    Example: Processing customer data in EU data centers with appropriate contract clauses.

  4. Broad app integration

    Over 3,000 pre-built app integrations, including many European services. For apps without native integration, any HTTP API can be connected – with visual mapping of request and response data.

    Example: Connecting a self-developed internal API via HTTP modules with custom authentication flow.

How a scenario runs in Make

Using incoming email attachments as the example: five steps from the mailbox to logged filing. The scenario history shows, with sample data, which decision was made for each attachment.

  1. Step 01 · Trigger

    Watch the mailbox

    The scenario listens to one approved shared mailbox, never to a person's whole correspondence. Sender, subject, message body and each file are read separately.

  2. Step 02 · Filter

    Check the file and make it readable

    File type, size and protection status are checked, archives are unpacked, scans and photos go through text recognition. Signature images drop out here, before they use up further operations.

  3. Step 03 · Router

    Determine the attachment type

    Sender, subject and above all the text inside the document produce the classification: invoice, delivery note, form, photo or signature graphic. A router sends each attachment type down its own path.

  4. Step 04 · Mapping

    Match the case and rename

    Customer number, job number or order number are read from the document and validated against your leading system. Only once that link holds does the file get its name under your scheme.

  5. Step 05 · History

    File and log

    The destination system receives the file and its key data, and the message is marked as processed. Every decision is logged with its rule number in the history; anything doubtful becomes a task instead of a misfiled document.

Make · Scenario history Sample data
makeHistory
  1. Mailbox
  2. Check
  3. Classify
  4. Match
  5. History

Scenario: file email attachments

Mailbox
invoices@your-company.example
Run
Tuesday morning · 4 messages · 6 attachments

Decision per attachment

  • 08:12INV-4471.pdf · R3 → case 8820Filed
  • 08:12logo-signature.png · R1 signature imageDiscarded
  • 09:04scan001.pdf · R7 → goods receipt 2026Filed
  • 09:41Detail_North_v2.dwg · R0 → review folderReview
  • 10:26INV-5518.pdf · R3 → case 9014Filed
  • 10:26Invoice_May_final(1).pdf · R4Duplicate
Rule R0No rule is defined for .dwg – instead of filing, the scenario raises a task for the project lead.

Example from our building block Email attachment automation

Typical Make.com use cases

  • Data synchronization between systems

    Merge data from multiple sources, clean it, and keep it synchronized. With bidirectional sync logic and conflict resolution.

  • Document generation

    Combine data from various sources, insert into templates, and generate PDFs, Word documents, or other formats.

  • Email automation & parsing

    Parse incoming emails, extract attachments, structure data, and forward to various systems – with regex and pattern matching.

  • Lead enrichment

    Supplement lead data with external sources (company databases, LinkedIn, Clearbit), qualify, and hand over to sales tools.

  • E-commerce workflows

    Synchronize orders, update inventory, create shipping labels, and notify customers about status changes.

  • Reporting & data aggregation

    Collect data from different tools, aggregate, calculate, and send as reports or store in dashboards.

  • Chatbot integrations

    Connect chatbots to backend systems, retrieve data from CRM, create tickets, and generate automated responses.

  • Webhook orchestration

    Receive webhooks from various services, validate data, transform, and forward to other systems with error handling.

Advantages & challenges of Make.com

Make.com is strong when visual overview and data preparation matter. Where the platform reaches its limits, we tell you openly – and recommend a different tool if needed.

n8n vs. Make compared side by side

Advantages

  • Intuitive visual interface

    Display and edit workflows as flowcharts. Less abstract than code-based approaches, but more powerful than simple list views.

  • Strong data manipulation

    Extensive functions for filter, map, reduce, string operations, and JSON transformation directly in the builder – without external tools.

  • Transparent operations usage

    Every executed operation is visible and calculable. No billing surprises, as each step is cost-transparent.

  • European server option

    Option to run workflows on EU servers. Important for GDPR compliance and companies with data residency requirements.

Challenges

  • Learning curve for complex workflows

    Simple flows are quickly created, but complex logic with iterators, aggregators, and nested branches requires practice.

  • Costs at high volume

    Usage is based on operations, which can quickly increase with data-intensive workflows. At high volume, this can be more expensive than flat-rate models.

  • No self-hosting

    Unlike n8n, there is no on-premise option. Data is processed in the Make.com cloud, which can be a deal-breaker for some companies.

  • Error handling limitations

    Error handling is possible but less flexible than n8n. Complex retry strategies or rollbacks require workarounds.

Best practices for Make.com workflows

Clean structures are crucial for maintaining overview as complexity grows. These practices help build maintainable workflows.

  1. Consistent naming

    Give modules descriptive names instead of default labels. "Create contact in HubSpot" says more than "HubSpot - Create a contact". Document the intent of each step.

  2. Group modules

    Use routers and notes to group related logic. Color coding or comments help understand the purpose of complex sections.

  3. Implement error handling

    Configure break handlers and directives for every critical module. Define what happens with API timeouts or errors – ignore, retry, or abort.

  4. Folders & structure

    Organize scenarios in folders by team, process, or system. A clear folder structure prevents chaos as the number of workflows grows.

Make.com licensing overview

Make.com uses an operations-based pricing model. An operation generally corresponds to one executed module. Costs depend on monthly usage and required features.

Free

1,000 operations/month, limited app selection, no scheduled execution. Good for testing simple flows.

Core

10,000+ operations, all apps, scheduling, webhooks. The typical entry point for productive workflows.

Pro / Teams

More operations, team features, extended permissions, dedicated support. For growing teams.

Enterprise

Unlimited operations, SSO, extended security features, SLA support. For large organizations.

Make.com + Lyron

We implement Make.com workflows that not only work but remain clear and maintainable. From initial planning to documentation, we focus on clean structures.

  1. Clear structure

    Organized workflows with documentation

  2. Knowledge transfer

    Your team learns the platform

  3. Cost optimization

    Efficient workflows with fewer operations

Frequently asked questions about Make.com

We build individual workflows from €490; larger automation projects range from €890 to €5,900. Ongoing support with monitoring starts at €290 per month – entry prices and the process are on our pricing page.
The free plan with 1,000 operations per month costs nothing and is good for testing. Paid plans start in the low double digits per month and scale with operations (as of July 2026). We help you design efficient workflows and choose the right plan.
Make.com is headquartered in Prague and can run workflows in EU data centers – an advantage over US-based providers. There is no self-hosting option, though; if data must never leave your own infrastructure, self-hosted n8n is the better fit.
Integromat is the former name of Make.com: the platform was rebranded, with the same Prague-based provider behind it. Features and app integrations have been expanded continuously since the rebrand.
Make.com stands out with its visual interface, strong data transformation and EU data centers – ideal for data-intensive workflows. Zapier offers the largest app selection for simple, linear automations; n8n is the right choice for complex logic and self-hosting requirements. We recommend the tool that fits your use case.

Free consultation · 30 minutes

Your Make scenario, built to stay clear.

Tell us about your process. In the intro call we clarify whether Make.com fits, how to keep operations usage in check and when a different tool would be the better choice.

  • Free & no obligation
  • 30 minutes via Google Meet
  • First view of effort & benefit
Team working together on a tablet and discussing the next steps