Make: what's new and what's changed

Overview

Make is not just an update, but a completely new product with new architecture and features which is heavily based on feedback from our valued customers and partners.

Upgrade required

If you're an Integromat user, you need to upgrade your organizations and your data to Make.

  1. Go to https://www.make.com/en/register.

  2. Enter the email address you use for Integromat.

  3. Follow the instructions on-screen to complete the upgrade.

To learn more about the upgrade, read Upgrading to Make.

This article brings an overview of new features and changes in Make, and the differences between Integromat and Make that you need to know about in order to transition between the two as smoothly as possible.

Note

Not every feature mentioned in this article is available on every Make plan. See Make pricing for more detail.

Top 5 improvements

  • Make has a completely new architecture which scales to meet the global demand and it is designed to be deployed across geographies with the US and EU hosting.

  • New teams feature in Make allows you to separate access to scenarios and connections between different teams in your organization.

  • Webhook-initiated scenarios can execute parallelly and instantly in Make with nearly real-time response to high-volume inbound requests from other applications.

  • Full-text search for scenario execution history makes it easier to find the right scenario execution and troubleshoot more effectively.

  • Make REST API enables you to access Make data and control the Make platform without opening its graphical interface.

All improvements

New architecture

Make is hosted on Amazon Web Services cloud platform (AWS), and it is built on a new foundation to be more performant and scalable. Users are managed centrally and they can have access to organizations hosted in the US, EU, or enterprise environments.

Make can be launched as a private instance anywhere in the world. Due to horizontal scaling, Make can rapidly boost performance for the whole platform by launching more instances. This results in increased performance, throughput, stability, and availability of the product.

Organization

Organization based single sign-on (SSO) support

Single sign-on (SSO) allows you to use your own provider of user account management, authentication, and authorization services to register and log in to Make.

Each organization can uniquely set up its own OAuth2 or SAML2 compliant Identity Provider (IDP) to be used as the authentication authority for its Make organization.

Single sign-on works with Okta, PingOne, Google, Azure, and dozens of others.

You configure SSO for each of your organizations separately.

sso_.png

Sign in with SSO

Learn more about SSO.

Templates

Anyone with a Make account can now create a template. Previously only Integromat employees could create templates.

This new feature allows you to:

  • Create new templates for yourself, and share them privately with your team.

  • Publish your templates to make them available to other Make teams and organizations via a public link.

  • Request approval from the Make team to make your templates publicly available to everyone in our growing public templates library.

  • Tailor your templates with defined wizard steps to help first-time users make a successful start.

There are two types of templates:

  • Team templates - all the templates you or your team have created. From here you can create, customize, save, and share them with others. You can search for team templates by name using the search bar.

  • Public templates - a collection of templates created by Make and our partners that demonstrate many common integrations. They are available for anyone to use to create their own scenarios. You can search for public templates by module or app name using the search bar.

templates_7.png

Team templates and public templates

Learn more about templates.

Teams

Teams are a completely new feature in Make which did not exist in Integromat.

Teams allow you to control access to scenarios and other Make data. Now you can divide your organization into multiple teams based on departments or projects for example, and control which employees have access to specific data.

Note

Make implementation partners can create teams for their clients.

My_team_.png

Organization divided into teams based on departments

Organization owners and admins create and manage teams and add team members to each team with a specific role.

Users can have the following team roles:

  • Team Admin has full access to all data within the team.

  • Team Member has full access to all data within the team, but cannot manage team members and cannot delete the team.

  • Team Monitoring has read-only access to the team, scenarios, and templates.

  • Team Operator has read-only access to all data within the team. In addition, the Team Operator can activate or stop scenarios and set up scenarios.

  • Team Restricted Member has full access to all data within the team, but cannot publish scenarios and cannot modify the team.

Team_roles_.png

Team roles

Members of a team have access only to scenarios and data that belong to that team.

The following items belong to a team:

  • Scenarios

  • Templates

  • Connections

  • Webhooks

  • Keys

  • Devices

  • Data stores

  • Data structures

Organizations vs Teams

Make provides a two-level permission model. There are organizations and teams, which means you have organization roles and team roles.

Organizations are the basic containers into which all teams belong. Scenarios, users, and data belong to a team.

Organization owners or admins assign users into teams. All users are members of at least one organization and one team. Users can be a part of an unlimited number of organizations and an unlimited number of teams. A user can be a member of multiple teams across different organizations and have a different role in each team.

See more about teams.

Scenarios

Live streaming of scenario executions

With the scenario streaming feature you can run more scenarios in parallel. You can also view everything that is happening with scenario executions in real-time and stop in-progress executions if you need to.

Live_streaming_.png

Scenario streaming, see executions in real-time

Scenario execution history: show check runs

When reviewing execution search history for scenarios with a scheduled or polling trigger, you can now easily toggle whether you want to filter out scenario runs that did not return any records. This helps you remove the clutter of those runs that didn’t find any new or updated data.

Execution_history_-_show_check_runs_.png

Scenario execution history detail review experience updates

The layout of scenario execution details interface allows you to review and troubleshoot execution details faster.

The performance of this page has been improved, particularly when interacting with a scenario that has processed a large amount of data. In Integromat, all input/outputs for every bundle get loaded into the browser immediately, causing sluggish performance for scenarios with hundreds of bundles or more. In Make, inputs/outputs are not loaded into the browser until the user clicks on the operation bubble next to a module.

execution history detail review experience update, integromat_.png
execution_history_detail_review_.png

Integromat (left) vs Make (right) comparison:scenario execution history detail review

Webhooks

Parallel webhooks

In Integromat webhooks process sequentially and executions queue waiting for the first one to finish for the next one to start. In Make multiple executions can run in parallel.

By default, scenarios now execute incoming webhooks in parallel, allowing better responsiveness to inbound requests. If you want, you can still enable sequential processing of webhooks. You can set your preference in scenario settings.

Parallel_webhooks_.png

Multiple webhooks running in parallel

See more about Webhooks in Make.

Webhook queue list improvements

Webhook queues now show in the same browser window and have the additional capability to select multiple incoming messages and then delete the messages all at once.

Webhook_queue_list_Integromat_.png
Webhook_queue_list_.png

Webhook queue list in Integromat (above) vs Make (below)

Learn more about webhooks in Make.

Admin

User management - inviting a new user

Only organization owners and admins can invite users to join an organization. You need more information to add a new user in Make. You need to enter the email and the organization role the same as in Integromat, plus the name of the user and team to which the user belongs, which were not required in Integromat.

See how to add users to organizations.

In Make you can find the following organization user roles:

  • Owner - the owner of the organization, can make all changes

  • Admin - can make all changes except delete an organization and transfer organization ownership

    Note

    In Integromat, the admin role did not have so many capabilities, e.g. they could not add users, but in Make they can.

  • Member - a basic user who has access permission that relates to a specific team

  • Accountant - can view payments and organization details

  • App Developer - can view organization details and install custom apps to the organization

    Invite_a_new_user_Integromat_.png
    Invite_a_new_user_Make_.png

    Invite a new user dialog in Integromat (left) vs Make (right)

    See more about organization roles.

    Note

    Note: Operator and monitoring role from Integromat do not exist anymore under Invite a new user dialogue, but they are moved under Teams. Both organization owners and admins can change roles in their organization and in teams that belong to the organization.

Custom apps - app sharing permissions updated and simplified

In Make, the organization admin can install custom apps. Once installed, the custom apps are available for all users in the organization.

This prevents a user from developing a custom app and using it without permission in the organization’s scenarios. In Make if the user wants to add a new custom app into a scenario, the app has to be installed.

In Integromat, there was no such concept and it would sometimes create confusion if a single user received an invitation to a custom app, and then used it in their scenarios, but the other users didn’t have access to this app.

The list of installed apps is available on the Organization dashboard > Installed Apps tab.

Custom_apps_1_.png

Full API

Make REST API uses HTTP requests to access Make data and control the Make platform without opening its graphical interface. This allows you to embed Make features into your software, add features on top of the platform and automate the tasks that you perform in Make. The API allows you to interact with multiple Make resources:

  • More than 300 endpoints to start/stop scenarios, manage teams and users, data stores, and more

  • Authentication with properly scoped tokens

  • Full control over the platform - whatever you can do from the web interface, now you can do through the API as well

Time savers

New forms interface

Forms are all areas within Make where users directly enter text, select a date, choose an option from a list, or otherwise input data.

Make has newly designed forms that are more intuitive, visually appealing, and easier to use.

Key updates include the following:

  • The form indicates which type of information you should enter in every field (e.g. text, number, date).

  • Opening existing module configurations that rely upon information returned from a third-party service is significantly faster (Make relies upon the information currently available and users can refresh individual fields as necessary).

    • Let's take Google Sheets: Update a row module configuration as an example. Clicking on the module you had already saved to review the configuration takes 15 to 30 seconds to show In Integromat, whereas in Make the form displays within 1 or 2 seconds.

  • Dropdown selection has a “find as you type” feature when selecting an item from a long list (see screenshot below).

  • You can collapse or expand individual fields (and subfields) to improve readability when working with large forms.

  • All the forms open within the same browser window. Therefore, you don't need multiple modal windows opening on top of each other when working with arrays, collections, and nested concepts.

new forms interface.png

New forms interface in Make

Improved data store browser interface

Viewing and managing contents of data stores in Make has been improved. The main features include the following:

  • The interface opens within the same browser window.

  • You can make multiple changes across columns and rows without saving them one by one.

  • You can reorder columns on the fly.

  • You can edit a single field with fewer clicks, it is much more like a spreadsheet.

  • New pagination controls make it easier to work with a large set of data (you can view up to 100 records per page).

    improved data store browser interface, integromat_.png
    Improved_data_store_browser_interface_.png

    Integromat (left) vs Make (right): comparison of data store browser interface

Function usability enhancements

The new basic function validation lets you quickly identify unclosed functions. For example, trying to save a form with open parentheses results in an error message. You can now visually see different parameters that are related to a specific function by hovering over one part of the function.

This feature helps you understand functions more clearly and to make function adjustments faster.

functions, integromat.png
function usability enhancements, make.png

Integromat (left) vs Make (right): comparison of functions

tolltip_coder__1_.gif

Hover over specific functions to see different related parameters