Release notes

Some templates did not load values for arrays. Templates now display these values so you can edit and change them as needed.

In some cases, login failed with a 401: Access denied error. Login now functions normally.

Atera

Fireflies.ai

Linear

Citrix Share File

Freshmarketer

Google Cloud Firestore

Google Groups

Google Tasks

Google Translate

LinkedIn

NetSuite

Slack

When you import a blueprint, it now includes the scenario name.

You can edit Boolean values in Data stores.

When you migrated from one zone to another (i.e. EU1 to US1), the Migration tool showed the wrong initial zone that you wanted to migrate from. Now the Migration tool shows the correct initial zone.

Team members who did not have a role and permission to delete members could see the Delete button. Now the Delete button only appears for team members with the Team Admin role.

Several bug fixes and tweaks for Custom scenario properties:

The button to delete an organization sometimes appeared for users who weren't owners of that organization. Only owners can now see the Delete button for their organization.

Circle

Foursquare

Abyssale

MongoDB

Teamleader

Zulip

Error processing: we updated the list of increasing time intervals. This reduces the number of operations consumed when repeated attempts are made to execute a scenario with errors.

Changing payment details and viewing invoices: we made changes to the information regarding what you should do when your payment fails.

You can now click on item pills to expand mapped items with subitems.

The Search items box in the mapping field didn't respond to user actions causing some glitches when you were typing or inserting text.

We continue developing new documentation on Make, including errors. The 429 errors - rate limiting article explains how to handle this error, which appears when you reach the API rate limit for the app.

Using the On-premise agent: we added a couple of colorful and clear graphic schemes that explain the mechanism of the On-prem agent work.

Modules that caused an error and had an error handler in the route didn't show a warning message.

Several small UI fixes made Make more attractive:

Adobe Acrobat Sign

Caspio

Facebook Groups

Feedly

Google Drive

Google Maps

Google Translate

Rebrandly

Square

Twitter

FAQs: Due to the shutdown of Integromat on the 30th of September, we shortened the article and left only relevant questions. We added a link to the article where you can learn more about the current state of Integromat.

Incomplete executions: We updated the procedure for resolving the Incomplete execution with another necessary step. The structure is clearer now, so it is easier to follow the whole process.

We tamed down our chaotic cursor: when you edit a formula with different functions, your cursor doesn't randomly move between the formula's elements.

Were you confused by empty variable pills when mapping although they should have contained data? Don't worry, it was just a tiny visibility issue: now pills are full of color to show you that they contain data.

We get how frustrating it can be when a data store misunderstands your command: you wanted to edit a record but Make added a new record instead. No more confusion - you have your record edited and saved correctly.

A module wrongly perceived an array as a string and didn't let you map the array's elements. We repaired this mechanism, so now the array's elements are available for mapping.

After adding another module of the same app you already had in a scenario, it didn't pull up a connection for this app. It's not a problem anymore: Make now remembers the connection from the same app.

Modules now handle different data types more gracefully. Data in all formats, from arrays to simple texts and numbers, are displayed correctly in the output.

Nobody likes an error, but when they happen, you need to know about it. We now ensure you have all the information about errors in your scenario logs.

We recently had an issue where Make was not allowing a new webhook to be created for the cloned scenario. We've fixed it, and now Make follows its own rules and assigns a separate webhook to each scenario.

Your confidential scenarios are now safeguarded. Previously, there was a small concern with webhooks revealing data in their logs and queue. Now we have developed a fog-like covering for webhook's data, ensuring that it remains hidden.

Calling all custom app users! Scenarios with custom apps can now be saved without any error popping up.

The clickable module ellipsis or three dots icon is back! You can now click it again to access additional options.

Attio

Alegra

bexio

Capsule CRM

Chatra

DEAR Inventory

Dropcontact

LinkedIn Lead Gen Forms - Events

NetHunt

Pushbullet

Parseur

Rossum

TalentLMS

FluentCRM

Hubspot CRM

OpenAI

Oracle Fusion Cloud ERP

Oracle Fusion Cloud HCM

Oracle Fusion Cloud Sales

SlickText

SugarCRM

Twitch

Xero

Zoho CRM

We've made the router even sweeter by adding missing icons to the Order Route window.

Treat yourself to a centered route name, so everything looks perfectly balanced now.

Previously, cloning scenarios with custom apps and webhooks was like trying to clone a pineapple – it didn't quite work! We've cracked the code and now each scenario comes with its very own unique webhook.

If you needed to define a target structure type in the array aggregator, it got picky and showed the target modules fields selectively. Now you see all available fields.

Make could not deal with migrated scenarios: they ran with an error that appeared without any reason.

The Migration tool refused to replace connections with ones created on Make.

Webhooks had a strike and didn't allow you to edit them. Fortunately, we satisfied their requirements.

Mapping pills were stuck in the initial modules field, so you could not drag them to another field.

Adobe CC Libraries

Checkr

Cloudinary

Glide

Hotmart

iLovePDF

Mailmodo

SamCart

Box

Bubble

Google Sheets

Microsoft SharePoint Online

Notion

OnceHub

Webflow

Wix

Workday Human Capital Management

Workday Financial Management

Yandex.Translate

We made our famous router much more attractive to the paparazzi:

No more cut app names in the scenario builder: you see the full application name under the module.

Make mixed error messages up, but we fixed it. Now if a scenario fails to finish the initialization, you see a correct message.

Languages unite people! The webhook output supports languages with the non-Latin script.

Modules don't erase mapping after you click Save.

HTTP OAuth2 and Email connections pretended they were zombies: you could see them in the Connections list, but sneaky 404 errors prevented you from making any changes.

The Migration tool played a bad game with you: it allowed migrating data stores that exceeded the allowed size in your organization on Make, but you didn't see any warning message beforehand.

The scenario activation toggle played dead, but we breathed a new life into it: turn your scenario on and off at any moment.

Were you wondering where your On-prem agent disappeared? Actually, they were always on the On-prem agents tab, but now they are visible.

We're not going to stop making our features even more awesome: the list of Connected systems became more comfortable to use on your mobile devices. We've added a charming little icon next to the connected system name shows you if it's connected to an On-prem agent.

You won't have any problems with understanding what the () function does: we added a clear description.

When there's something strange in your scenarios, who you gonna contact? We've streamlined our help ticket process to automatically include your relevant information.

We tried a new insect repellent out and killed a whole bunch of UI bugs:

All the data is in its place safe and secure! After the scenario migration to Make, mapping remains the same as it was in Integromat.

The Refresh form button doesn't erase mapping anymore.

The filter settings window is not a spoiled child: it works correctly and appears without a random error.

Make is a good diplomat: it talked with app servers and agreed to show available settings options in some modules that refused to show them before.

We believe in second chances. A small bug kept members entirely from your organization. Now, a member who's not on any team can't access any scenarios or data but you can assign them to another team without adding them to the organization again.

Want more features from the Apps Code editor? We've got you covered! With this release, you get IML functions docs when you hover over them. If you try that with a custom IML function, you can use the pop-up to jump to the definition of the function.

It is easy to mix-up a comma and semicolon, but we keep an eye on that: the formatNumber function has the correct example with a semicolon.

Sometimes Make insisted on saving the scenario in the edit mode when you already saved it. We calmed it down: no more annoying pop-ups.

Empty custom variables seem so useless, especially in functions! The issue is in the past: all custom variables contain relevant values wherever used in the scenario.

All fans of the Integromat DevTool don't experience its failure on custom domains anymore.

The rise of the machines is canceled: Make doesn't prevent you from extending your connections any longer.

Tiny, but an oh-so important UI fix: the route menu is as beautiful as everything else in Make.

We bet you don't need buttons that don't do anything, right? Don't be surprised by the absence of the Refresh form button in the scenario schedule settings.

Longer looks better now. We tweaked the UI so lengthy organization names don't look ... awkward ... anymore.

You don't have to automate alone anymore. We squashed some bugs that got in the way of inviting collaborators into your organization. Now they can log in and get into your organization without any issues.

Holmes would be proud. We cracked the case of the missing mapped values. Those values are back in your templates and won't disappear when you create Make

Even more useful data in system variables: we added a new Is incomplete execution variable that shows whether the scenario execution is a regular one or an incomplete one.

And one more lovely variable: Execution type shows the way the scenario was executed. Possible values are:

Were you ever wondering why Make asked you to save changes in the incomplete execution when you didn't change anything? We understand you: no more irritating messages appear without any reason.

We fixed the mod operator description: it reflects the operator's work correctly.

Nobody likes filters that don't filter anything, right? That's not the case anymore: if a filter contains a team system or custom variables, it does take them into account.

Make Migration tool doesn't ignore Make limitations in custom apps names' symbols anymore: if the name contains more than 30 symbols, the Migration tool won't migrate it.

It had one job! In some cases, extra operations auto-purchasing didn't keep scenarios running. We squashed this bug and you trust our amazing extra operations auto-purchasing without any worries!

The mysterious case of the vanishing connection! Our templates used to play hide-and-seek with your existing connections, but we've given them a crash course on detective work. Now, you can easily spot and leverage your connections whenever you use a template. No more disappearing, case closed!

It had one job! In some cases, extra operations auto-purchasing didn't keep scenarios running. Don't worry, we squashed this bug and you can rely on extra operations auto-purchasing.

The mysterious case of the vanishing connection! Our templates used to play hide-and-seek with your existing connections, but we've given them a crash course on detective work. Now, you can easily spot and leverage your connections whenever you use a template. No more disappearing, case closed!

We organized the organization dashboard. Does that make it a reorganization dashboard? Reorganization-ception? We don't know but buttons and information related to your subscription and extra operations are tidier and more logical now.

Developing a custom app, now in color! We remodeled the code editor experience and improved syntax highlighting, code beautification and a new save button. Keep your hats on, more incoming in the next release!

Polling triggers using the Choose manually option were not updating with the correct epoch data value. We didn't even have to poll all of you to know that this incorrect data shouldn't be allowed to stay in office.

We know you all trust us to get things right, so we made sure our type conversions were on point. When mapping an array with a single item inside, no more empty results when you're expecting some sweet text value.

Gone are the days of sad- and awkward-looking columns that wouldn't scale. I guess you can say they're making a bigger thing out of it now.

Is it supposed to look like that?! No, nobody wanted our logo in the two-factor authentication QR code to look like a rejected rugby ball design. That's why we changed it making sure it still does the job of keeping your account secure.

Clearer hints in the Incomplete Execution to let you understand the functionality better.

Did you set up a fallback route in your scenarios and then couldn't find it? We've found the issue, and fallbacks aren't reset randomly anymore.

The names of custom fields in your applications are now shown correctly when mapping: no more confusing numbers.

We like short links, but not cropped ones. In webhook logs, you can see all the data in webhook URLs, as before.

Did it seem illogical to choose the date range for scenario scheduling if it ran just Once or On demand? We think so. Date ranges are no longer shown in these cases.

A new beautiful button for creating a connection in every application you might need to build a scenario:

The results in the full-text search became even more effective: as usual, you have the most relevant data at the top, but now the most recent results go first.

No more troubles with the formatDate function: it correctly considers the organization's time zone.

Let your data stores work properly: if you add a new item to the data structure, the system no longer messes up its type.

Now a webhook can process all files it receives under the same key. But there is a little trick: you can find information about all the files in the collection named by the key, under the files array. Let's jump into an example:

In this example, the webhook received two files: image and image(1) under the picture key. Only the last sent file is shown in the picture collection. To see both files, expand the files array.

But don't worry: no need to urgently adjust your scenarios - you may leverage new functionality whenever you want.

No more issues with connecting to Twitter via OAuth2: use it as always! To start using the new Twitter application, just give Make your approval as an additional step - and it's done. Once creating a connection, click Yes, continue as shown in the screenshot, and then grant all permissions on Twitter's side.

Clearer hints in the Scenario Builder to let you understand the functionality better.

Updated logo in Upgrade Hub and Make Migration Tool: we're Make forever and ever! If you haven't migrated from Integromat to Make yet, it is the right time to do it with the help of our amazing tool.

An iterator couldn't process variable values: now you have all data you need.

Some apps didn't appear appear in the scenario editor. Instead, a Module not found error appeared at the app's place without any reason.

When deleting a custom variable, no warning message with the list of referenced scenarios appeared.

The base64 function converted the value in the wrong way.

It wasn’t possible to delete an incomplete execution. The Some of the executions could not be deleted because they are being processed right now error appeared, however, the incomplete execution wasn't in processing.

A scenario execution was stuck in the Running status, however, it wasn't in processing.

If the scenario contained a webhook with records in its queue, and you added a new trigger module to the scenario, after running it, the new module was trying to process its queue instead of waiting for data.

In the Upgrade hub, you can see the list of organizations that haven't been migrated fully yet.

If you had an array of numbers in the scenario input, the Set Variable module showed a Invalid value "VALUE_NAME" of variable arrayOfNumbers. Type number expected error without any reason.

If you used several custom variables in a scenario, but then deleted all of them and tried to save the scenario, the warning message didn't show all deleted variables used in this scenario.

After setting up an app, an error bubble appeared without any reason.

When trying to resolve an incomplete execution, the history showed the successful attempt without any error while it wasn't resolved in fact.

When running the /data-stores/{dataStoreId}/data API endpoint without the exceptKeys optional parameter, there was an error.

When clicking the Exit editing button in the scenario builder, the Not found error appeared without any reason.

When creating a remote procedure for any custom app, you didn't see the connection name under the Connection section.

In the migration tool, you have all scenarios that can be migrated selected for further migration by default.

It wasn't possible to save the scenario after clicking Run once. The Unknown Exception: invalid input syntax for type json error appeared without any reason.

The formatDate function didn’t modify the date according to the settings you set for this function.

If a module in the scenario contained a custom function, the scenario failed with the [object Array] could not be cloned without any reason.

Manual writing of a function’s notation in the module didn't work correctly.

When approving a custom app as an admin, the Commit button wasn't clickable with no errors if you left the text field empty.

An updated version of the Make mobile app is available for your Android and iOS devices. This version features Make branding.

A branded Google Sign-in button appears when you create a new connection for any of Google apps.

When you use the following components in the scenario, but then deleted some of them, Make shows a warning message that contains information about the deleted component(s) once you try to save the scenario:

Improved hints for some features.

It wasn't possible to delete a user who created a custom function.

The Unexpected internal error was caught. Contact the support. error appeared in the scenario when there were no errors in fact.

When the admin of the organization entered another organization that they were not an admin for, they didn't see the organization's custom functions (if any existed).

It wasn't possible to migrate a huge data store (around 2000 MB and bigger).

Custom functions didn't work in filters.

Clicking multiple times on Buy extra operations opened multiple checkout pop-ups.

In some cases, it was not possible to add an ACH payment method.

Improved hints for some features.

When you used notes in the scenario builder, the user interface had minor visual glitches.

When setting up modules (including custom apps), text values in various drop-down menus weren't sorted in alphabetic order.

If there was a custom function in an iterator, its output wasn't clickable, and it wasn't possible to open the next module after executing the scenario.

In the scenario with the "Flow Control tool → Module → Array aggregator" scheme, the Array aggregator didn't show the name of the chosen Flow Control tool while mapping values.

After deleting a custom variable and then executing scenarios where it was used, the warning message didn't contain the name of the deleted variable.

The Reauthorize button for some OAuth connections wasn't visible in Connections.

It wasn’t possible to map an iterator’s result to the module next to the iterator, if there was a Set Variable tool before the iterator.

It was impossible to restore the oldest version of a custom function.

When using the Choose where to start option, it wasn't possible to specify a specific ID of the item to start with.

The affiliate dashboard did not correctly display the number of paying organizations that count toward affiliate payouts.

Improved hints for some features.

The Reauthorize button for some OAuth connections wasn't visible in Connections.

When setting up the scenario input, if you selected the Boolean type of data and set it up as No, it was reset to Empty after clicking Save.

It was possible to clone a scenario with custom functions to a different team.

The icons of custom apps were broken when mapping values between two modules.

The mapping process crashed the scenario containing custom functions and a bundle with binary data.

If you didn't find the needed app in the list of modules, the system didn't suggest requesting for a new app.

If the scenario had the Break error handler, and the scenario resulted in an incomplete execution several times, there was only one record for all failed executions in the Incomplete Executions tab.

Improved the resiliency of webhooks and mailhooks, which are forwarded from Integromat, against DoS attacks.

If a scenario failed with a RateLimit error, scheduling was ignored and incomplete executions were not handled correctly.

New payment methods: Make now accepts ACH direct debit payments (US bank accounts).

Added the help center link to the scenario inputs panel.

When selecting the webhook instant trigger in SmartSuite > When a record is created, it was not possible to create a new webhook. Instead, the error 'Validation failed for 1 parameter(s).’ appeared.

In some cases, even if a scenario was successfully executed, scenario history logs were not always displayed for all past executions.

The ClickUp app logo was not displaying correctly in the scenario builder when selecting ClickUp apps and modules.

It was not possible to use the side navigation to switch between organizations in different zones, i.e. EU1 to US1.

Some SSO logins encountered an unresponsive infinite loop.

Customers on free plans incorrectly saw a nonfunctioning button to purchase extra operations.

Some payments could not be correctly processed and the pending status persisted.

Some notifications appeared without a description.

On the affiliate dashboard, the date filtering dialog did not close after clicking Apply.

In case of failed card payments, there were errors processing newly entered payment cards.

App search panel improvements: added a help hint when there are few or no modules found.

It was possible to create scenario inputs structures with the same name, and there were no errors.

Organizations could not redeem coupons for extra operations if there was no saved payment method.

Legacy accounts did not link to new Make accounts when joining Make via an invitation to an organization.

The pop-up for buying extra operations did not automatically close after purchasing extra operations.

App search panel improvements: added the search icon and “Search applications” text. 

When adding a new data structure, the required fields for the date and collection data types were not visible.

For some customers with more than 50 webhooks, some of the webhooks were not showing in the user interface, even though they were attached to the scenario. When opening the Custom webhook module, it showed “Choose a hook” instead of the list of webhooks, even though the specific webhook was already configured.

For some scenarios which had incomplete executions and were using advanced scheduling, the executions did not wait for the first one to finish before starting the new one. Instead, the new execution started whilst the previous one was still running.

It was not possible to rename devices. You can edit a device's name by going to the Device tab and double-clicking on the name you want to edit.

Invitations to organizations failed when inviting new users to Make who had '+' in their email addresses. For example, invitations failed for a new user with an address such as [email protected].

We have published API documentation on inspecting the webhook execution logs. Check out the respective docs:

The template Asana > List tasks did not work as expected. It was necessary to manually map the module. Also, clicking Continue did not proceed to the next step.

When manually migrating scenarios from Integromat to Make, some scenario migrations were unsuccessful. This happened when confirming default values for webhooks, connections, and folders and then going back to change the webhook default value from "duplicate and forward" to "duplicate only". The reason for the error was caching invalidation.

In the mapping dialog, some nested fields were displaying the names instead of labels.

When hovering over a variable, you can now see the variable value and data type. This includes both system and custom variables.

Added information about API rate limiting in the Make API documentation.

When using the template Asana > List tasks to create a scenario, clicking Continue did not work.

When mapping custom apps, the File parameter showed, even though Show advanced features was not switched on.

Added the ability to filter affiliate statistics by date on the affiliate dashboard.

Manually rerunning incomplete executions threw errors such as "This execution cannot be displayed: blueprint version is missing". Some users also got email notifications "Cannot initialize the scenario because of Inconsistent Snapshot state on Team Level".

In the US1 zone and across enterprise instances, error messages appear for issues that were fixed when manually rerunning incomplete executions.

You can now filter webhook executions in the webhook log and queue.

Use the collapse and expand option to see variables from the previous modules.

In Integromat, you can now see which scenarios were migrated to Make. When you hover over the migrated tag, you can also see the zone.

For non-compiled custom apps, the connection dropdown did not show the app icon in the forms interface.

Podio > Filter app items module was throwing the “store.reduce is not a function” error.

In the forms interface, the fields with long names were not fully visible and they hid the map button.

It was not possible to clone the API key connection, webhook, or data store while cloning the scenario.

It was not possible to select the date in the calendar when filtering logs of incoming webhooks and scenario history.

The output suggestion is based on the first ten bundles of the first two operations of the module (it used to be the first bundle of the first operation).

UI improvements: Better distinction between custom and system variables.

When using the Custom webhook module and saving it while the Stop button is still loading, the first hook call got lost.

Variable history did not show the time for the date data type variable.

App search was returning matches in the incorrect order and the exact match was not the first result.

When deleting a scenario with a custom webhook, the webhook was deleted together with the scenario.

When searching templates by app, removing an app from the search field did not update the filtered results shown. Instead, the search still displayed the original results.

UI text for active scenarios incorrectly referred to organizations when displaying team information.

Improved scenario saving time.

When using a template wizard, Make automatically saves your new scenario as soon as you complete the wizard. This lets you edit and test run your scenario right away.

When creating scenarios from a public template, clicking Run once started the scenario but immediately redirected to the scenario editor during execution.

The data type column in the system variables was sometimes showing numbers, even if the data type was different.

When using the system and custom variables in the Iterator module, the output value was empty.

When entering JSON in the Generator option in custom apps, the labels were not returned.

The Webhook response module returned a warning when the scheduling was changed to Immediately and Run once.

The default size of a data store changed to 1 MB.

Optimized the Webhook Gateway performance, which can help reduce 5xx errors being returned from webhooks.

The Delete button in Variables would disappear on certain screen resolutions.

There was no pop-up asking for confirmation before deleting the custom variable. This occurred for custom variables starting with a capital letter.

The “TeamID” parameter was included in API calls and aggregator when it shouldn’t have been. This affected multiple apps.

In Text parser > Replace module checkboxes were missing for Case sensitive, Multi-line and Single-line fields so it was not possible to set any of these options. Also, it was not possible to map these fields manually.

It was not possible to save Katana templates.

Scenarios created from a template and saved could not activate.

Templates with a webhook trigger did not default to automatic triggering schedule.

When using Google Chrome, scenarios were not loading the module settings, specifically for Aggregator modules.

Pipedrive > Watch Activities module did not return output data when selecting the Choose manually option in the Choose where to start dialog.

When copy-pasting scenarios, mapping in some modules was not working correctly after pasting the modules.

Pipedrive > Update a Deal module wrongly reset the mapped time input value after saving the module.

The home dashboard displayed a limited number of scenarios but now displays a scrollable list.

Sharing templates via Facebook, Twitter, or email did not work.

In apps that use incremental authorization, it was not possible to extend the missing scopes automatically when using the default connection. For example in Jira Cloud Platform, Adobe Sign, Slack, Google Drive.

After reloading your browser, your selected team unexpectedly changed in some situations.

Enhanced internal checks for billing and subscription accuracy.

Make SDK: You can now add a custom header in the JWT-type connection. For more info, check the JWT connection in the Make SDK docs.

When clicking the Refresh connection button in the module configuration panel, another connection was selected or the panel was closed completely.

Failed payments sometimes resulted in incorrect charges after updating the payment card.

Fixed repeated loading in forms.

It was not possible to search for or delete manually added values when mapping the values from one module to another. For example in Monday, Slack, Airtable.

In scenarios with JSON and Freshdesk, connections and data structures duplicated wrongly across teams when using copy-paste and export-import blueprint options.

RSA/SSH keys were not extracted correctly when trying to connect the SFTP module.

Pipedrive > Watch Activities module was not returning any data after scenario execution.

There were errors when mapping Monday > Update Column Values of a Specific Item module and the fields did not save correctly.

When trying to map a complex array with the XML > Parse XML module, the variables appeared broken.

For apps that load information dynamically and have two or more different connections, clicking the connection dropdown automatically selected a connection without the user clicking on it.

Mapped items disappeared after clicking the Refresh button. This issue appeared in Notion > Create a Database and Airtable > Create a record module.

Validation errors occurred when migrating scenarios with custom apps that contain an instant trigger and search or action modules.

Full-text search in scenario history did not find matches when using upper case.

Using Make's API did not successfully create API tokens.

Users with a paid organization could not create a free organization.

In rare cases, users were unintentionally logged out and lost unsaved changes.

The full-text search in scenario histories didn't work on free plans.

The Make logo flickered under some circumstances.

User dashboards only displayed four scenarios.

Changes in billing method were not reflected on screen.

Some organizations did not work properly after migration.

Recurring payments sometimes failed when calculating sales tax.

The Clone as a template button didn't work.

Links to templates didn't work across different geographical zones.

Coupons for extra operations.