Platform Ideas and Improvements

Whenever I try to map a datetime field the datetime panel shows up, and if using the panel to select a time it adds datetime in this format MM/DD/YYYY HH:mm A and not as ISO 8601 format YYYY-MM-DDT:HH:mm:ssZ This makes zero sense, every datetime field where the datepicker shows up will only accept the ISO datetime format not a custom friendly format. Not sure how this passed the QA and still live for like past year. If this is intended, I'm curious to know why as it has never been helpful to me.

Greetings, Make Team. I want to ask about Make MCP Server. So I've tried the Make MCP Server via Langflow and good thing it worked. But, the output only tells us that the "Scenario is executed successfully". Is it possible for us to get the module's output value from the scenario, not only the success message? If yes, can you tell us how to do it? If not, can you provide it for the next feature? Thank you.

My scenarios are supposed to run every day at 00:01 to collect data. Due to the summer time changeover, the start time always shifts by one hour and is then automatically at 23:01. It would be really helpful to have a setting that considers the time changeover.

When using scenario chaining (child scenarios), the child scenario's output isn't returned to the parent, strongly limiting the usefulness of what otherwise seems like a core feature. Only the Execution ID is returned; the feature request is to return whatever was output by the last module in the child scenario. Not having this forces designers to work around the problem using webhooks, making the process far more complicated and inefficient than it needs to.

Would be nice to have the ability to define global variable for multiple usage. For example: a SFTP patch to a specific folder which is used in multiple scenarios. ------------------------- BESTPRACTICE: If you can spare one Data store ( https://support.integromat.com/hc/en-us/articles/360006248793-Data-store ) you may use it for storing your global variables: Click on the "Data stores" menu item in the left vertical menu. Click on the "Add data store" button in the top right corner. Setup a Data store and the underlying Data structure (see the 1st screenshot). Click on the "Browse" button of the newly created Data structure. Add a variable to the Data store (see the 2nd screenshot). In your scenario, use the "Data store > Get a record" module to obtain the value of the variable (see the 3rd screenshot).

Be able to convert String types to Number types. Like the toString function that changes any type to a text type.

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

Please add an option to retry incomplete executions in bulk (either Retry All, or Retry Selected with a bulk selection option). Background: In the event that a scenario fails due to a connection error, failed executions need to be re-run individually, which is an extremely tedious process: Click to view the execution Click on the canvas to see the Run button Click the Run button Wait for the execution to run …and this can't be done in parallel because retrying multiple executions in the same module results in an error.

On an HTTP module, if you turn on the "Evaluate all states as errors (except for 2xx and 3xx)" option and the request returns an error code, there is no way to process the body of that response. Some services add extra context about the error in the body of a 4XX-5XX code. This will allow you to do multiple things, such as: Set proper routing based on the message. Save a record of the specifics of the error. Handle error responses in a more efficient and quick way. Thanks!