Platform Ideas and Improvements

A few months ago, Make released a gigantic cosmetic overhaul to the webpage that lists all of our scenarios. However, when you guys updated the scenario list page, you also introduced a major bug. The major bug is that ever since this update, the scenario list can no longer be scrolled through on the iPad. We can only see the first few scenarios, but there is no ways to scroll through the list to see the rest of our scenarios. This makes it impossible to use Make on an iPad, which is something that we did all the time in the past. Can you please fix this bug ASAP, so we can continue using Make on our iPads? Thank you!

Please allow the ability to bulk insert rows into the datastore, rather than each row costing an update.

It would be fantastic if you could easily copy things like Actions and even Custom Apps. However, some advanced editing would be necessary because, at the moment, certain properties are hidden after these entities are first created.

I would like to see a new module that supports Tesla API

We should be able to create a group or folder of team variables to organize them and have better visibility, instead of having long list of variables.

When working with arrays of strings that represent numbers, it would be helpful if the sum function offered an option to treat strings as numbers. Without this, we have to use workarounds or chain multiple numeeric aggregators, which adds unnecessary steps and hurts usability.

My name is Jonathas, and I’m a Brazilian accountant / automation professional and a student of Roberto Dias Duarte’s program. Through this training, I’ve been learning and building workflows inside Make.com , and now I’m starting to implement agentic (AI agent) workflows in real business scenarios. I wanted to respectfully ask if Make could prioritize and accelerate the availability and evolution of the “Agent” feature. Many professionals and companies here in Brazil are eager to adopt agentic automation using Make, and we truly believe the platform has the potential to lead this movement — ideally with an Agent experience that is faster, more robust, and easier to implement than what’s currently emerging in n8n. Thank you for everything you and your team are building. If you ever want feedback, tests, or real-world use cases from the Brazilian market, I’d be happy to help. Best regards,

Problem / Background Currently, the Analytics Dashboard displays the total number of errors and error rates, which is helpful for a high-level overview. However, clicking on these error counts doesn't provide any detailed breakdown of what errors occurred, when they happened, or which scenarios were affected. As someone who manages many scenarios, I rarely check email notifications for scenario errors. To work around this, I've built an automation using the Notifications API endpoint to forward error alerts to Slack. While this helps, the information available through the Notifications API is still quite limited for effective error monitoring and troubleshooting. Feature Request Error Details in Analytics Dashboard When viewing error counts in the Analytics Dashboard, I would like to be able to drill down into the details, including: Scenario Name/ID – Which scenario encountered the error Error Timestamp – When the error occurred (date and time) Error Type – The type/category of error (e.g., ConnectionError, DataError, RateLimitError) Error Message – The detailed error description Execution ID – Link to the specific execution for further investigation This would allow users to quickly identify and resolve issues without having to navigate through each scenario's execution history individually. Error Details API Endpoint In addition to the dashboard improvements, please expose this error detail data through the API. A dedicated endpoint (e.g., /api/v2/errors or /api/v2/analytics/{organizationId}/errors) that returns: ```json { "errors": [ { "scenarioId": 12345, "scenarioName": "My Scenario", "executionId": "abc123", "errorType": "ConnectionError", "errorMessage": "Connection refused: target server unavailable", "timestamp": "2024-12-03T10:30:00.000Z", "moduleId": 5, "moduleName": "HTTP Request" } ] } ``` This would enable users to: Build custom monitoring dashboards Integrate with external alerting systems (Slack, Teams, PagerDuty, etc.) Perform automated error analysis and reporting Create proactive maintenance workflows Use Case Organizations managing dozens or hundreds of scenarios need efficient ways to monitor errors across their entire Make environment. The current approach requires either checking email notifications (which many users don't monitor closely) or manually reviewing each scenario's execution history—neither of which scales well. Having error details accessible both in the Dashboard and via API would significantly improve operational visibility and reduce the time needed to identify and resolve issues.

Please improve the Wordpress post creation module, so it can take a CSV text list of categories and tags and have it automatically get the IDs for those, or create new ones, and add them to the post. It is very very difficult and complex at the moment to do this using iteration.

Currently, all test runs consume credits at the same rate as live executions. Given how essential repeated testing is during scenario development, this approach can become quite costly very quickly - especially when troubleshooting complex flows (because also of the counterintuitively of the platform! ). A dedicated testing mode with reduced credit usage or a separate credit pool for testing would help teams experiment and iterate without excessive overhead. Ability to Retest from a Specific Scenario Step Another major pain point is the inability to restart tests from a specific step. Once a scenario progresses beyond certain steps (and the data is pulled), there’s no way to isolate and retest just a portion of the flow with the retrieved data set. Enabling a feature that allows developers to start or re-execute the scenario from a chosen module would save significant time and credits.