Commit automation and extension scripts to a GitHub, GitLab or Bitbucket repository. Allows for backups, version control and restoration of scripts. ... View more

Currently, the button field allows you to run an extension script. I have to maintain separate automation and extension script that performs the same actions. Would be ideal to be able to run an automation like interface buttons do. Support for multiple triggers would also be helpful. For example, I could have a trigger for when a record meets certain conditions and a button trigger whenever manual execution is desired. An automation script where I think this would be useful is one that creates or updates a record/object in a third party system. ... View more

What is the proposed idea/solution? It should be possible to use detail view templates across interfaces if they are based on the same table, e.g., I have one interface that shows products and one interface that shows tasks and tasks are linked to products. Within the product interface I allow users to click into the details of the linked tasks and currently I have to recreate my task detail view across interfaces. How does is solve the user problems? I'd save time as I don't have to recreate detail views that I've already set up // I wouldn't have any discrepancies between detail views.  How was this validated? We have this issue constantly and are experiencing increased workload through this Who is the target audience? Builders ... View more

What is the proposed idea/solution? In the shared view while viewing  a workspace, we want to be able to see the base descriptions.  How does is solve the user problems? Viewing base descriptions is easy for onboarding new members of our team and visualizing easily what base is used for what. How was this validated? ...with your team Who is the target audience? our team ... View more

Overview: We cannot create new Linked records when submitting a form. There is only the ability to create a new Linked record after the initial form is submitted (and record created). This is not conducive to some workflows, where it would be very helpful to create a linked record during the initial record creation process. Feature Request: Allow users to directly create linked records while they are in the process of submitting the initial Form/record in Interfaces. Current Workarounds: Provide a link on the initial Form for a user to open up another form to create the linked record prior to them completing the initial form. Create additional fields in the table and then use automations to automatically create linked records in the background when those are selected.   ... View more

While it's possible to autofill a "User" field type using the "Current User" that's logged into an Interface, it is not possible to auto-link a Linked Record using the currently logged in user.  Use case: We have a custom table of our users that contains a number of fields including the user's email address. We would like to have the option to autofill (set the default value) of a linked record to the current user that's creating a new record in an Interface form. Currently the user has to select themselves out of the list and this adds an extra step to creating a new record and introduces opportunity for data entry errors (e.g. mistakenly selecting a similarly named user) Example 1: Shows the properties of a User field where "Current user" is selected as the Default Value Example 2: Shows the properties of a Linked Record where there is no option to use the Current User as a default value to auto select the correct linked record. ... View more

What is the proposed idea/solution? Add an option to sort the list of bases on the Home screen alphabetically. How does is solve the user problems? The current sort options are oldest<>newest only. This means bases and interfaces change places on the screen each time a base is clicked into. The user problem: this makes the Home screen inaccessible to those who have trouble following constant visual changes. Alphabetical sorting would solve this problem by allowing bases and interfaces to stay in consistent positions on the screen. Who is the target audience? Everyone (others have requested this functionality for non-accessibility reasons as well) ... View more

What is the proposed idea/solution? Add more imported data from each email imported from Outlook via Automations. Specifically I'm missing "Conversation ID" that could be very useful to automatically group emails that are part of a longer conversation. If possible, also being able to get at least PDF attachments would be amazing. How does is solve the user problems? I have to rely on one or more services to get these features today (Power Automate (has more data from each email) to Google Sheets, then using automations to import from Google sheets. As you already have a Outlook integration, adding a few more data points should be easy. How was this validated? Other services provide much more data points for Outlook emails. Who is the target audience? People that use Outlook and Automations to import emails from their inbox to Airtable. ... View more

Field names have to be hard-coded into a formula, which makes it so you can't do something like indicate which field name to pull from in a multiselect field. You can only use a switch with hardcoded field names, or use a whole bunch of if statements to make different things happen depending on the multiselect options. I'd love to be able to write like: FIELDS({multi-select that says which fields to return}) and have that return the value of all those fields as an array ... View more