Feature Requests

Being able to group automations into folders would be sooo useful in keep things organized and knowing how/where to find specific automations. With hundreds of automations across different tables/solutions it is impossible to keep track of what needs maintenance and updating, even with a meticulous naming convention.

Being able to duplicate a tab in dashboards would be a huge time saver. Having different tabs in a dashboard offers endless opportunities, but the inability to duplicate them makes it a bit painful to “rebuild” several tabs with similar setups/modules.

It would be great if you could view dashboards on Mobile

For example, if I create a record/task that repeats daily, I want the option to view x number of future instances for that task. This is especially useful in calendar view so you can see all your upcoming tasks for the week/month without needing to create each one individually.

The "Off/On" style of button works great, but "Off" and "On" isn't always relevant in terms of the use case. Being able to control what the "Off/On" states say in the button would be amazing. Examples might be: "Not Saved/Saved" "Not Sent/Sent" or even being able to have the "Off" state be blank, and the "On" state say something. 🙌 Does this affect operations? I suppose not, but would be a nice polished improvement to anyones setup.

It would be ideal for a company to have it under their own domain and change logos, etc -ie. white labelling, any plans for it?

To be able to use conditional logic around the actions in an automation similar to Airtable, ie not in the trigger but in the body of the auto.

Allow inserting files (images) into an email that is part of an automation

When building dashboards, It can be time consuming creating new modules, and setting up filters/visible fields/column widths etc. Being able to copy a module (particularly a Grid View) and paste it in a different tab would be fantastic. Notion allows you to duplicate/copy/paste "Linked Databases" the same way I've described this.

Enhance the CSV import functionality to provide better control, safeguards, and customization options, reducing the risk of unintended changes to data, especially in scenarios where duplicate or repeating keys might cause issues. Requested Enhancements: Option to Disable or Restrict Override/Replace Functionality: Add a configuration option to disable the "Override" or "Replace" functionality during CSV imports. Allow administrators to enable/disable this feature on a per-table or workspace basis to ensure data integrity. Autonumber as the Default Key: Provide the option to set the Autonumber field as the default key for identifying records during imports, rather than relying on fields like "Title," which may have duplicates. Allow administrators to define default key fields for CSV imports. Improved Warnings for Override/Replace: Introduce clearer, more prominent warnings when users select the "Override" or "Replace" option during imports, emphasizing potential data loss or unintended changes. Include a confirmation dialog that highlights the number of records potentially affected and allows users to review changes. Restrict CSV Import Access for General Users: Provide an option to restrict the CSV import functionality to specific user roles (e.g., Administrators or Managers) to prevent unintended bulk updates or changes by general users. Include granular permission settings for who can perform imports and use override/replace functions. Benefits: Prevents data integrity issues caused by duplicate or unsuitable key fields. Reduces the risk of unintended bulk updates or data overwrites during imports. Ensures better control and safeguards over data management processes. Improves user experience and confidence in performing imports without unintended consequences. Example Scenarios: When importing records into a table with hundreds of repeating titles, the Autonumber field can act as a unique identifier to avoid overwriting data mistakenly. General users are restricted from performing imports, limiting bulk changes to data only to authorized personnel. A warning prevents a user from accidentally using the "Replace" function and overwriting thousands of records.