Skip to content
Home

/

Glossary

/

Integration

/

Make (formerly Integromat)

Integration

6 min read

Also: Integromat, Make.com, Make scenarios, Celonis Make, Make Integromat, Make automation

Make (formerly Integromat)

Quick answer

Make (Make.com, called Integromat until February 2022 and owned by Celonis) is a visual no-code platform where you build scenarios that pass data between apps. It bills in credits, usually one per module run, and the Free plan includes 1,000 a month; see every Make plan limit.

Make (formerly Integromat) is a visual automation platform that connects apps and designs complex workflows using a drag-and-drop canvas. It offers more advanced data transformation and branching capabilities than simple trigger-action tools, making it popular for technically-inclined users.

Last verified

What people do with Make (formerly Integromat)

Key facts

Made byMake (owned by Celonis since its October 2020 acquisition of Integromat)
FormerlyIntegromat, renamed Make in February 2022
TypeCloud, no-code integration and automation platform (visual "scenarios")
Billing unitCredits since 27 August 2025; one operation of a non-AI module = 1 credit
Free planYes, with a monthly credit allowance
Self-hostingNo; Make is cloud-only

What is Make?

Make, formerly known as Integromat until its rebrand in 2022, is a cloud-based integration and automation platform that lets users visually design workflows called "scenarios." Unlike simpler trigger-action platforms, Make uses a canvas-based visual editor where you can see the entire data flow, add routers for conditional branching, and handle complex multi-path logic.

How Make Works

Make scenarios consist of modules connected on a visual canvas:

  • Trigger module: Watches for events in a source app (new email, updated record, scheduled interval).
  • Action modules: Perform operations in connected apps — create records, send messages, update databases.
  • Routers: Split the workflow into several routes, each with its own filter, for if/else-style branching.
  • Iterators and aggregators: Loop through arrays of data and consolidate results, essential for batch processing.
  • Data transformers: Built-in functions for text manipulation, date formatting, math operations, and JSON parsing.
  • Make vs. Zapier

    AspectMakeZapier
    Visual editorFull canvas with data flow visualizationLinear step-by-step builder
    BranchingNative router modulesPaths (on paid plans)
    Data manipulationRich built-in functionsLimited without code steps
    PricingCredits (one credit per module run for most apps)Tasks (one task per successful action step)
    Learning curveSteeperGentler for beginners
    Error handlingGranular per-module error routesBasic retry and notification

    Make's Strengths

  • Visual data flow: The canvas shows exactly how data moves through your workflow, making complex logic easier to understand and debug.
  • Advanced transformations: Built-in functions for manipulating text, dates, numbers, and arrays without needing custom code.
  • Pricing granularity: Make bills in credits. Since 27 August 2025 a standard (non-AI) module run, called an operation, costs one credit, while AI modules consume a variable number. Workloads with many cheap steps are often less expensive on Make than on per-task pricing, but every module run counts, including triggers that check for new data and find nothing.
  • Error handling: Dedicated error-handling routes let you define fallback behavior for each module independently.
  • Make's Limitations

  • No built-in browser automation: Like Zapier, Make works through app connectors and HTTP calls. Clicking through a website needs a third-party scraping or browser service connected as an app.
  • Steeper learning curve: The power of the visual canvas comes with complexity that can overwhelm non-technical users.
  • Execution time limits: Scenarios have maximum execution time constraints that can limit long-running workflows.
  • AI is newer: Make has added AI features, including AI agents and AI-assisted scenario building, but they work through its app connectors rather than a live browser.
  • Who Makes Make

    Integromat was founded in Prague, Czech Republic, and was acquired by Celonis, the process-mining company, in October 2020. It was relaunched under the Make name in February 2022. Existing Integromat scenarios were migrated to the new platform, which kept the same core concepts: scenarios, modules, operations and data stores.

    Common Make Problems

    Make's own documentation names a small set of error types that account for most failed runs:

  • RateLimitError: the connected app's API answered HTTP 429 because the scenario sent too many requests. Add a Sleep module between bulk operations, reduce the batch size, or use a Break error handler so Make retries later. See rate limiting.
  • ConnectionError: the third-party service was unavailable (HTTP 502, 503 or 504), typically during maintenance or an outage. Enabling *incomplete executions* lets Make store the failed run and retry it.
  • DataError: the data the module sent did not pass validation in the other app, for example a missing required field or a date in the wrong format. Retrying will not help; the mapping has to change.
  • Scenario deactivated: a scheduled scenario that keeps failing without error handling is switched off, so it silently stops running until someone notices. Error-handler routes (Resume, Ignore, Break, Commit, Rollback) are how you keep one bad record from stopping the whole scenario.
  • Unexpected credit usage: polling triggers consume credits on every check, and an iterator multiplies every downstream module by the number of items. Switching to instant (webhook) triggers and filtering early are the usual fixes.
  • Make vs. Autonoly

    Autonoly also has a visual canvas, but its starting point is an AI agent that drives a real cloud browser from a chat prompt; a finished session can be converted into a reusable workflow. That makes it a better fit for websites without an API. Make is the more mature choice for app-to-app integrations: it has a far larger connector library than Autonoly's native integrations, plus iterators and aggregators for processing lists, which Autonoly's workflows do not have (they have no loop node). See Make alternatives and Zapier vs Make vs n8n vs Autonoly for a fuller comparison.

    Make, formerly Integromat, provides visual, multi-step integration scenarios. Autonoly's equivalents are its visual workflow builder and integrations.

    Why It Matters

    Make showed that a visual builder can handle real complexity: branching, list processing and data transformation. Knowing how it works helps teams decide whether they need a connector-based platform like Make, or a tool that can also work inside websites that have no API.

    How Autonoly Solves It

    Autonoly covers a different gap from Make. Its AI agent drives a real Chromium browser from a chat prompt, so it can log in, click through and extract data from websites that have no API connector, and the session can be turned into a scheduled workflow. Autonoly has fewer native integrations than Make (others are reached through the HTTP Request node) and its workflows have no loop or iterator, so for heavy app-to-app syncing over lists Make is often the better tool; many teams use both.

    Learn more

    Examples

    • Using Autonoly for the part of a process that happens in a supplier's web portal with no API, and Make for the app-to-app steps around it

    • Describing a browser task to Autonoly's agent in chat, then converting the finished session into a workflow instead of building it step by step

    • Keeping a Make scenario that iterates over hundreds of records, because Autonoly workflows have no iterator or loop node

    Frequently Asked Questions

    Make offers a more visual canvas, stronger data transformation and operations-based pricing that is often cheaper at scale. Zapier is easier to learn and has more pre-built app connectors. The best choice depends on how complex your workflows are and how technical your team is.

    Integromat rebranded to Make in February 2022. The platform, features, and team remained the same — only the name and branding changed. Existing Integromat users were migrated to Make automatically.

    Not on its own. Make works through app connectors and HTTP requests; to click through or scrape a website you connect a third-party scraping or browser service. Autonoly includes a real cloud browser, so its AI agent and workflows can click, type, scroll and extract data from websites directly.

    An operation is one run of one module: a trigger checking for data, an action creating a record, a search returning results. Credits are what you buy and spend. Since 27 August 2025 Make bills in credits; for regular, non-AI modules one operation costs one credit, while modules that use Make's built-in AI consume a variable number of credits.

    Usually because it was deactivated after repeated errors with no error handler, because the connection to an app expired and needs re-authorizing, or because the organization ran out of credits for the month. The scenario history shows which run failed and why; adding error-handler routes and enabling incomplete executions keeps a single bad record from switching the whole scenario off.

    Celonis, the German process-mining company, which acquired Integromat in October 2020. Integromat was relaunched as Make in February 2022.

    Related terms, automations and guides

    Where this concept shows up in practice.

    DefinitionAPI IntegrationAPI integration is the process of connecting two or more applications through their APIs so they can exchange data and trigger actions automatically. It eliminates manual data entry by letting systems communicate directly with each other in real time.DefinitionData IntegrationData integration is the process of combining data from multiple disparate sources into a unified, consistent view. It involves extracting data from various systems, transforming it into a common format, and loading it into a destination where it can be accessed and analyzed holistically.DefinitionRate LimitingRate limiting is a technique that controls the number of requests a client can make to a server within a given time window, preventing abuse and ensuring fair resource distribution.DefinitionError HandlingError handling is the practice of anticipating, detecting, and responding to errors in software execution, including catching exceptions, logging failures, and implementing fallback logic to keep automated workflows running reliably.DefinitionOAuth 2.0OAuth 2.0 is the IETF authorization standard (RFC 6749) that lets an app access your account in another service with a scoped token instead of your password. It powers 'Connect your Google account' buttons and nearly every app-to-app integration.DefinitionAI AgentAn AI agent is an autonomous software system that uses large language models to perceive its environment, make decisions, and take actions to accomplish goals with minimal human direction.GuideAutomate Without API: How AI Agents Work With Any Website or AppLearn how AI agents automate websites and apps that don't have APIs. Covers browser-based automation, legacy system interaction, government portals, and how to build automations for any website — no integrations required.GuideWeb Scraping Best Practices: Avoiding Blocks, Bans, and Legal IssuesA comprehensive guide to web scraping best practices. Learn how to avoid IP blocks, deal with CAPTCHAs and anti-bot systems, respect legal boundaries, and where AI browser agents help (and where they don't).

    Stop reading about automation.

    Start automating.

    Describe what you need in plain English. Autonoly's AI agent builds and runs the automation for you — no code required.

    See Features