Platform Ideas and Improvements

copy condition of the filter and paste to another filter -------------------------------------- BEST PRACTICE: https://support.integromat.com/hc/en-us/articles/360001988734#copying-a-filter

Allow the owner of the organization to have the option of enforcing the use of 2FA for all users. Also update the "Users" view to show which users have 2FA enabled.

When in need to connect multiple accounts (exp. google calendar). There will be an ability to send a link to that client in order to create a connection. That way the client creates the connection on his own device, and that connection will be added to the account that had sent the link.

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

Allow users to leverage JS inside a module and output the values as a JSON object ------------------------- BESTPRACTICE: Amazon Lambda: Modules: https://www.integromat.com/en/integrations/amazon-lambda Documentation: https://www.integromat.com/en/kb/pkg/amazon-lambda/index.html Google Cloud Functions: JavaScript: https://medium.com/@jwdt/using-javascript-with-integromat-6fe38c47830c Python: https://medium.com/@jwdt/using-python-with-integromat-865d4efb2a77 Cloudflare Workers: https://blog.cloudflare.com/cloud-computing-without-containers/ SEE ALSO: https://integromat.canny.io/feature-requests/p/custom-iml-javascript-functions

jeff Delacruz: We have a trigger that monitors Shopify for new orders and sends emails out. We wanted this scenario to only run when an order was placed and not check every 1 min as that uses a lot of operations. We switched to a Webhook Module and now it waits for an order to come in. The only issue is that we cannot use the "Choose Where To Start" functionality found in the regular triggers. This prevents us from: Rerunning past processes if a scenario fails, like sending another email. Testing with actual payloads. We can see the history of a Webhook, it would be great if we could reference it to re-run in the scenario. Because we can't use webhooks our operations count are unnecessarily high, costing extra money to maintain. ------------------------------------------- BESTPRACTICE: Open one of the past scenario executions during which the webhook outputted a bundle. Click on the "bubble" above the webhook module and choose "Download output bundles" from the drop-down menu next to the "Data size" label. Use Postman to send this data to your scenario. Alternatively, create a new scenario with HTTP > Make a request module and use it to send the data to your scenario. You can also check the video guide here - Integromat Academy 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 ) Ability to "re-run" historical instances: https://integromat.canny.io/feature-requests/p/ability-to-re-run-historical-instances

When using the http module, specifically with POST requests with large JSON/XML/querystring payloads it is virtually impossible to format the data so that the indentation is correct and readable. This forces me to copy and paste the text to a text editor for formatting. Additionally it would be cool to have some sort of script validate the body and show an error incase something is not valid. This would make my life easier, am pretty sure others would agree. ---------------------------------------------------- BESTPRACTICE: Use our "JSON > Create JSON", "XML > Create XML" modules that can help you with building the JSON/XML payloads or editing of already existing payloads. See our docs: https://www.make.com/en/help/connections/connecting-to-any-web-service-that-uses-api-tokens-authorization#json-body-mapped-using-thejson---create-jsonmodule

We sometimes have the problem that too many webhooks arrive at the same time, so that the scenario gets processed 50 times in parallel, which results in hitting rate limits of the ClickUp API. We could instead use "Sequential processing" but then only one would be processed at a time, which slows down the process massively. We would like to suggest an option in each scenario to set X amounts of webhooks can be processed at a time. For some scenarios I would like to process 10 in parallel, for others maybe only 5 in parallel. Is this porrible to implement? Thanks.

Would be great to take a module or a branch (series of modules) and copy paste it in another scenario. Sometimes while building I realise that a branch would be better off being a scenario on it own. At the moment, I need to redo all modules within a new scenario.

Currently, to convert values (for example, map month numbers like “01”, “02”... to Polish month names), I need to add 12+ text replacement modules, which makes the scenario unnecessarily long and hard to manage. There is no option to use built-in logic (if, switch, case) or simple code (like JavaScript or Python) for such data transformations unless I integrate an external app, which is not convenient for security and workflow reasons. It would be extremely useful to have: A mapping block (dictionary, switch/case, or value map) Or a custom code block (JavaScript, Python) directly in Make, without relying on third-party integrations This would make scenarios much more efficient and user-friendly for everyone who needs basic data transformations.