- 30 Nov 2023
- 4 Minuten zu lesen
Interface element: Button
- Aktualisiert am 30 Nov 2023
- 4 Minuten zu lesen
The Button element allows collaborators who are interacting within an interface to perform an action or set of actions at the click of a button. This feature works very well with the "Record review" and "Record summary" interface layout templates. If you are building an interface from scratch, then many of the button actions work with the record list element.
All plan types/levels
Please consult this support article for a breakdown of Interface Designer permissions.
Web/Browser, Mac app, and Windows app
Adding and configuring button elements
If this is the first time you've added elements to an interface, please consult this help article first.
Find the Button element by clicking + Add element in the lower left portion of the interface editor.
You'll then place the element somewhere in the layout of your interface page. Don't worry if it isn't in perfect positioning yet, as you can always move the element later.
On the right side of the page, you'll see a dropdown menu to pick which type of action the button will perform when a user clicks it.
A button element can perform the action types listed below. The first 6 action types require a record picker or record list element to be used. The last 3 action types listed below don't require a connected element.
Update record - Configure a button to perform single or multiple updates to a record. One example would be to quickly update a record's status with the click of a button. You can also set the button to automatically move to the next record once it is clicked.
Copy link to record - Depending upon the current record being reviewed/summarized, this action will copy a direct link to that record in the interface page currently opened.
Delete record - A button to quickly delete a record opened from the chosen source. As always, users can press CMD Z to quickly undo an accidental deletion. Editors and creators with access to the underlying base can also access the base trash to restore deleted records.
Go to previous/next record - Add a button to help users simply navigate to the next or previous record.
Go to URL in record - By connecting the button to a particular URL field, it creates the ability to have a dynamic button that will navigate to the URL in the particular record that is currently open. You can also choose whether or not to open that URL in a new browser tab.
Run automation - Choose a previously configured automation to trigger when the button is pressed. You can also start creating a new automation right in the interface. After naming the automation you can click Continue to start building the automation in a new browser tab. There are two requirements in order to set up this button element action:
Either a record picker element or a record review layout (containing the record list element) must be present on the interface page where the button element is placed to use as a source.
For an automation to be used with the button element, it must include the When a button is clicked automation trigger. Read more about the setup process here.
Go to interface page - This allows you to add a convenient button that links to another interface page in this interface. You can also choose whether or not to open that interface page in a new browser tab.
Go to external URL - Add a link to another website, another interface, an Airtable base, and more. You can also choose whether or not to open that external URL in a new browser tab.
Before moving on to further interface configuration or publishing your interface, you may want to rename/label the button or change its color to provide more context to collaborators who are interacting within the interface you are building. You can also have the button update colors and/or label after the button has been clicked.
Test the button
Lastly, it's a good idea to test the button, especially in more complex use cases, to ensure that it is performing the way you would like it to. Below you can see that pressing the "Mark project complete" button updates the checkbox field the way we intended it to.
Are there any limits to be aware of with the button element?
You can set a button to perform a maximum of 5 actions at once. The actions performed are all or nothing. There is no "logic" that can be configured for the button
Can collaborators with Read-only or Commenter permissions click on buttons?
A collaborator can only click on buttons in interfaces that meet their permission levels.
A read-only or commenter collaborator can only click on buttons with certain action types such as Copy link to record, Go to previous/next record, Go to URL in record, Go to interface page (if they have access to that page), and Go to external URL.
Read-only and commenter collaborators are not able to click on buttons with the Update record, Delete record, or Run automation actions since they are not allowed to perform those types of actions with their given permission level.