Platform Ideas and Improvements

When a scenario runs into an error it would be useful to be able to run it again using the same trigger. ------------------------------- SEE ALSO: Incomplete executions: https://support.integromat.com/hc/en-us/articles/360001988854-Incomplete-executions "Run module only" with real data: https://integromat.canny.io/feature-requests/p/run-module-only-with-real-data ) Enable "Choose Where To Start" for instant triggers / webhooks: https://integromat.canny.io/feature-requests/p/enable-choose-where-to-start-for-instant-triggers-webhooks

Get some kind of notification if a webhook will expire or has expired. Since webhooks expire when not being used for some time it would at least help to be notified.

Being able to setup more than one trigger per scenario is useful when the same kind of data comes from different sources. Ex: Leads comming from Facebook Ads, and from another, generic, webhook. ------------------------- BESTPRACTICE: Create a "core" scenario that would perform the common data processing. Insert the "Webhooks > Custom webhook" module at the beginning of the scenario. Copy the webhook's URL. (see https://support.integromat.com/hc/en-us/articles/360006249313-Webhooks for further information about webhooks) For each trigger you would like to employ create a separate scenario and insert the corresponding trigger in it. Connect the "HTTP > Make a request" module after the trigger. Configure each "HTTP > Make a request" module to pass the data to the "core" scenario: paste the copied URL in the URL field and map the items in the Fields field. (see the attached screenshot and https://support.integromat.com/hc/en-us/articles/360006248533-HTTP for more information about making HTTP requests) SEE ALSO: https://integromat.canny.io/feature-requests/p/execute-a-scenario-sub-scenario

The Converger module is basically a counterpart of the Router module and it would enable you to merge several routes into one. ------------------------- BESTPRACTICES: https://support.integromat.com/hc/en-us/articles/360016984073-Converger When in doubt, please, contact our support ( https://www.integromat.com/en/ticket ) or feel free to post a question to our Facebook Integromat Community group ( https://www.facebook.com/groups/integromat/ ), where hundreds of specialists, users and fans are willing to help.

Use case: When a webhook payload reaches Make with a small error (e.g. invalid character, wrong email, or missing field), it can cause a scenario to fail. Currently, there is no way to manually edit the data in the webhook queue, the only option is to delete the execution and resend a corrected webhook externally. Feature request: Add the ability to manually edit the webhook data before rerunning the failed execution. This would help in cases where the incoming data is nearly correct but needs a minor fix.

Working with subscenarios is GREAT, the issue is that when you're managing a lot of variables it's very painful to have to manually create every input whenever you create a subscenario I'm currently working with +20 inputs, and everytime I create a new subscenario I need to create these +20 inputs again.

Feature Request: Please allow users to create subfolders or sub-groups within scenario groups. Why it matters: As automations grow, managing dozens or hundreds of scenarios in a flat structure becomes overwhelming. Subfolders would: Keep scenarios organized by client, department, or function Help teams separate Dev/Test/Prod versions Make large workspaces easier to navigate and maintain Support scalability for agencies and enterprise users Current workarounds like naming conventions or too many groups just don’t scale. This would be a major usability upgrade. Thanks!

Provide an option for users to start executing from a specific module and then proceed to execute all other modules linked in sequence from that point in the pipeline.

I've had an automation blocked for a while, and what you should say is that when that automation doesn't work, you can give it an order and thus tell you what the next step is and do it to make it work. It's facilitating movements for this automation platform, which is not very intuitive to say

A recent email came out from Make notifying us that Shopify is requiring all users to transition to their v3 API. The email says "Modules that need upgrading will be marked with a green upgrade icon. Simply click the arrows to update them." This seems to suggest upgrading to v3 is as simply as clicking the arrow. However, what actually happens, is a new module is inserted into the scenario. This new module has a new identifier number and is not connected to your scenario. As such, what has to happen, one has to delete the existing module, connect the new module, and then look at every other module in the scenario and adjust the identifier. This could be a huge process, one prone to errors or omissions. Rather, I would suggest that Make provides for a true "update" process by which one could choose to have the update automatically done: * The current module is automatically replaced with the new, while retaining the identifier and/or * The update process searches through all other modules in the scenario and automatically updates any reference to the old module, with the reference to the new module.