Release notes

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 he was not an admin for, he 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.