Make (Integromat)

Overview

Make, originally launched as Integromat in 2016 and later rebranded, is a visual platform designed for building, designing, and automating workflows. It operates as an integration platform as a service (iPaaS), allowing users to connect otherwise disparate applications and services to create automated data flows and task sequences. The platform's core offering is a drag-and-drop interface where users construct 'scenarios' — automated sequences of tasks triggered by specific events. These scenarios can range from simple data transfers between two applications to complex multi-step workflows involving conditional logic, error handling, and parallel processing.

Make is positioned for a broad audience, including technical users, business analysts, and developers seeking to automate operational processes without extensive coding. Its visual builder abstracts underlying API interactions, enabling the creation of integrations by configuring modules and their connections. For more advanced use cases, the platform supports custom webhooks and HTTP modules, allowing integration with APIs not natively covered by its pre-built application connectors. This flexibility extends to programmatic management of scenarios and organizations via the Make API itself.

The platform's utility is demonstrated in use cases such as synchronizing customer data across CRM and marketing automation platforms, automating report generation from various data sources, or orchestrating responses to specific events in a cloud environment. For example, a common scenario might involve capturing new form submissions, enriching the data, and then pushing it into a database and a notification system. Make's infrastructure is designed to handle varying loads, with scenario execution managed to ensure data integrity and workflow completion. The company maintains compliance certifications including SOC 2 Type II, GDPR, and ISO 27001, addressing data security and privacy requirements for enterprise adoption.

While Make offers a visual, low-code approach, developers can leverage its HTTP/SOAP modules and JSON parsing capabilities for more granular control over data manipulation and interaction with custom or less common APIs. This blend of ease-of-use and technical depth positions Make as a tool for both rapid prototyping of integrations and deployment of production-grade automation. The platform is owned by Celonis, a process mining and execution management firm, indicating a strategic alignment towards integrating automation with process optimization initiatives.

Key features

• Visual Workflow Builder: A drag-and-drop interface for designing and configuring multi-step automation scenarios.
• App Integrations: A library of pre-built connectors for hundreds of popular cloud applications and services.
• Scenario Execution: Automated running of workflows based on defined triggers, with options for scheduling and real-time processing.
• Data Mapping and Transformation: Tools for mapping data fields between applications and transforming data formats within workflows.
• Error Handling: Mechanisms for defining how scenarios should react to errors, including automatic retries and custom fallback paths.
• Custom Webhooks and HTTP Modules: Support for integrating with any application or API that uses webhooks or standard HTTP requests.
• Iterators and Aggregators: Modules for processing collections of data and combining multiple data items into a single bundle.
• API for Scenario Management: A REST API that allows programmatic creation, modification, and monitoring of scenarios and organizations.

Pricing

Make offers a tiered pricing structure, including a free plan with limited operations and data transfer. Paid plans scale based on the number of operations, data transfer volume, and advanced features such as higher execution frequency and priority support. The pricing information below is current as of May 2026.

For detailed and up-to-date pricing information, refer to the official Make pricing page.

Common integrations

Make supports connections to a wide array of cloud applications across various categories, including CRM, marketing, e-commerce, and productivity tools. Some common integration categories and examples include:

• CRM Systems: Salesforce, HubSpot, Pipedrive.
• Marketing Automation: Mailchimp, ActiveCampaign, SendGrid.
• E-commerce Platforms: Shopify, WooCommerce, Magento.
• Communication & Collaboration: Slack, Microsoft Teams, Gmail, Trello.
• Databases & Storage: Google Sheets, Airtable, MySQL, Dropbox, Google Drive.
• Payment Gateways: Stripe, PayPal.
• Analytics & Reporting: Google Analytics, Google Data Studio.
• Project Management: Asana, Jira.

A comprehensive list of supported applications and their specific integration modules can be found in the Make documentation.

Alternatives

• Zapier: A widely used iPaaS platform offering extensive app integrations and a simplified visual builder for automating tasks.
• n8n: An open-source workflow automation tool that provides a visual interface for building complex workflows and can be self-hosted.
• Microsoft Power Automate: Microsoft's cloud-based service for creating automated workflows between apps and services, integrated within the Microsoft ecosystem.

Getting started

To begin using Make, users typically create an account, then design their first 'scenario' in the visual builder. A basic scenario involves a trigger and one or more actions. For instance, to capture new form submissions and send them to a spreadsheet, you would select a webhook as the trigger and a Google Sheets module as the action. The following example outlines a simple process using a generic HTTP webhook to capture data and a placeholder for processing it:

// Example of a data payload received by a Make webhook
// This data would then be processed by subsequent modules in a scenario.
{
  "event": "new_form_submission",
  "timestamp": "2026-05-09T10:30:00Z",
  "data": {
    "name": "Jane Doe",
    "email": "[email protected]",
    "message": "I'm interested in your services."
  },
  "source": "website_contact_form"
}

// In the Make visual builder, a scenario for this might look like:
// 1. Webhooks module (Custom webhook) - Trigger
//    - Listens for incoming HTTP POST requests.
// 2. Google Sheets module (Add a Row) - Action
//    - Maps data from the webhook (e.g., name, email, message) to specific columns in a Google Sheet.
// 3. Email module (Send an Email) - Action (Optional)
//    - Sends a notification email to a team member with details of the new submission.

This structure allows for the rapid deployment of automated processes. Developers and technical users can also use the Make API to manage scenarios programmatically, enabling CI/CD pipelines for automation workflows.