This seems obvious, and I guess there is a back-end reason it's not already the case. But there are several limitations in airtable that make automation troubleshooting more difficult than it needs to be. It would be infinitely more helpful if airtable's failed automation notifications were instant. There's always a delay of at least a few minutes, but often much longer. The delay, combined with the lack of suggestion 2, makes it quite hard to piece together why an automation has failed (usually we are entering data, going back to another job, and seeing an automation failed notification in the emails later) - so it's not that easy to trace the steps back to find out what action triggered the failure. Activity log for whole base. Rather than needing to check trash logs, individual record logs, etc, it would be really helpful to have all of this info collated in one space. Ideally this log would also included failed automation runs. When there are complicated automations that fire other automations, it's sometimes really hard to piece together what actions are creating failures. I often really struggle to recreate failures.   ... View more

Requested change: On the account home page either include shared bases, interfaces, and workspaces under "All Workspaces" or add a separate "Shared with Me" item below the All Workspaces menu button/chevron. Reasoning: Newer users often are unable to easily find shared interfaces and bases after responding to the initial invite.  Many if not most users' first experience with Airtable comes via sharing, and they should be able to go to Airtable.com, log in, and immediately see what has been shared with them.  Users may naturally select "All Workspaces" but this will not lead them to the shared items.  Even selecting Home may not show the shared items if the filter is set to "Opened by You." All filters should be off upon the initial landing view so that everything the user is authorized for is visible, whether shared or user created and regardless of open status. See Google Drive screenshot for what this can look like and what would be familiar to many users. ... View more

Airtable already depends on pre-defined formatting. And to certain degree formatting is configurable. Some fields might have different `actual value` and `presented value` by default - for example the datepicker, duration or percentage field. This is great! It makes the field both user friendly and well usable within automation and scripts and filtering, sorting. I think it would be awesome if this pattern would expand further: Often we're using formula fields. To some degree there's a possibility to format the formula field: as number, currency or even map it to single select options. What if in the formatting tab, there would be an option for "formula"? Then you can define your own custom way to format your value. Examples: Formatting difference values as `+5%` with the `+` included. (Price difference) Custom date formatting via DATE_FORMAT (but the underlying value is still date) Custom duration formatting Units visible directly in the cell (200 m²) Custom number formatting (using both K, M as needed... 100K, 200M) Formatting dependent on other fields! $200 in one record, €200 in another, based on the picked currency in the Currency single select field Custom labels for Urls and buttons! The button CTA could be different based on other fields but the link is defined. `Open 'SKU123' in Admin` or `Delete John Doe in X` (as opposed to Delete User). I think this little thing could improve a lot of QOL improvements. And you would not have to have special `formatted` formula fields. Values would display nicely and at the same time you could also practically work with them in automations and scripts. The main downside? It could be confusing to someone that they are entering a value but the underlying formula then transforms it differently. For example you enter "3" and it shows up as "0.03%", depending on how the author designed the formatting formula. But I still believe this would be a net positive feature 🙏 ... View more

What is the proposed idea/solution? Add PDF as supported file type for attachment annotations. How does is solve the user problems? This would allow more robust proofing & approval workflows than what Airtable currently allows. PDF is a standard format for this workflow and not being able to annotate drives users to seek external solutions or move to alternate platforms. How was this validated? This is a standard need, and the attachment annotations help page confirms that PDF is not a supported file type. Who is the target audience? Marketing & Creative teams, Sales teams, Legal teams/contract review, any other teams that need to be able to annotate PDFs vs. just images or videos. ... View more

Proposed Idea/Solution: The idea is to introduce a “Default Column Order Template” in Airtable. This template would allow users to define a consistent column order that automatically propagates to any views linked to the template. For example: •If View #1 and View #5 could both reference the same “Default Column Order Template” (e.g., “Template: Customer Service Data”), any changes made to the column order in the template would dynamically apply to both views, maintaining consistency. •While linked views would share the column order, they could still independently choose to show or hide specific fields/columns, giving users flexibility while ensuring a uniform structure. This feature would save time, enhance collaboration, and reduce errors caused by inconsistent column arrangements across multiple views.   How Does It Solve User Problems? This feature addresses several challenges: 1.Efficiency in Multi-View Management: Users working with multiple views often need a consistent column order to streamline workflows. Manually maintaining the same column order across multiple views is time-consuming and prone to errors. A default column order template would ensure consistency across views with minimal effort. 2.Team Collaboration: In collaborative environments, different team members might use different views of the same data. Having a consistent column order ensures everyone is aligned, reducing confusion and making it easier to locate fields. 3.Improved User Experience: For projects involving multiple teams (e.g., customer service, marketing, and analytics), a unified column order reduces onboarding time for new team members and enhances data usability. 4.Dynamic Data Adjustments: As fields are added, removed, or reordered in the template, linked views dynamically reflect those changes. This ensures up-to-date and organized data without requiring manual updates in every individual view.   How Was This Validated? While this request arises from a practical need observed in real-world workflows, its benefits have been implicitly validated through user behaviors and existing challenges: 1.User Feedback Patterns: Many Airtable users express frustrations in forums and support requests about the manual effort required to maintain consistent views. This feature would directly address such feedback. 2.Analogous Features in Other Platforms: Systems like spreadsheet templates or CMS tools often offer shared configurations for layout or structure. These serve as precedent for the efficiency and utility of such a feature. 3.Internal Testing Opportunities: Airtable could validate this feature through beta testing or user surveys, targeting teams or users managing complex bases with numerous views.   Additional Use Cases: 1.Customer Relationship Management (CRM): A sales team and customer service team might use different views of the same customer data. Maintaining a consistent column order ensures smooth transitions between teams without data disorientation. If 50% of their views need to be different, for their CS team as an example, then that team would use their own template! 2.Project Management: A project manager might create views for “High-Level Overview” and “Detailed Task Tracking,” where consistency in column order aids in quickly understanding data context. 3.Event Planning: An event planning team could have separate views for “Guest List,” “Catering,” and “Budget,” but benefit from a unified column order to avoid confusion when cross-referencing data. 4.Analytics & Reporting: Analysts working with multiple dashboards can maintain uniform field arrangements, making it easier to compare and combine data.   This feature would be a game-changer for users managing multiple views and collaborating across teams, ensuring Airtable continues to be a leader in dynamic data management. ... View more

I've had a few cases where I was using views in the style of a "help desk" and really wanted to see the number of records that needed to be actioned on. It would be nice to have an optional badge count shown for records in a view or in the interface pages, especially for help desk and similar apps where the views and pages are filtered based on the actions needed to be taken. ... View more

We need a 'Conditional Select' type field to add to forms. This type of single select and multi select question would conditionally disable and 'grey-out' specific options in select questions on forms. It doesn't seem currently possible to do this. There would be many use cases for this. My particular one is that I have a form for view only users to update certain fields in a database for a not for profit or charity music school recording students and musical instruments loaned to them. We need to prevent students resigning but not handing instruments back. The first single select question on the form is "What do you want to do?" which hides/shows various fields on the same form. One of the options is to resign a student. If that student is still holding an instrument, (ie. {instrument ID} is not blank) It should not be selectable, but should still be visible, greyed out so that the user can see they are in the right place and its clear they cannot select that option. An important feature of the proposed conditional select field would be the option to include a warning message when the disabled option is clicked or hovered over, which should allow the inclusion of variables from the source field causing the restriction. ie. in my use case, I would want to say, "{First name} cannot be resigned at this time because records show they are still holding the instrument {Instrument ID}. I think this feature would be of great benefit to a lot of Airtable users. ... View more

I'm a PM at a Product company and we've been using the Gantt view to build all of our schedules! One function that would be extremely helpful is the ability to add or remove the vertical lines that run through milestones, depending on how we want it visualized.  Example: We have a Mile High view that displays only milestones for multiple projects across the company. With so much overlap, the vertical lines become extremely condensed and messy quickly. Our goal is to have one, visually clean view that we can return to on a monthly basis and review with a cross-functional team to track milestones across the company. Would love any suggestions here! ... View more

What is the proposed idea/solution? I'd like to have the ability to save draft forms before sending them and recall them later. How does is solve the user problems? A user can start filling out a form, save the answers entered and complete the form at a later time, for example if they need to collect information to be able to answer everything. Who is the target audience? Anyone who uses a form to collect complex information, which requires time to fill out or the need to collect additional information. ... View more