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

A simple request, but it will take som time to implement successfully. Please add dark mode.

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.

When using migration templates to batch upload time, there is an option to mark an entry as non-billable, but not the additional option to "Show this entry on the bill" (as is available in traditional entry of Activities). This would be helpful and the final step in being able to fully enter time in batches.

It would be super useful to have a screen in the organization's configuration that will allow us to set scenario settings default. For example: I set the setting "Allow storing of Incomplete Executions" for 99.9% of my scenarios, and it's really annoying to forget it and then find out that one of my scenarios failed to run. So it would help to set this parameter on on organization level and then every new scenario will have it on upon creation.

Whilst this can be done with an custom API request, that requires parsing the json and defining a type and is generally unwieldy in comparison to allowing Get Task to request it and returning it in the bundle. Would it be possible to add that?

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.

It would be really great if there was a way to STOP a scenario from continuing after any given module has been successfully run. Why? Because of routers & filters. Currently, there is no way for us to put a "STOP SCENARIO" module at the end of a router path. As a result, ALL ROUTER PATHS always get evaluated 100% of the time, and then we are forced to create VERY COMPLEX FILTERS to try to prevent all the other router paths from activating. In other words, if the router goes down "Path A", we have no ability to prevent the scenario from going down "Path B" and "Path C" without creating complicated filters. We currently have to use very complex filters to prevent the scenario from going down any other router paths, but it would be amazing if there was a way for us to just put a "STOP SCENARIO" module after a certain path. The only other workaround for this is to willfully create an error message and then use a "commit" error module, but this is really bad practice. Thank you!

If integromat was HIPAA Compliant that would really open up this useful service to healthcare businesses and workflows. Currently I'm not able to use it because of that limitation.

So make.com has obviously been a huge help for using automation and AI, this might be too hard to implement but it would be great if Make.com had an AI that would scan your scenario and give you the most optimal way to create this scenario using functions or way less module's to save on operations.